Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

AMP puts 100KB of JavaScript in the initial render path, and a bunch of CSS. That doesn't mean that other sites cannot be worse but it means that there's no way to make an AMP page which doesn't require transferring at least that much data.

I notice this fairly regularly in marginal network coverage (subway tunnels/platforms) where AMP pages load no faster than any well-optimized site unless the stars are aligned and you actually get a cache hit.



Keep in mind that this AMP JS library is being loaded from the CDN only once for all AMP pages, then cached in the browser.


If that works. In my experience, you're eating the initial DNS lookup, connection and SSL setup, etc. more frequently than expected.

The general rule about inclining render-blocking resources matters here, too.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: