Core Web Vitals Budget Planner
Plan first-view limits for JavaScript, CSS, images, fonts and third-party scripts. Compare supplied LCP, INP and CLS with your targets and save the assumptions.
Core Web Vitals Budget Planner: how to use it
- Choose a device profile, page complexity and archetype. Enter the LCP, INP and CLS targets and the asset counts and repeat cache assumption.
- Enter any supplied readings and first-view byte figures. Select the measurement scope, generate the plan and compare the per-asset and metric headroom.
- Copy or download the JSON plan. Use the cold allowances as release guardrails and compare them with new observations.
Limits and notes
A scenario estimate for one device and page type. Transfer uses decimal KB. Device speeds, timing reserves and interaction allowances are model assumptions. Supplied readings are compared locally without generating field data.
How your privacy works →Core Web Vitals Budget Planner: common questions
Does a higher cache hit rate change the cold budget?
No. The cold allowance assumes none of the listed transfer is cached. The repeat estimate applies your hit rate to the allocated assets and keeps the unallocated amount.
What is the difference between field p75 and a synthetic reading?
Field p75 is the 75th percentile of an observed page and device group. A synthetic or single-run value describes one controlled observation. Choose the label that matches your data.
Is the CLS target converted to KB?
CLS is a unitless stability score. The tool compares a supplied CLS with the target and gives layout checks for hero images and fonts.