Specialized Testing

What Is Performance Budget?

A performance budget is a set of measurable limits on web performance metrics (such as page load time, bundle size, or Core Web Vitals) that a team commits to not exceeding, enforced through automated checks.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

Performance budgets translate vague goals like "the site should be fast" into concrete, enforceable thresholds. Common budget metrics include Largest Contentful Paint (LCP) under 2.5 seconds, First Input Delay (FID) under 100 milliseconds, Cumulative Layout Shift (CLS) under 0.1, total JavaScript bundle size under 200KB, total page weight under 1MB, and number of HTTP requests under 50.

Budgets are most effective when enforced automatically. Tools like Lighthouse CI, bundlesize (npm package), and webpack-bundle-analyzer can fail builds or PR checks when a budget is exceeded. This prevents the gradual performance creep that occurs when individual changes are "only a few KB" but accumulate over months into a bloated, slow application.

For QA engineers, performance budgets provide testable acceptance criteria for every change. Instead of subjectively judging whether a page "feels fast," you compare metrics against the budget. Performance testing becomes a pass/fail gate rather than an occasional audit.

Why Interviewers Ask About This

Interviewers ask about performance budgets to see whether you proactively prevent performance regressions rather than reactively fixing them. It shows a quality-engineering mindset.

Example Scenario

A team sets an LCP budget of 2.5 seconds and a JavaScript budget of 200KB. A developer adds a charting library that pushes the JS bundle to 245KB. The Lighthouse CI check fails the PR. The developer switches to a lighter charting library (85KB), and the PR passes the budget check.

Interview Tip

Name specific metrics (LCP, CLS, bundle size) and tools (Lighthouse CI, bundlesize). Explain how you would integrate performance budgets into a CI pipeline to prevent regressions automatically.