Welcome to WebmasterWorld Guest from 188.8.131.52
Google will begin sending traffic to your AMP pages in Google Search early next year, and we plan to share more concrete specifics on timing very soon. Google's (AMP) Accelerated Mobile Pages Project Starts Early 2016 [amphtml.wordpress.com]
[edited by: FranticFish at 7:48 am (utc) on Nov 27, 2015]
Well, here's what I'm going to do. Nothing for the moment
if the idea is to restrict HTML, then surely that's a job for mobile browsers,
which is clearly a version of the article stripped down for responsive display on smart phones
Last, it seems to be 'mobile only', not 'mobile upwards' and that in itself seems like a huge step backwards.
You can build one responsive front end or a front end for every smartphone on the market. Your choice.
If I was going to go to that much trouble then I'd rather device-sniff than adopt a different coding standard. Work off one code base, serve different stylesheets and assets, less assets overall, omit certain parts of the page etc.
The BBC site is an interesting example but I don't think it's a representative example
limited set of HTML served to mobile browsers
The runtime may choose to delay or prioritize resource loading based on the viewport position, system resources, connection bandwidth, or other factors. The amp-img components allows the runtime to effectively manage image resources this way.
So, how fast is AMP HTML? Pretty fast. In a sample of pages our early partners created we are seeing performance improvements measured through Speed Index between 15% and 85%. This was measured with a simulated 3G connection and a simulated Nexus 5 device. The best part is you don't need to be a performance expert to get this; best practices are baked right in. And as we optimize AMP HTML in the future, all pages benefit.
1. Provide a way for Web developers to build their own, fully-featured DOM elements. Though it was long possible to create DOM elements with any tag names in HTML, these elements weren't very functional. By giving Web developers the means to both inform the parser on how to properly construct an element and to react to lifecycle changes of an element, the specification eliminates the need for DOM-as-a-render-view scaffolding that has to exist today in most web frameworks or libraries.
2. Rationalize the platform. The specification ensures that all of its new features and abilities are in concert with how the relevant bits of the Web platform work today, so that these new features could be used to explain the functionality of existing Web platform features, such as HTML elements.