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. When a pull request pushes a metric over budget, the build fails, which turns performance from an audit into a daily constraint.
No account needed · Scored in under a minute against a senior rubric
What does Performance Budget mean in practice?
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 do interviewers ask about Performance Budget?
Interviewers ask about performance budgets to see whether you proactively prevent performance regressions rather than reactively fixing them. It shows a quality-engineering mindset.
What does Performance Budget look like in a real project?
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.
How should you talk about Performance Budget in an interview?
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.
Go Deeper on Performance Budget
Know the term. These are the courses that turn the concept into something you can demonstrate.
Which terms relate to Performance Budget?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining performance budget and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account