4 ms·
Isn't this at least in part because google was caching the pages & serving them (possibly pre-loading them, I don't know) from their own Google CDN? So comparin
by sequoia 6y ago
Isn't this at least in part because google was caching the pages & serving them (possibly pre-loading them, I don't know) from their own Google CDN? So comparing the speed of loading a performant page from google's CDN from a SERP click vs. loading the page from the origin is not really a fair comparison. My website would be faster if it were in a warm google CDN cache as well :)
https://developers.google.com/amp/cache https://developers.google.com/amp/cache
- HALtheWise 6y agoYeah, but the only reason that AMP is able to preload the page from Google's (or Cloudflare's) CDN cache without leaking your information to the website is because of all the other design decisions.
- fidelramos 6y agoIt doesn't leak information to the website but even worse it leaks your information to Google.
- Drew_ 6y agoThis is another purported benefit of serving AMP pages but doesn't this imply publications weren't already using CDN's previously or that Google's CDN is much faster than competitors? I would guess neither of those are true.
- joshuamorton 6y agoThe entire design of AMP is such that amp links can be safely preloaded by the browser, making effective load times 0ms, dinner the content is already on your device when your click the link.