Supercharge the speed of your app with these PWAs' secrets! ⚡
summary
Claims concrete outcomes: specific caching patterns, measured fixes, and a prototype link. Performance testing uses tested 15 PWAs with web.dev (Lighthouse) and finds recurring faults: long critical-request chains, huge transfer sizes, bulky JS and render‑blocking CSS. Prescribed remedies include cache-first / network-first / stale-while-revalidate strategies, server-side rendering for the shell plus client-side hydration, code‑splitting, lazy images, WebP/AVIF, a budget.json, and a Rust/WASM generator PWAFire generator for Rust that integrates service worker and manifest.
AI-written summary · about
chapters (23)
- 0:00Intro
- 2:44Agenda
- 4:00The heart of PWAS
- 5:58How do you render the app?
- 6:23How do you cache the app?
- 7:05Where does the data live?
- 7:28Caching strategies
- 8:54The app shell + content = the app
- 9:43SSR (Shell) + CSR (content)
- 10:12SSR (shell) + fetch content
- 10:44CSR (shell) + CSR (content)
- 13:05How does JavaScript run?
- 13:55How does Web Assembly compare?
- 14:49How does Web Assembly work?
- 15:44WOZ - (PWAA) generator for Rust
- 17:15The performance experiment
- 18:00Avoid chaining critical requests
- 19:22Keep request counts low and transfer sizes small
- 19:54Minimize main-thread work
- 20:40Defer offscreen images
- 21:15Properly size images
- 22:02What is the impact of styles for the app speed?
- 22:28How to keep a progressive style?
related talks
40mSupercharge the speed of your app with these PWAs' secrets!
28mSupercharge the Speed of your App with these PWAs Secrets!
55mPWA Fundamentals: websites with superpowers
24mPWA for Mobile Engineers
51mAMP, PWAs, HTTP/2 and Service Workers: A New Era of Web Performance?
51mPWA Challenges
22mModern Web Apps Performance Tricks with PWA and Vue
45mScaling with PWA