Making Chromestatus.com a Lightning-Fast PWA
summary
Chromestatus is rebuilt as a fast, offline-capable PWA using Polymer 1.0, an app‑shell on App Engine, Service Worker caching and http/2 push/preload; first paint on a Nexus 5 over 3G is ~1.9s, full time‑to‑features ~3.8s and repeat views shave ~800ms. Server rendering plus lazy imports and iron-list cut initial DOM from ~4,400 nodes to ~53. Delivery uses a generated push manifest (via http2-push-manifest), measures with appmetrics.js, and scores ~95/100 on Lighthouse.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30Who am I
- 3:27Chrome Status History
- 6:53Chrome Status Improvements
- 9:04Chrome Status Metrics
- 12:10Deprecation Policy
- 18:54Lazy Load
- 19:59Performance Flags
- 21:33Avoid Web Fonts
- 23:55Make a Custom Icon Set
- 24:43Lazy Load NonCritical Components
- 25:34Measure Measure
related talks
31mFrom Website to Progressive Web App
23mPerformance Optimizations for Progressive Web Apps
35mDesigning Great Progressive Web Apps
51mProgressive Web Apps
32mPerformance Optimizations for Progressive Web Apps
51mOutrun the 🐻! Performance Optimizations for Progressive Web Apps
40mSupercharge the speed of your app with these PWAs' secrets!
24mPWA for Mobile Engineers
