What is an AMP page?
An AMP page is a page built specifically to render fast as static content with the resulting save of time and bytes to the final client. To achieve the goal these page are using the three following techniques:
- AMP HTML Basically is HTML with extended properties. In some cases adding attributes and in others replacing the existing ones to get advantage of new capabilities.
- Google AMP Cache Is a Content Delivery Network (CDN) acting as a proxy where all the AMP documents are precached in order to provide them all automatically optimized, serving all resources, like images and js, from the same origin with the HTTP 2.0 advantages.
AMP performance practices
- Allow only asynchronous scripts to avoiding delays in page rendering and block during the DOM construction.
- Size all resources statically All the resource sizes are sized statically to avoid style recalculations. Only one request is needed to get the document layout and fonts.
- Don’t let extension mechanisms block rendering All scripts that require additional HTTP request will be sandboxed with an amp-iframe to don't block the page rendering.
- All CSS must be inline and size-bound Minified and write it all on the <head> of the <html ⚡> document.
- Minimize style recalculations Any style recalculations is made till the entire page layout is loaded because the DOM is all read before it's written.
- Only run GPU-accelerated animations The css animations, transitions and opacities are made by the GPU dedicated.
- Prioritize resource loading The most currently important resources are loaded first.
- Load pages in an instant Prerendering thanks to the preconnect API helping the page to be rendered before the user takes the action to navigate.
- Help make AMP faster The AMP project leads you to contribute to this opensourced project.
The Google AMP Cache is a proxy-based content delivery network for delivering all valid AMP documents. It fetches AMP HTML pages, caches them, and improves page performance automatically. When using the Google AMP Cache, the document, all JS files and all images load from the same origin that is using HTTP 2.0 for maximum efficiency.
More information about it: https://www.ampproject.org/
How it looks the structure of an AMP document
This is an example of an html AMP page.
How to build an AMP document
Basically you should build a page with the following structure and you have an AMP ready page to be distributed.
And you also have to link your non AMP document with a link rel tag on the head of your normal document.
You can check a complete AMP HTML tags specification on the Github project page https://github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md
Wordpress users and AMP documents
If you are using a Wordpress content management solution you have a plugin (as usual) that solves the problem to generate all the AMP versions of your content.
What does think Google after all?
All the SEO people should be aware if it alters the results and an AMP version of a page raises your Google ranks or not.
Google is offering from mobile searches the AMP version of an HTML page if it is indexed highlighting the result with the featured lightning.
What I think about it?
The strategy is similar that the provided for the Opera Mini for cellular phones. The Opera Mini browser acted as a proxy to deliver small, fast and optimized versions of the requested pages provided from Opera servers. The AMP project is a tool to delegate the responsibility to the content providers and freeing the intermediary of the task.
IMHO, I think Google is forcing with this technology the web developers to provide simpler webs instead of bloated ones that you can find over there. For sure Google knows, and lives for it, that ads are for many webs their economic sustenance and provides all the tools to deliver optimized and necessary ads fast and small sized.