Web Vitals Budget Planner
Set LCP, CLS, and INP targets for your page type and get a full resource budget breakdown with pass/fail indicators.
Page Type
Google Thresholds
Active Targets
Resource Budget Breakdown
Optimization Rules
Third-Party Script Budget
Frequently Asked Questions
What are Core Web Vitals?▼
Core Web Vitals are a set of real-world metrics Google uses to measure user experience: LCP (Largest Contentful Paint) measures loading performance, CLS (Cumulative Layout Shift) measures visual stability, and INP (Interaction to Next Paint) measures responsiveness. Google uses these metrics as ranking signals in Search. All three are measured in field data from real users via the Chrome User Experience Report (CrUX).
What is a performance budget?▼
A performance budget is a set of limits on metrics that affect website performance — page weight, resource sizes, number of requests, or Core Web Vitals scores. By setting a budget before building a feature, you create a constraint that forces you to optimize. Budgets should be tied to your user-facing targets (e.g., LCP ≤ 2.5s on 4G) and enforced in CI/CD using tools like Lighthouse CI or bundlesize.
How is the hero image size budget calculated?▼
The hero image size limit is estimated by assuming a 4G connection speed of approximately 10 Mbps (1.25 MB/s) and allocating a fraction of your LCP budget to the hero image download. Since the hero image is typically the LCP element, it must be downloaded and decoded before LCP fires. The formula used here is: LCP target (seconds) × 100 KB/s network allowance. Optimize with modern formats (WebP/AVIF), responsive srcset, and priority fetchpriority attribute.
What is INP and how does it differ from FID?▼
INP (Interaction to Next Paint) replaced FID (First Input Delay) as a Core Web Vital in March 2024. FID only measured the delay before the first interaction was processed. INP measures the latency of ALL interactions throughout the page lifecycle — clicks, taps, and keyboard inputs — and reports the worst percentile. A poor INP usually means too much long-task JavaScript blocking the main thread.
What causes CLS and how do I fix it?▼
CLS is caused by content that shifts after the initial render: images without explicit width/height, ads that expand, web fonts causing text reflow (FOUT), or dynamically injected content above existing content. Fixes: always set explicit dimensions on images and video elements, use font-display: optional or preload fonts, reserve space for ads with min-height, and avoid inserting content above the fold after page load.
Related Products
on GumroadDeveloper Productivity Bundle
Stop rebuilding the same setup every project. 51 VSCode snippets, 40 Git aliases, 5 Docker Compose stacks, 5 GitHub Actions workflows, 5 README templates, and a dotfiles kit. Set up a professional dev environment in under an hour.
Buy on Gumroad →AI Prompt Engineering Toolkit
58 structured prompt templates for Claude, ChatGPT, and Gemini — organized by use case. Code Review, Debugging, Documentation, Architecture, and 10 model-specific tips. Stop writing prompts from scratch.
Buy on Gumroad →Developer Cheat Sheet Bundle
10 print-ready cheat sheets for the tools developers use every day: Git, Docker, Linux CLI, SQL, Regex, HTTP Status codes, VS Code shortcuts, Bash scripting, jq/JSON, and Markdown.
Buy on Gumroad →You Might Also Need
Web Performance Checklist
Interactive web performance checklist covering images, fonts, JavaScript, CSS, caching, and server. Check off items to track your score out of 100 and export as Markdown.
Open free tool →
Web Vitals Analyzer
Analyze and score Core Web Vitals. Enter LCP, INP, CLS, TTFB, and FCP values to get good/needs improvement/poor ratings with optimization tips.
Open free tool →
Lighthouse Score Simulator
Estimate Lighthouse performance scores based on JS bundle size, CSS, images, TTFB, and render-blocking resources. Get LCP, FID, CLS, FCP estimates.
Open free tool →
More Free Tools
Related Articles
Web Vitals Optimization: Achieve Core Web Vitals Score 90+ in 2026
Step-by-step guide to achieving Core Web Vitals score of 90+ in 2026. Covers LCP, INP, CLS optimization techniques with code examples, measurement tools, and before/after benchmarks.
Web Performance and Core Web Vitals 2026: Complete Optimization Guide
Complete guide to Core Web Vitals optimization in 2026. Covers LCP, INP, CLS, TTFB optimization with real code examples. Includes Next.js, React, Vite, Cloudflare Workers, and backend optimization strategies for achieving 90+ Lighthouse scores.
Web Performance 2026: INP, Core Web Vitals & Lighthouse CI
Master web performance in 2026: INP replacing FID, LCP and CLS optimization, Lighthouse CI in GitHub Actions, RUM with web-vitals.js, and setting performance budgets to keep your site fast.
Web Performance Optimization: Improve Your Core Web Vitals in 15 Steps
15 actionable web performance optimization techniques to improve LCP, CLS, and INP (Core Web Vitals). Real code examples, measurement tools, and before/after results.
JavaScript Bundle Size Optimization: From 2MB to 200KB — A Practical Guide
Practical techniques to reduce JavaScript bundle size from megabytes to kilobytes. Covers tree shaking, code splitting, dynamic imports, bundle analysis, and tools that actually work in 2026.
Enjoying this tool? Get more like it.
Weekly developer tool guides, productivity playbooks & AI tricks. Free. No spam.
Unlock AI-Powered Dev Tools
- ⚡ AI Code Review, Doc Generator & SQL Builder
- ⚡ All premium templates & early access
- ⚡ Member discounts on Gumroad products
$9/mo after trial · Cancel anytime
Want the full toolkit?
Get DevPlaybook Pro
Every template, guide, boilerplate, and automation script in one bundle. 13 premium products — grab them all at once and save big.
MIT licensed · Instant download · No subscription
See what's included → Browse all deals →