Supercharge the Speed of your App with these PWAs Secrets!
summary
Service worker helps only after first load and caching must be chosen deliberately: cache-first vs network-first vs race and server+client rendering often gives the best first view plus dynamic updates. Performance audit of 15 PWAs audited with web.dev surfaces top fixes: break critical request chains, trim and code-split JS, and defer offscreen images. Image work alone cut a tested app’s load from ~18s (lazy load) to ~17s (proper sizing) to ~14s (next‑gen formats). Also shows PWAA: Rust PWA generator and Blazor WebAssembly as concrete Wasm options.
AI-written summary · about
chapters (6)
- 0:00Introduction to PWAs
- 1:25Why speed matters in PWAs
- 2:50Caching strategies and design patterns
- 13:49Progressive WebAssembly apps
- 17:50Performance experiment results
- 26:24Summary and key takeaways
related talks
25mSupercharge the speed of your app with these PWAs' secrets! ⚡
40mSupercharge the speed of your app with these PWAs' secrets!
51mAMP, PWAs, HTTP/2 and Service Workers: A New Era of Web Performance?
45mScaling with PWA
55mPWA Fundamentals: websites with superpowers
35mDesigning Great Progressive Web Apps
39mPWA & Front-end Frameworks
24mPWA for Mobile Engineers