> AMP serves a critical strategic purpose: it severely disincentivizes crappy, JS-heavy websites on search results and as a result makes people less likely to install adblockers.
The slowest, most resource-intensive web sites I visit are, in order: Slack, GMail, and Google Play Music. If Google wants others to take web performance seriously, they should start with their own internal stuff.
Are Slack, GMail, Google Play Music websites or web applications? AMP is not applicable to sites/applications that remain open in your tabs all the time. I think it's more applicable to pages you open, consume the information and close the tab in couple of minutes.
Let's say Google Maps then. It will show up in search results, artificially at the top because of close integration, but performs incredibly poorly. I can't take their claims about AMP being about performance seriously when they do not seem to make any attempt at optimizing the stuff that they put on top.
Sorry missed this. I don't consider Google Maps a website as well. Specially not a static website that AMP is targetting. You move around in maps, give it input and it gives you a different output.
The slowest, most resource-intensive web sites I visit are, in order: Slack, GMail, and Google Play Music. If Google wants others to take web performance seriously, they should start with their own internal stuff.