Reload button on the Browser and broken pages go hand in hand, in fact, Reload button is one of the most important features of any browser. Starting from Chrome 54, Google has revamped the way pages are reloaded and Facebook helped Google to make the change happen. Facebook informed Google that the Chrome was sending validation request at a rate of 3X as compared to other browsers.
Usually, when one refreshes the page, the browser fires up a revalidation process in order to check if the given source is still intact. The downside here, though, is that Chrome had been revalidating all the sub-sources while refreshing, eventually putting up the extra load on servers and users network for no fruitful reason. This feature of validating all the elements was designed back when broken pages were common and was crafted to address two causes with a single fix. But moving on, since the overall web quality has increased over the years, the relevancy of validating all the sources has faded.
Chrome has now been updated to validate the main resource and thus proceed with a regular page load. Needless to say, the new feature will help users save on data usage, power consumption and will also result in lower latency. Google has showcased how the changes have drastically improved the load time with Facebook now loading 28% faster with 60% fewer validation requests from Chrome. Furthermore, the change is also expected to help users access websites on Chrome despite poor connectivity.
Google has been working on making Chrome Browser less resource hogging and also bring about a surge in performance. Most of the updates have been focussing on reducing the load times and also the burden Chrome puts on the computing resources. However, the recent updates seem to have made things better and as a Chrome user, I have personally noticed that things are getting a little bit snappier but again it’s just the beginning.