No javascript, so no d3 on the page or any interactive graphics that can't be stuffed into an iframe. >One thing we realized early on is that many performance

No javascript, so no d3 on the page or any interactive graphics that can't be stuffed into an iframe. >One thing we realized early on is that many performance issues are caused by the integration of multiple JavaScript libraries, tools, embeds, etc. into a page. This isn’t saying that JavaScript immediately leads to bad performance, but once arbitrary JavaScript is in play, most bets are off because anything could happen at any time and it is hard to make any type of performance guarantee. With this in mind we made the tough decision that AMP HTML documents would not include any author-written JavaScript, nor any third-party scripts. https://www.ampproject.org/how-it-works/ https://www.ampproject.org/how-it-works/ http://www.niemanlab.org/2015/10/get-ampd-heres-what-publishers-need-to-know-about-googles-new-plan-to-speed-up-your-website/ http://www.niemanlab.org/2015/10/get-ampd-heres-what-publish...