Understanding and Benefits Using AMP (Accelerated Mobile Pages) for BlogspotWelcome to AMP blog for blogspot. For the first time, the author will introduce all about AMP from google and benefits when implemented on your blogspot. Let's take a full review of AMP..
What is AMP ( Accelerated Mobile Pages ) ?
Google Accelerated Mobile Pages is an initiative and innovation in the form of open source applications that arose from discussions between publishers and technology companies about the importance of improving the entire mobile content ecosystem for everyone including publishers, consumers, creators, and users.
If you ever search for an article on google and have found a search result that strikes "lightning", then it is certain that the blog and article are indeed valid AMP. And when you click on those search results, it is certain that the page is faster accessed.
Summarized from the web amp project, the AMP page is built with 3 core components ie AMP HTML, AMP JS and AMP Cache. Perhaps this cache is one of the important components of why the AMP page is so quickly accessible. Let's discuss them one by one:
AMP HTMLAMP HTML is HTML with some restrictions for performance that can speed up web page performance. There are indeed some restrictions on some regular HTML languages that can not be used in HTML pages.
Examples are script, style, OnClick, and much more. If in your blogger template using these languages, then certainly your blog will not be valid AMP.
In addition, the use of HTML and scripts for some components such as <img> is also replaced to <amp-img>, and even for the AdSense code was changed to improve page performance. We will discuss more fully about it in the next article.
AMP CacheGoogle AMP Cache can be used to display cached AMP HTML pages. Google AMP Cache is a proxy-based content delivery network to display all valid AMP documents. This network takes the AMP HTML page, places it in the cache, and improves page performance automatically.
When using Google AMP Cache, documents, all JS files, and all images loaded from the same origin using HTTP 2.0 to get maximum efficiency. (sumber: ampproject.org)