Page performance after load
summary
Claims that post-load experience hinges on measurable smoothness and responsiveness and that optimizing them beats vague “examples.” Specific tools and techniques include avoiding a constant RAF loop (it forces unnecessary frames), using performance.measure and custom entries shipped via performance.getEntriesByType, the PerformanceObserver frame-entry proposal, offloading work with Comlink and Paint Worklets, serving modern JS with module/nomodule, following RAIL targets (100 ms or up to 1 s), and a study showing memory beyond a threshold increases Total Blocking Time.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:25Loading Performance
- 4:30Smoothness
- 6:30Responsiveness
- 9:06What Techniques Can Help with Typical Post Load Performance Problems
- 11:05Reduce Your Memory Usage
- 11:31General Conclusions
- 12:10Monitor for Memory Leaks
- 12:20To Find and Fix Memory Leaks
- 12:35Only Load What Is Needed
- 13:02Shipping Modern Code
- 13:35Recap
related talks
19mPerceived Performance, And Why It Matters
22mNew Perspectives on Performance
50mWeb Performance APIs You (probably) Didn't Know Existed
32mEverything you need to know about Web Performance
44mFast but not Furious: Debugging User Interaction Performance Issues
30mPerformance as a Religious Experience
39mPerformance Beyond Page Load
16mCoding Session: Stunning Performance