Accelerated Mobile Pages: The good, the bad and the ugly
summary
Accelerated Mobile Pages (AMP) is a 2016 Google‑led system that speeds mobile by enforcing an AMP HTML subset, an AMP JS library, and serving pages from AMP Cache on Google servers. Claim: average mobile page loads 19s and >50% of users leave after 3s, so AMP yields noticeably faster loads and avoids layout shift by requiring width/height and disallowing arbitrary scripts. Tradeoffs: 50 KB CSS limit, sandboxed third‑party JS, near‑uniform publisher layouts, and preferential placement in the Top Stories carousel that drives SEO adoption.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker
- 2:23What is AMP
- 5:26Mobile web problems
- 7:14How AMP works
- 13:44Good parts of AMP
- 19:39Opinions on AMP benefits
- 24:09AMP harm to open web
- 28:56AMP and SEO controversy
- 32:09Future of AMP
- 34:21AMP wake-up call
- 35:46Conclusion and call to action
related talks
32mGetting 'Up To Speed' with Accelerated Mobile Pages
35mBuilding lightning-fast sites for the mobile web
29mCreate instant loading mobile web pages with AMP
06mAccelerating the Web through AMP
39mHow AMP HTML speeds up sites and improves business metrics
33mTowards the future with AMP
31mAMP in 2018 Still fast, still furious
34mRapidly Building Better Web Experiences with AMP
