4 ms·
When you click an AMP result, your browser does not actually navigate away from Google's search result page. The search result page just dynamically updates its
by playpause 5y ago
When you click an AMP result, your browser does not actually navigate away from Google's search result page. The search result page just dynamically updates its own DOM to show the AMP page content inline.
Depending on how confident they are that you are going to tap a given result, they can even preload the actual content and render it as hidden DOM so it can be displayed the moment you release your finger.
There is literally no possible way that a 'real' navigation (to a new page on a different domain) can compete with a simple DOM update.
- lmm 5y agoPreloading the link can save a network roundtrip, but shouldn't the browser be able to do that (and parse and pre-render) as well? Other than that, surely replacing the entire page content involves the same amount of work for the browser as rendering a fresh page.
- notriddle 5y agoThey tried. It’s too complicated to do it with all of the available features. https://groups.google.com/a/chromium.org/g/blink-dev/c/0nSxuuv9bBw https://groups.google.com/a/chromium.org/g/blink-dev/c/0nSxu... https://developers.google.com/web/updates/2018/07/nostate-prefetch https://developers.google.com/web/updates/2018/07/nostate-pr...
- playpause 5y agoI was talking about what’s possible for content creators to do on the web platform we have today, not whether it’s possible for browser vendors to make something AMP-like work at the browser level in future. On your last sentence: no I don’t think so. There’s got to be some overhead in setting up a new JS/DOM environment, parsing the HTML and CSS, determining security constraints for the new domain name, stuff like that.
- ec109685 5y agoIt’d also be a privacy issue given it would leak that the person viewed a link to your website.