AMP, PWAs, HTTP/2 and Service Workers: A New Era of Web Performance?
summary
Shows a concrete implementation combining AMP, HTTP/2 (with server push), CDN/edge caching, and a service worker to cut full page load from ~7s to ~2s and report a ~15% conversion lift in a cited case study. Uses a service worker for offline cache, background sync, and IndexedDB for local checkout state, and builds a PWA with homescreen install, push notifications and offline reload to demonstrate the performance and revenue improvements.
AI-written summary · about
chapters (31)
- 0:00Web performance challenges
- 1:47Server bottleneck
- 4:36JS blocking rendering
- 7:17Google’s standards
- 9:50Google & Facebook cases
- 13:11Offline with Service Workers
- 14:35Service Workers sync
- 17:09Native-like web apps
- 19:01Network latency
- 21:55Content delivery
- 23:08Browser optimizations
- 24:27HTTP/2 push
- 25:13CDNs and caching
- 26:47Service Workers limits
- 28:36SW resource management
- 30:05Service-based web apps
- 31:33Cloud auto-scaling
- 32:19Metrics and UX
- 33:27Visual completeness
- 34:10Push & caching
- 35:10PWAs & performance
- 37:22Browser engine updates
- 38:57Performance literature
- 40:15Mobile performance
- 41:18Custom JS speed
- 43:48Browser differences
- 44:45App performance
- 45:56Google’s CDN impact
- 47:19Traffic optimization
- 48:08Real-time content
- 50:06Summary & future
related talks
55mFuture of Web
55mPWA Fundamentals: websites with superpowers
28mSupercharge the Speed of your App with these PWAs Secrets!
46mWeb Performance in 2018
24mPWA for Mobile Engineers
40mSupercharge the speed of your app with these PWAs' secrets!
25mSupercharge the speed of your app with these PWAs' secrets! ⚡
24mPWA All The Things!