Why are web applications slow, and what to do about it
summary
A concrete claim backed by tools and measurements JavaScript is the main culprit for slow sites shown by a custom tool called Performance Insights that queries Lighthouse and finds top 50 e commerce sites mostly red deleting JavaScript raises some scores to 96 Third party tags move off the main thread using Partytown by proxying DOM to a web worker First party cost can be cut by resumable frameworks like Wiz and Quick which serialize server state to HTML and aim for O(1) startup with ~1KB initial JS
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:15Why web performance matters
- 2:37Developers vs tooling blame
- 4:00JavaScript growth impact
- 6:28JavaScript bottleneck
- 8:12Third-party JS in web workers
- 9:37First-party JS overhead
- 10:39Resumable web apps need
- 12:03Server-side to frameworks
- 13:27Hydration white screens problem
- 14:31Resumable frameworks examples
- 15:55What makes frameworks resumable
- 17:39Resumable systems startup delays
- 18:42Future of resumable frameworks
- 19:47Prefetching progressive loading
- 20:29Startup vs runtime performance
- 21:11Q&A
related talks
01h 23mWhy Slow?
37mSecret Shortcuts of Loading Web Performance
01h 03mSpeed up your Web Application
29mClient Says Your Awesome Web App Works Slowly. Now What?
48mJavaScript in Browser Performance
27mHow we make Web Apps lightning fast at Microsoft
41mHow we make Web Apps lightning fast at Microsoft!
22mUnderstanding Resumability