Google Chrome may get a “Never Slow Mode” to give users a consistently fast browsing experience

Google Chrome may get a “Never Slow Mode” to give users a consistently fast browsing experience

With over 70% market share, Google Chrome is undoubtedly the most popular web browser for all platforms. The reason why so many people use Chrome is that it’s fast, reliable, syncs with Google services, offers thousands of extensions, and is available on pretty much every relevant operating system. To make the experience even better, Google is constantly working on improving the websites’ performance. They are regularly improving compression algorithms and data-saving capabilities. Chrome Story noticed yet another performance-improving feature which should give users consistent browsing experience.

A new commit in the Chromium Gerrit unveils the “Never Slow Mode.” This newest feature is aiming to block large scripts and set budgets for contents like fonts and images. The description states, “Enables an experimental browsing mode that restricts resource loading and rutime processing to deliver a consistently fast experience.” For example, after adding the feature, Google will only allow scripts that take less than 200 milliseconds to end. There are several variables that come into play:

  • Per-image max size: 1MiB
  • Total image budget: 2MiB
  • Per-stylesheet max size: 100KiB
  • Total stylesheet budget: 200KiB
  • Per-script max size: 50KiB
  • Total script budget: 500KiB
  • Per-font max size: 100KiB
  • Total font budget: 100KiB
  • Total connection limit: 10
  • Long-task limit: 200ms

The current values may change when the build hits the stable channel. It is currently unknown when this will happen. At its early stages, “Never Slow Mode” will only be available as a development flag. It will most likely become a default option eventually, though.

Chrome Story also found clues about yet again a feature which disables “Best Effort Tasks,” which are tasks used for “writing user data to disk, cleaning caches, reporting metrics or updating components.” According to the commit, they will execute only after the website is closed. Currently, they run alongside the website, which fills up the disk, RAM, and CPU usage on the computer.

There is currently no information about the estimated release date of the feature. We are not even sure if it’ll make it to the next major version of Chrome, which should be released in March.

Via: Chrome Story

About author

George Burduli
George Burduli

Love everything about Android. I'm an enthusiast, blogger, and a future developer. Direct enquiries to: [email protected]