Hacker News Reader

Comment by matthewmacleod | Hacker News Reader

I've thought about it, but I'm obviously missing the point completely here. Can't publishers already create high-performance web pages using non-bastardized HTML? Aren't the vast majority of performance issues on the mobile web due to publishers misusing analytics and advertising, rather than anything that would be solved by this project?

View on HN

Analytics and advertising are core parts of how publishing works as a business, but they often seem to be implemented without thinking about speed.

AMP makes it harder (impossible?) for them to misuse analytics and advertising by putting those features into their own elements in the page and preventing arbitrary JS.

Part of AMP is caching on Google's servers (and others). That can't quite be done individually.

I guess I'm not really seeing why that's the case, though; what prevents 'Google and others' from providing caching existing web content, subject to publishers making their content effectively cacheable?

Since this exclusively uses web tech there is absolutely nothing publishers cannot do today.

A big problem is that they don't and AMP is as much about fixing that as about technology.

Google has provided PageSpeed Service for a long time.

Google shut down the PageSpeed Service on 2015-08-03:

https://developers.google.com/speed/pagespeed/service/Deprec...

AMP pages can also only use Javascript as part of web components that have been added to the open source AMP project.

Reply on news.ycombinator.com