1. Web Performance Budgets advanced

    A booking site enforces a performance budget in CI: the main bundle must stay under 300 KB compressed. The budget has passed on every build for a year. Field data shows the median page is 2.8 MB of JavaScript and interaction latency has doubled. Review the budget. What is wrong with it, and what would you replace it with?

    3 min answer performance-budgetthird-partyrumgovernance
  2. Web Performance Budgets intermediate

    A booking site sets a JavaScript budget. Six months later it is exceeded on every page. What was missing?

    1 min answer performance-budgetciregressionownership
  3. Web Performance Budgets beginner

    A build gate caps a route's JavaScript at 280 KB and has passed every build for a year. DevTools reports 1.1 MB of script for the same route, and a mid-range Android phone spends roughly 1.4 s executing before the first tap registers. Both numbers are correct. Why do they differ by about four times, and which one should the budget be written in?

    2 min answer performance-budgetcompressionparse-costmain-thread
  4. Web Performance Budgets advanced

    A platform team wants a pull request to fail when a route's field Interaction to Next Paint at the 75th percentile regresses. The route gets about 4000 page views a day and real-user monitoring samples 10% of sessions. Roughly how long before a shift from 25% to 30% of interactions above 200 ms is detectable, and what does that rule out?

    3 min answer rumsample-sizeperformance-budgetstatistics
  5. Web Performance Budgets advanced

    Pinterest rebuilt its mobile web experience in 2017 and reported time to interactive falling from about 23 seconds to 5.6 seconds, with the core bundle cut from roughly 650 KB to 150 KB against an old experience shipping over 2.5 MB of JavaScript. What was actually wrong, what did the rebuild change, and where would copying it be a mistake?

    3 min answer pinterestperformance-budgetjavascriptmobile-web