Thats how with AMP you can speed up the performance?

The AMP stands for Accelerated Mobile Pages which is not only being supported by the Google search but also by various other platforms. A valid AMP HTML version can direct mobile users to the cached AMP and pages with invalid AMP will not be eligible for some Search features. Just like the search engine optimisation same can be done in the case of AMP and some combined optimisation techniques can help AMP pages to load fast.

1. Keep third party javascript out of the path

Third party javascript likes to use synchronous javascript loading. Let us give you an example:

“If you have three ads and each ad does three synchronous loads with one second latency then just for javascript loading it will take 12 seconds.”

Although AMP pages in sandboxed iframes allow the third party javascript by banning them and thus can be used there.

2. Allow only asynchronous scripts

We all know that javascript is an amazing thing and can modify every aspect of the page but at the same time it can cause multiple delays in page rendering. So to avoid the page rendering one should use the asynchronous javascript. A carefully designed javascript under the hood can avoid performance degradation.

3. Use inline and size-bound CSS

Although the inline style sheet has maximum size of 50kb but this size is big enough for well sophisticated pages. In AMP pages online inline CSS is allowed, so by removing one or more HTTP requests from critical rendering path and improve the performance.

4. Efficient font triggering

Page with few synchronous scripts and style sheets waits to download the page font, so AMP system declares zero HTTP requests until fonts start downloading. So by proper font triggering one can get the efficient performance.

5. Instant Page Loading

The preconnect API is used to ensure HTTP requests fastly as soon they are made. With this, a page can be rendered before the user explicitly states they’d like to navigate to it; the page might already be available by the time the user actually selects it, leading to instant loading.

When AMP document get prerendered for instant loading, resources that might use a lot of CPU (like third-party iframes) do not get downloaded.