Why performance budgets matters more than it looks

This is one of those topics that looks small until it costs you something. Performance budgets is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Real-world numbers from actual visitors matter more than a score produced on a fast laptop. It rarely shows up as a line item, which is exactly why it slips.

The reason this keeps coming up

A number in writing stops slow creep. That sounds obvious written down. It is still the thing most often skipped. It rarely shows up as a line item, which is exactly why it slips.

Budget for total page weight and script size. In practice this is a scheduling problem more than a technical one. Doing this properly once is usually cheaper than doing it approximately three times.

Warning signs

Enforce it automatically or it gets ignored. There is a version of this that is over-engineered, and it is worth avoiding. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

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
• 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

Pick the one that would hurt most if it failed, and start there.