Chrome’s ‘Never Slow Mode’ Could be a Standard Similar to ‘AMP’

In a recent post, I shared the technical details about Chrome’s upcoming “Never Slow Mode”. It talked about how Chrome is planning to run a website in “Never Slow Mode” (NSM) by limiting the number of scripts and restricting some other resources.

Today, I have some more details about Never Slow Mode. The most interesting thing is that Never Slow Mode is not just a Chrome feature, but possibly a web standard like AMP.

Never Slow Mode as a Standard

I stumbled upon this Github page today (linked from a Chromium code commit) which talks about the whole NSM plan in detail.

The very first paragraph from the Readme file made me think that this is not just a Chrome browser feature that we are looking at:

Never-Slow Mode (“NSM”) is a mode that sites can opt-into via HTTP header. For these sites, the browser imposes per-interaction resource limits, giving users a better user experience, potentially at the cost of extra developer work. We believe users are happier and more engaged on fast sites, and NSM attempts to make it easier for sites to guarantee speed to users. In addition to user experience benefits, sites might want to opt in because browsers could providing UI to users to indicate they are in “fast mode” (a TLS lock icon but for speed).

The document also talks about the need for standardizing the requirements to make “NSM” versions of websites. The goal of the project is to provide this standardizing so that developers know what to optimize and how.

Visual Cues for Fast Websites

The project proposes visual cues for fast websites or NSM websites. Just like we have AMP pages, we might soon see NSM versions of websites.

Further down the lane, we might even see warnings for slow websites. Read this paragraph from the document:

Today’s browsers tacitly condone terrible performance, however we’re starting from an even worse position; no browser today has a reliable signal against which to let users know that a site is fast (let alone slow). NSM provides such a signal in much the same way that the introduction of SSL/TLS in browsers created the opportunity to badge some sites as secure. In the short-run this will let browsers show users that certain sites are opting into delivering a good experience. In the long run, this enables the same default flip. At some date in the far distant future, perhaps only sites that don’t opt in will receive “slow site” warning UI.

Something like this:

I can also see an upcoming Chrome flag that will help us test this feature being added:

Let me end this by reminding you that this is a indeed a document written by an engineer working on the Chrome team, however, we cannot say if everything that is proposed here will become part of Chrome and maybe even other browsers.

What I am really keen to know however is your thoughts and comments on this. Do you think this will become popular like AMP?

If you are a developer, please share your thoughts on this new standard. Do you think this will help the web in general?

Leave a Reply

Your email address will not be published.