Google Amp Pages are one of the more important web language changes we see coming with Google creating a new format for loading pages up to 4x faster. AMP stands for Accelerated Mobile Pages and is a Google project intended as an open standard for any publisher to have pages load quickly on mobile devices. It will be interesting to see how using AMP will affect mobile page rank which AMP is geared towards.
The official AMP website is here >> https://www.ampproject.org/
Also, here is a new tutorial page to get you started >> https://www.ampproject.org/docs/get_started/create.html
Here is an excerpt from a good summary article on AMP:
Google will begin sending traffic to AMP pages in Google Search as early as late February, 2016. Twitter will begin to experiment with linking to AMP content provided by publishers early in 2016. Pinterest, currently testing publisher AMP pages in their iOS and Android apps, found that AMP pages load four times faster and use eight times less data than traditional mobile-optimized pages. In addition, today we’re announcing that leading messaging apps LINE, Viber, and Tango will link to AMP content in early 2016 as well.
Excerpt from an Google AMP post:
Access to information is at the heart of Google’s mission. Unfortunately, today, the mobile web isn’t living up to the expectations people have for getting the information they need, particularly when it comes to speed. In fact, data shows that people abandon websites after just three seconds if the content doesn’t load quickly…
For more technical info on AMP Html:
AMP is a way to build web pages for static content that render fast. AMP in action consists of three different parts:
AMP HTML is HTML with some restrictions for reliable performance and some extensions for building rich content beyond basic HTML. The AMP JS library ensures the fast rendering of AMP HTML pages. The Google AMP Cache (optionally) delivers the AMP HTML pages.