ok, lets take a look at https://www.ampproject.org/ https://www.ampproject.org/ which is a valid amp document. page speed insights https://developers.googl

ok, lets take a look at https://www.ampproject.org/ https://www.ampproject.org/ which is a valid amp document. page speed insights https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.ampproject.org%2F mobile 68/100 desktop 59/100 webpagetest.org https://www.webpagetest.org/result/151214_DW_X81/ first byte: 0.225s start render: 0.816s speed index: 3396 compare it to one of my sites where we did some speed optimization (wordpress based / responsive design) page speed insights https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.veganblatt.com%2Fnatuerliche-antibiotika mobile 71/100 (mostly thx to jquery) desktop 90/100 page speed insights https://www.webpagetest.org/result/151214_4T_X91/ first byte:0.145s start render: 0.712s speed index: 797 Amp is not per-se fast(er). But for this, they crippled HTML5, basically want us to forgo responsive design (responsive is not (only) about mobile), oh, and buy into another google dependency. and why? just because publishers are too lazy to make sites fast, and too dependent on third party crap (ads & an unbelievable amount of other crap). As a publisher and user, I hope Amp succeeds in disrupting the way publishers publish mobile. As a developer: OMFG, they throw the baby out with the bathwater. (they = Google, baby = html5, bathwater = internet)