Performance Optimizations for Progressive Web Apps
summary
Shows a production Xfinity xFi progressive web app built with Google Polymer and the PRPL pattern and demonstrates concrete wins not platitudes. Uses Chrome DevTools & Lighthouse, the user timing API and Comcast’s surf library to measure; applies code‑splitting, defer scripts, dns prefetch, service workers and CSS/DOM fixes. Replaces heavy libs like moment with smaller alternatives. Claims include shrinking initial payload toward the 130–170 KB budget and cutting desktop startup from about 6s to 2.3s and real‑world median from 21s to 15s.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:46What is our Goal?
- 18:01Code splitting
- 18:44CRITICAL PATH
- 21:32An Optimal DOM Tree
- 29:48Discipline
related talks
51mOutrun the 🐻! Performance Optimizations for Progressive Web Apps
23mPerformance Optimizations for Progressive Web Apps
35mImprove Your Web Application Using Progressive Web Metrics
33mEnd to End Apps with Polymer
32mPractical Performance Tips Building Progressive Web Apps
51mProgressive Web Apps
27mProgressive what apps?
39mProgressive web apps with Polymer
