Google plans to ship omnibox prerendering in Chrome
Google may soon integrate a new feature in its Chrome web browser that it calls omnibox prerendering to speed up the loading of certain websites in the browser.
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.
The new omnibox prerendering feature will be supported on all platforms that Chrome is available on. Google plans to introduce it on Android first before it becomes available on other platforms. Chrome users may set an experimental flag in the browser to enable the feature right now in Chrome.
- Load chrome://flags/#omnibox-trigger-for-prerender2 in the Chrome address bar.
- Set the state of the experimental flag to enabled.
- Restart the Chrome browser.
A demo page is available at https://omnibox-prerender.glitch.me/ to test the functionality.
The feature should be considered experimental at this point. Work on prerendering version 2 continues at Google.
Now You: what is your take on preloading? Good feature? (via Techdows)
Gargoyle will do anything to get your cookies sent to them.
Cookies… Too late.. Here comes an invasion of our daily lives, maybe ?
*Chrome OS Flex*.
Free OS for everyone, if W10 & W11 is a no-go on your older than six months computers.. Article about it ?
Very interesting new upcoming feature imho! :]
WTF is wrong with Chrome that Google is releasing trick after trick to speed it up? My Chromum works fine, maybe a second or two max for slow page loads, most seem instantaneous. I do have a good ad blocker/anti-tracker working, is that the difference?
Is Google serving SOOOOO many ads they’ve constipated Chrome? Do they have such employee bloat, MS style, too many have nothing to do beside pointless initiatives like this?
It’ll make a slow internet connection probably seem slower and do nothing for a fast one. Disabling preloading speeds up browsing! Of course it does; this is really about sending ads with better focus that no one will look at just like all the other ads no one looks at.
Chrome Google’s Exectutive VP of Advertising.
Preloading has been in Chrome/Chromium since day one (and most web browsers have it too now). It’s one of the main reasons why Chrome has a reputation for being fast, but also a resource hog. This is just an update to something that already exists.
works faster WITHOUT prefetch/preload/preconnecting ;)
Never change Google
Prefetching and prerendering already privacy no-nos. Now Google wants to add an API so that websites will be able to detect prerendering more easily. I’m glad that Brave disables prefetching.
Firefox can disable prefetching reliable.
Chrome/Chromium not so much. :(
> On Chromium 51 and above (including browsers based on Chromium 51 and above), this setting is completely unreliable, as it does not cause DNS lookups, preconnections and prefetches to be reliably blocked, because Chromium allows web pages to override that user setting.
“because Chromium allows web pages to override that user setting.”
If you turn the option on manually? Or regardless?
As I understood it, it’s in both cases (the uBO option and Chrome’s option).
uBO just switches Chrome’s option. The switch in Chrome is then greyed out and states it is controlled by uBlock Origin.