Web Performance in 2018
summary
Sets a performance budget (interactive <5s on slow 3G) and builds a bank-like PWA using an app-shell that inlines critical HTML/CSS to ~50KB, loads modern JS with script type=module/no-module to save ~150KB across bundles, and uses dynamic import (webpack chunkName comments) to lazy-load features. Adds service worker for instant subsequent loads, web workers for heavy crypto off the main thread, measures with User Timing API, and observes real-device gains (example: ~900 KB/s, 40 ms latency considered).
AI-written summary · about
chapters (13)
- 0:00Start
- 2:39Constraints
- 7:35Stages of usage
- 8:34Importance of first load.
- 18:12Watch the size of your app shell
- 20:48Priority based loading
- 25:12Variable fonts features
- 26:09Demo
- 35:31Use cases
- 39:50Can the web do that?
- 40:50default to JSON
- 41:18Properly configure babel-preset-env
- 42:00depends on your target market and your browser support policy
related talks
26mWeb Performance in modern JavaScript world
23mPerformance Optimizations for Progressive Web Apps
51mAMP, PWAs, HTTP/2 and Service Workers: A New Era of Web Performance?
42mBuilding quick apps in 2018
22mModern Web Apps Performance Tricks with PWA and Vue
36mNobody cares about web performance. It's hard, expensive and unneeded
29mBringing Mobile Web back to Life
41mHow we make Web Apps lightning fast at Microsoft!
