Performance budgets, explained without the jargon

Most teams know this matters. Fewer have decided who owns it. Here is performance budgets without the vocabulary that usually surrounds it.

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. If two people in the business would answer this differently, that gap is the actual problem.

The short version

A number in writing stops slow creep. Small and consistent beats large and occasional here. Check it against what you would want a competitor's site to get wrong.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. There is a version of this that is over-engineered, and it is worth avoiding.

Budget for total page weight and script size. In practice this is a scheduling problem more than a technical one. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

A reasonable first step

Enforce it automatically or it gets ignored. The teams that handle this well are rarely the ones with the biggest budgets. Check it against what you would want a competitor's site to get wrong.

How to tell if yours is fine

Speed is a feature people notice only in its absence, and then they leave rather than complain. Three things worth confirming about performance budgets before you move on:

• Someone can say what the current setup is without going to look
• A number in writing stops slow creep — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.