3 ms·
Off-topic: I had to whitelist javascript on the AMP page to get it to load properly, where it promptly pulled down nine JS scripts: https://imgur.com/SkQgMOU h
by AdmiralAsshat 8y ago
Off-topic: I had to whitelist javascript on the AMP page to get it to load properly, where it promptly pulled down nine JS scripts:
https://imgur.com/SkQgMOU https://imgur.com/SkQgMOU
Wasn't the whole point of AMP to stop this crap?
- d4l3k 8y agoLoading multiple scripts from one site isn't actually a performance issue. With HTTP2 there's almost no overhead since they all get multiplexed as streams over the same connection. With server push you also don't even have to have to wait for multiple round trips. https://medium.com/@asyncmax/the-right-way-to-bundle-your-assets-for-faster-sites-over-http-2-437c37efe3ff https://medium.com/@asyncmax/the-right-way-to-bundle-your-as... AMP is more focused on UI responsiveness with things like having a fixed content layout so the page doesn't jump around when things load, as well as loading things asynchronously in the background so first paint is faster. Splitting up the JS so only the first paint JS loads immediately and then progressively upgrade the page is actually a good thing. It makes it immediately usable for slow connections. https://www.ampproject.org/docs/fundamentals/spec#performance https://www.ampproject.org/docs/fundamentals/spec#performanc...