Revisiting Performance Budgets
summary
A practical playbook that shifts performance budgets from aspirational goals to regression detectors: use RUM and synthetic side-by-side, set thresholds to the worst recent value over 2–4 weeks, and alert when exceeded; benchmark against SpeedCurve industry dashboards; watch long tasks and image weight as proxies for third‑party bloat. Concrete examples include Shopzilla’s 1.2 seconds → 12% lift then regression, an LCP discovery problem on ~39% of pages, and a 2 second start‑render budget pattern.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:43Welcome
- 1:53Performance
- 2:50Benchmarks
- 7:00Maintaining
- 8:10What is a Performance Budget
- 10:05Real User Monitoring Tools
- 13:05The Unicorn
- 14:51Minimum Viable Budget
- 17:39Page Loading
- 21:06Can I use the page
- 25:12How the page feels
- 31:44Budget thresholds
- 32:38Creating budgets to fight regression
- 36:02Cheat Sheet
- 36:23Budget Management
- 38:40Performance Budgets for Every Metric
- 39:19Do You Need Performance Budgets for All Pages
- 42:11Summary
- 43:49Footnote
related talks
57mAn Opinionated Guide to Web Performance Budgets
48mPerformance Budgets: the What, Why and How
36mTaking the Guesswork out of Performance Budgets
50mCreating Performance Impact in a Changing Tech Landscape
12mPerformance In Context
24mHow To Manage Performance Like a Product
34mThe Business of Performance, a Panel discussion
37mTracking Regressions and Improving UI Performance using Benchmarking Approach