Skip to the content
searchboar.

Crawling and indexing

Performance budget: meaning, examples and practical use

A performance budget is a set of predefined limits used to evaluate website development and changes. It can constrain JavaScript weight, image size or deterioration in a measured experience metric, with the aim of deliberately protecting usability.

Also known as: Teljesítménykeret

At a glance

  • Choose limits using the audience and measured starting point.
  • Transfer size and execution time can need separate limits.
  • Evaluate exceptions explicitly rather than silently raising the threshold.
On this page
A page resource bundle weighed against a clearly marked allowance.
Conceptual illustration: a page resource bundle weighed against a clearly marked allowance.

Which limits can be useful?

A page type might have a maximum image size, compressed JavaScript allowance or metric target under fixed test conditions. The introduction to performance budgets explains the value of early, deliberate constraints. No single file-size limit suits every website.

How can a budget be verified?

Specify the page type, environment and unit. Transferred and uncompressed size are different quantities. Comparing laboratory results requires consistent conditions. An automated check can flag changes that exceed the agreed allowance.

Example: a glossary article

Imagine a team setting a resource budget for article pages. A proposed animation exceeds it. The team assesses whether the animation improves understanding, whether a simple diagram could replace it or whether revising the allowance is justified. The trade-off is considered rather than hidden.

What is not a useful budget?

“Make it fast” is an untestable wish. But a strict numerical limit is also unhelpful if it makes the product unusable. Real-user observations and the actual task help judge the compromise. A budget should prevent accidental regressions while still allowing deliberate improvements.

Sources

  1. web.dev: Performance budgets 101