Performance
The performance budget that actually held
A budget nobody enforces is a wish. We made it fail the build.
Nadia Osman
We had a performance budget for two years and blew through it every quarter. Then we wired it to CI and it held for eleven months straight.
The budget had never been the problem. The problem was that exceeding it produced a warning in a dashboard nobody opened, three days after the deploy.
Make it a failure
We moved the check into the pipeline and made it exit non-zero. The first week produced four failed builds and a great deal of complaining. The second week produced none.
A budget that only warns is documentation. A budget that fails is a budget.
The bundle is now within nine kilobytes of where it was a year ago, across roughly two hundred merged pull requests.