3 ms·
> AMP also came with the unfortunate requirement that publishers let traffic sources such as Google cache their content and serve it from their domain, such as
by gsnedders 5y ago
> AMP also came with the unfortunate requirement that publishers let traffic sources such as Google cache their content and serve it from their domain, such as google.com.
At least with Chrome, one related performance advantage will remain, given AMP pages will remain preloaded from Google results pages, whereas non-AMP pages won't be.
Why is this related? On mobile, Google preloads AMP pages in the carousel that are in the Google cache, which will obviously give them a page-load time advantage. Why not do that for more sites? Avoiding third-parties (i.e., third-party v. the Google results page) from being able to detect when they appear in search results and getting data (like IP) from the user regardless of whether or not they click on the result.
Is this insurmountable? Can you outperform it? Sure, but it's inevitably going to be harder as a result.
- jefftk 5y agoThis has changed too: Signed exchanges (SXG) allow Google Search to prefetch your content while preserving the user’s privacy. In practice, this means that both AMP and non-AMP results shown on Google Search may prefetch a few key resources (such as HTML, JavaScript, CSS, images, or fonts) in a privacy-preserving manner, if the associated website supports SXG. https://developers.google.com/search/docs/advanced/experience/signed-exchange https://developers.google.com/search/docs/advanced/experienc... (Disclosure: I work for Google, speaking only for myself)