Chrome, Good-bye to the performance drops with the new Never-Slow Mode
Google is trying out a new mode on Chrome that should limit the performance drops in web browsing. Here’s how it will work.
In a more or less near future, to date we do not know when, Chrome could introduce a new feature called ” Never-Slow Mode “, which should guarantee high performance in the most common web browsing experiences.
Chrome is among the most complete browsers around, but it can still improve dramatically in terms of performance and memory consumption. And they do not help the heavier (or badly developed) sites, which sometimes become a torture to visit.
The feature is currently in a prototypal state of development and is mentioned in one of the entries on the Chromium open-source project page. By activating the function, reading in the description, more restrictive rules will be applied for some elements of the page and for the heaviest scripts in order to keep the main calculation thread as clean as possible.
The project has not yet been described by Google, but one of the developers has broadly explained how the feature works to speed up the loading of web pages. These are the words of Alex Russel spent in the description of the mode:
” [The new function] at the current stage blocks large scripts, sets limits for certain types of resources (scripts, fonts, css, images), disables document.write (), limits XHR syncs, enables client-hints pervasively, and creates a buffer for resources without ‘Content-Lengh’ set.The limits are reconfigured after each interaction (click, tap and scroll) .The longer 200 ms scripts pause the entire page execution until the next interaction “.
The limits are set by default and, at least at the current stage of development. It is clear, that this is a feature that cannot be used on a daily basis. The feature could be introduced on Chrome as often happens with other experimental features, and will be activated within the advanced browser options with full user awareness regarding possible repercussions.
Some elements of the page could be blocked because they are based on resources considered too expensive to manage in terms of computational, and for this reason Google will insert a warning in the description of the functionality.
For more information, refer to the post written by Alex Russel on Chromium Gerrit
