←  All terms
P
Performance

Performance Budget

A performance budget sets measurable limits for website resources, loading times, or user-experience metrics.

A performance budget sets measurable limits for website resources, loading times, or user-experience metrics. Optimization becomes meaningful when real-user data, repeatable lab tests, and an explicit performance budget are used together. The concept is closely related to Website Performance and Core Web Vitals.

Read more

Website Performance

Core Web Vitals

Quality Assurance

Monitoring

FAQ

Performance Budget

How does a performance budget differ from a one-time audit?
An audit is a snapshot with a list of measures, while a budget is a lasting limit that constrains every future change. The audit finds existing problems; the budget prevents new ones. Without a budget, optimized pages often degrade again over time as scripts, images, and tracking tags accumulate.
What happens when a performance budget is exceeded?
Ideally an automated check in the build pipeline trips and either blocks the release or forces a decision. Two paths follow: optimize the offending element or remove something else from the budget. A budget without consequences for overruns remains a mere recommendation.
How is a performance budget set?
The starting points are the current state and competitor comparisons, from which targets per page type and device follow. Business goals help too: where load time affects conversions, stricter limits apply. Design, engineering, and marketing should share the budget, otherwise it gets bypassed at the first feature request.
Which metrics work well for a performance budget?
Three groups work well: quantity limits such as total size, JavaScript, and image weight; timing values such as LCP; and user metrics such as INP and CLS. The Core Web Vitals thresholds (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1) make good starting values. Resource limits can be checked early, user metrics only in the field.