Web Vitals / Performance Budget Calculator

Enter a rough performance budget spec — total JS/CSS size, image count and average size, third-party script count, web fonts — against editable pass/warning thresholds based on common performance-budget guidance. Estimates which categories are likely to hurt LCP, TBT/INP, or CLS. A static budget-threshold estimator, not a real Lighthouse/CrUX measurement.

This is a budget-threshold estimator, not a real measurement. Enter rough page-weight numbers and it flags which ones fall outside commonly cited performance-budget guidance — it does not fetch, load, or measure any actual page. For real field/lab data use Chrome UX Report, Lighthouse, or WebPageTest.
Total JS (gzipped)
Affects: TBT/INP
Pass
Parse/compile/execute cost blocks the main thread — the classic 170KB "good" budget comes from Addy Osmani's original performance-budget guidance; 300KB is a commonly cited looser modern ceiling.
Total CSS (gzipped)
Affects: LCP
Pass
Render-blocking stylesheets delay first paint and, in turn, the largest contentful paint.
Number of images
Affects: LCP, CLS
Pass
More image requests compete for bandwidth on the critical path; images without reserved dimensions also risk layout shift.
Average image size
Affects: LCP
Pass
Large hero/above-the-fold images are very often the element Chrome reports as the LCP candidate.
Third-party scripts
Affects: TBT/INP
Pass
Ads, analytics, chat widgets, and tag managers add parse/execute cost you don't directly control and often load synchronously.
Web fonts
Affects: CLS, LCP
Pass
Each additional font file is another render-blocking (or swap-triggering) request; FOIT/FOUT swaps can shift layout.
LCPPass
TBT/INPPass
CLSPass
Total image weight
1200 KB
Est. total page weight
1420 KB
All budgets within their "good" threshold — estimated low risk of Web Vitals issues.

Thresholds default to commonly cited performance-budget guidance (e.g. ~170KB gzipped JS as a historically "good" ceiling, ~300KB as a looser modern one) but are fully editable — every team's real budget depends on target devices/networks and should be tuned with real Lighthouse/CrUX data, not just this calculator.

Web Vitals / Performance Budget Calculator

Enter a rough performance budget spec — total JS/CSS size, image count and average size, third-party script count, web fonts — against editable pass/warning thresholds based on common performance-budget guidance. Estimates which categories are likely to hurt LCP, TBT/INP, or CLS. A static budget-threshold estimator, not a real Lighthouse/CrUX measurement.

Common uses

  • Check if a 450KB JS bundle is within a performance budget
  • Estimate the CLS risk from too many web fonts
  • Load a "heavy SPA" preset and see which budgets fail

Also searched as

  • performance budget calculator
  • is my js bundle size too big
  • estimate lcp risk from page weight
  • cls risk web fonts
  • web performance budget thresholds
  • third party scripts performance impact estimate
  • tbt inp budget estimator
  • javascript bundle size budget 450kb

Frequently asked questions

How do I check if my page fits a performance budget?

Enter total JS and CSS size, image count and average image size, third-party scripts and web fonts, and compare against editable good/warning thresholds.

Does this measure real Core Web Vitals?

No. It is a static budget-threshold estimator, not a Lighthouse or CrUX measurement.

Can I change the thresholds?

Yes, thresholds are editable, and example presets such as a heavy SPA are available.

Is my data uploaded to a server?

No. This tool runs entirely in your browser — your input is processed locally on your device and is never uploaded or stored on a server.