Page Prerendering Introduced In Google Chrome Dev
Prerendering is a technology that can speed up web browsing by loading web pages in advance. The advantage of prerendering is an almost instant page loading time for prerendered pages. There are disadvantages though. The average web page has anywhere from a few dozen to more than one hundred links. Prerendering all link targets would send bandwidth usage to the roof. It would also take a long time to prerender them all. That's why developers use algorithms to prerender links with the highest click probability.
Google for instance knows that the majority of search engine users will click on the three first links in the search results, making those results optimal prerendering targets. But this is guesswork, which means that it happens that the wrong pages are prerendered. It should also be clear that usually more pages are prerendered than visited by the user.
Why the introduction? Because Google has added an experimental feature to Chrome Dev that introduces prerendering in the browser. The feature is enabled by default in Chrome Dev.
Chrome Dev users who do not want to use the feature can disable it in the Chrome Options. The easiest way to get there is to load chrome://settings/advanced in the browser.
Locate Predict network actions to improve page load performance and uncheck the preference to disable prerendering in Chrome.
Google notes that prerendering is available to any site, but that it will be only "useful to a handful of sites that have a high degree of certainty of where their users will click next".
Page loading of prerendered pages is very fast, which should be obvious considering that the page has been loaded already. On Google Search, Google seems to preload the top three results in the majority of cases, with other results occasionally thrown into the mix. This obviously means that some results will load normally, while a few will load faster.
Prerendering could be a problem for low bandwidth users and users who are paying by Megabyte / Gigabyte of traffic considering that multiple pages are prerendered of which some or even none at all may be visited by the Chrome user.
Webmasters may also see an increase in web traffic without increase in visitors. This may be especially true for pages that are listed as the second and third result on Google. For now, it is unlikely that big differences will be noticed. This may change once the feature comes to Chrome stable as turned on by default (via)Advertisement