How to get performance budgets right
Teams tend to reach for this after something has already gone wrong. The short answer to performance budgets is that it is mostly a sequence of small decisions, not one big one.
Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Check it against what you would want a competitor's site to get wrong.
What is actually at stake
A number in writing stops slow creep. Getting it slightly wrong is survivable. Ignoring it entirely is not. If two people in the business would answer this differently, that gap is the actual problem.
The steps
- Establish what you have today before changing anything
- Budget for total page weight and script size
- Enforce it automatically or it gets ignored
- Write down the decision so the next person does not re-litigate it
Enforce it automatically or it gets ignored. This is the sort of thing that compounds, quietly, in both directions. It is the sort of thing that looks like polish right up until it costs you an enquiry.
What to do next
The short version
Performance work is mostly subtraction, which makes it unpopular and effective. Three things worth confirming about performance budgets before you move on:
- Someone can say what the current setup is without going to look
- Enforce it automatically or it gets ignored — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If any of that sounds like a description of your current setup, it is fixable.