: Is there a benefit to using AMP on already fast mobile sites? I have a blog that scores 100/100 on page speed insights mobile. It seems like I already follow most of what AMP does like inlining

@Eichhorn148

AMP's biggest performance improvement is its ability to lazy load images and ads. From github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md:


HTTP requests necessary to render and fully layout the document should be minimized.
Resources such as images or ads should only be downloaded if they are likely to be seen by the user.
Browsers should be able to calculate the space needed by every resource on the page without fetching that resource.



If your page has images or ads below the fold, it is likely that AMP will be able to render your page faster by lazy loading the images.

However, it is possible to hand implement an optimized page faster than AMP. At the very least, amp requires a call to a piece of third party javascript (cdn.ampproject.org/v0.js). If you don't need the features provided by AMP, then that JavaScript call itself will bloat you site. It is possible to get results better than AMP with techniques such as:


Removing third party resources
Inline JavaScript and CSS
Data URI images


AMP places restrictions on development. It limits which HTML features you can use. AMP may or may not be straightforward to implement because of these restrictions.

AMP may be able to optimize your site beyond the 100/100 score on PageSpeed Insights, however it is not straightforward just to tack in on, and if you don't need image lazy load, AMP itself can be added weight to your page.

Vote Up Vote Down