Course contentsShow
← Web Development
Lesson 1936 of 2,98235. Web Performance FundamentalsFree lesson

Metric-Based Budgets for Core Web Vitals

Setting thresholds for LCP, FID, and CLS that align with Google's good performance recommendations.

Metric-Based Budgets for Core Web Vitals

You'll learn how to set concrete performance thresholds for Core Web Vitals that keep your site aligned with Google's "good" performance benchmarks.

What Are Metric-Based Budgets?

Instead of just limiting file sizes or page weight, metric-based budgets focus on user experience outcomes. You set maximum allowed values for Core Web Vitals metrics—treating them like spending limits that your site cannot exceed. Think of it like a speed limit for your website: you're not just counting fuel (bytes), you're measuring how fast you actually go (user experience).

Setting Thresholds Aligned with Google

Google defines three performance tiers for each Core Web Vital. Your budget should target the "good" thresholds to ensure positive user experience:

LCP Budget (Largest Contentful Paint)

  • Good: ≤ 2.5 seconds
  • Set your budget at or below this threshold across all key pages.

INP Budget (Interaction to Next Paint)

  • Good: ≤ 200 milliseconds
  • Your budget should keep interaction delays minimal across the entire lifespan of the page.
  • Note on FID: Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) as a Core Web Vital on March 12, 2024; FID is deprecated. You must treat FID as a legacy/historical metric, so do not use or rely on FID thresholds as current ranking guidance. Point your focus toward the course's INP lessons for a deeper dive into measuring and optimizing the current metric.

CLS Budget (Cumulative Layout Shift)

  • Good: ≤ 0.1
  • Target zero unexpected layout shifts in your budget.

How This Works in Practice

You establish these numeric targets as non-negotiable limits during development. Before deploying changes, you verify that your site's 75th percentile measurements (representing most users) stay within these "good" ranges. If a new feature pushes LCP to 3.0 seconds, it violates your budget and needs optimization before going live.

This approach shifts your focus from "How much does this weigh?" to "How does this feel to users?"—the ultimate measure of web performance.

Key Takeaway: Metric-based budgets define maximum allowed values for LCP (≤ 2.5s), INP (≤ 200ms), and CLS (≤ 0.1), ensuring your site consistently delivers Google-defined "good" performance to real users.