Current versions of Google Chrome support prefetching as well, but the process is limited as it does not execute JavaScript or renders the page in advance. The main goal of the feature was to use less memory than full prerendering according to Google while still reducing page load times in the process.
Prerendering speeds up the process of loading websites as some content is preloaded. Google changed the prerendering behavior of Chrome in version 63 when it limited the functionality. While prerendering may speed up the loading of sites, it may also waste resources at times; this happens when content is preloaded that is never seen by the user, e.g., when a site with preloaded content is not accessed at all.
Omnibox prerendering adds more elements to the prerendering process. In particular, Chrome will process the DOM tree construction and script executions. The browser limits the new omnibox prerendering feature to "high-confidence suggestions" only according to the intent to ship discussion on
Google Groups.
We would like to ship omnibox (i.e., URL bar) prerendering. With this feature, Chrome will start prerendering the high-confidence omnibox autocomplete suggestions. Chrome is currently prefetching resources for high-confidence suggestions using No-state Prefetch, but with this feature we will be further processing the webpage, including the DOM tree construction and script execution.
Websites that are selected by Chrome for the process are "loaded before the navigation is committed", Google notes. Chrome will support a basic API that websites may use to find out if it is prerendered and when it was activated.
