AMP

Wooh...The another opensource framework of Google.
AMP is an open source HTML framework developed by the AMP Open Source Project. It was originally created by Google as a competitor to Facebook Instant Articles and Apple News.
AMP is optimised for mobile web browsing and intended to help webpages load faster (light weight Super fast).

Google Search recently announced a new Search ranking signal centered around page experience. We’re excited by the potential for Google’s page experience signal to guide and empower developers to build a better web. Because AMP was developed to help enable development of user-first sites, we believe AMP is a cost-effective and simple solution for publishers to create a great page experience. In today’s post, we want to step through what the announced changes to Google Search mean for the AMP community as well as the web ecosystem.

Google’s continued investment in AMP
Google will continue to invest in AMP, and strongly believes in the AMP Project’s goal to make it easy to create web pages that provide a great user experience. When available, Google Search will continue to direct users to the AMP versions of web pages in the mobile Top Stories feature. This behavior keeps in place hallmarks of the AMP experience, such as privacy-preserving pre-rendering that can happen when content is served from an AMP cache. This also means that the page experience signal for a given search result will be evaluated based on the performance of the AMP page when available.

The AMP Project will continue to focus on creating strong page experiences. AMP’s always up-to-date “evergreen” release schedule means AMP users will get future performance benefits as we make them, without investing additional engineering resources..

How to AMP Works.
The following optimizations combined are the reason AMP pages are so fast they appear to load instantly.

01) Execute all AMP JavaScript asynchronously
02) Size all resources statically
03) Don’t let extension mechanisms block rendering
04) Keep all third-party JavaScript out of the critical path
05) All CSS must be inline and size-bound
06) Font triggering must be efficient
07) Minimize style recalculations
08) Only run GPU-accelerated animations
09) Prioritize resource loading
10) Load pages in an instant

Details By: https://amp.dev/