Once you go PRPL...
summary
PRPL means concrete steps not promises: push critical assets with preload/prefetch and HTTP/2 server push, precache and runtime cache with a service worker (Workbox can run generate:sw as part of builds), lazy-load routes and monitor bundles (examples range 4–200 KB), avoid pushing unused files, use handlers like networkFirst for APIs, note 73% report slow mobile pages and measured time‑to‑interactive often hits 16–19s so aim for far lower first paint and fast repeat visits via cache + precise pushes.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:45HTTP/2 Server Push
- 9:59Pushing too much
- 10:23Pushing unused assets
- 10:40Cache?
- 11:25Service workers
- 15:42DYNAMIC CONTENT
- 19:56BUNDLES
- 22:04WEBPACK BUNDLE ANALYZER
related talks
21mThinking PRPL
33mHoussein Djirdeh - SeattleJS Conference 2017
32mIt’s Time to Join the Fantastic Four of the Web
40mSupercharge the speed of your app with these PWAs' secrets!
34mFast Nuxt.js Applications with PRPL Pattern
45mScaling with PWA
09mAdvanced PWA patterns
32mPractical Performance Tips Building Progressive Web Apps