AMP stands for Accelerated Mobile Pages, from Accelerated Mobile Pages, a project that emerges as an open source initiative. It embodies publishers’ vision to create optimized mobile content that instantly uploads anywhere. Surfing the internet through mobile is usually a slow, clumsy and frustrating experience and the AMP tries to end this feeling. Thanks to the APM, the navigability of a web page is significantly improved and as a consequence, it’s SEO.
Operation of the AMP
Like all web pages, accelerated mobile pages load in any browser or application. AMP files take advantage of various technical and architectural approaches that prioritize speed to provide a faster experience for users. The goal is not to homogenize how content looks and feels, but to build a core that is more common between pages and that accelerates loading times.
This does not influence the advertising system, since a page that uses AMP HTML will continue to choose its ad networks and the formats it deems appropriate.
AMP is a way to build static content web pages with very fast performance. Its structure can be divided into three distinct parts:
- AMP HTML: it is HTML with some restrictions so that it has reliable performance and with some extensions to build rich content beyond the basic HTML. The AMP JS library ensures fast performance of AMP HTML pages.
- The AMP JS library: implements AMP performance best practices, manages resource load, and provides tags, all to ensure fast page delivery.
- Google’s AMP cache is a proxy-based content delivery network for the delivery of all valid AMP documents. Gets HTML AMP pages, caches them, and improves page performance automatically. When using Google’s AMP cache, the document, all JS files, and all images are loaded from the same point that you are using HTTP 2.0 for maximum efficiency. The cache also comes with a built-in validation system that confirms that the page works and does not depend on external resources. The validation system executes a series of claims that confirm that the page complies with the HTML AMP specification. Another version of the validator is included with each AMP page, where validation errors can be logged directly to the browser console when the page is rendered, allowing you to see how complex changes to the code could affect performance and user experience.