I will add though that despite what it may sound like, I'm still not entirely sold on AMP myself. My main issue with it is that it the spec still contains [thi

I will add though that despite what it may sound like, I'm still not entirely sold on AMP myself. My main issue with it is that it the spec still contains [this line][1]: > AMP HTML documents MUST > [...] > * contain a <script async src="https://cdn.ampproject.org/v0.js"></script> https://cdn.ampproject.org/v0.js"></script> tag inside their head tag The actual specification requiring JavaScript to be loaded into your page from any one particular server is unacceptable IMO. Hopefully this is fixed in future updates to the spec. My other problem with it is much more minor; I just don't like the idea of serving a "special" version of my site just for mobile. I'm very much a fan of responsive design, and I'd prefer to just serve one version of my site that looks and works great no matter what device or internet connection you're viewing it with. [1]: https://www.ampproject.org/docs/reference/spec#scrpt https://www.ampproject.org/docs/reference/spec#scrpt