Website Performance & Core Web Vitals

Core Web Vitals 2026: The Ranking Metrics

Google discontinued "PageSpeed" as a ranking signal and replaced it with three user-centric metrics: LCP, INP, and CLS. Your Lighthouse score is irrelevant. Your CrUX field data is everything.

The 3 Core Web Vitals

LCP

Largest Contentful Paint

✓ Good: ≤ 2.5s✗ Poor: > 4.0s

Time until the largest above-the-fold element (image or text block) fully renders. The primary load speed signal.

Key Fixes

  • Preload the LCP image in <head>
  • Serve images as AVIF/WebP
  • Use Edge CDN to reduce TTFB
  • Remove lazy loading from LCP element

INP

Interaction to Next Paint

✓ Good: ≤ 200ms✗ Poor: > 500ms

Responsiveness to user interactions (clicks, taps, keyboard input). Replaced FID as the interactivity Core Web Vital in 2024.

Key Fixes

  • Break up long JavaScript tasks (> 50ms)
  • Defer non-critical scripts
  • Avoid synchronous XHR blocking main thread
  • Use web workers for heavy computation

CLS

Cumulative Layout Shift

✓ Good: ≤ 0.1✗ Poor: > 0.25

Visual stability — how much content unexpectedly shifts position during load. Scored 0-1+; lower is better.

Key Fixes

  • Set explicit width/height on images
  • Reserve space for dynamic ad slots
  • Use font-display: swap for web fonts
  • Avoid inserting content above existing DOM

The Lab vs. Field Data Trap

Google ranks you based on Field Data (CrUX) — not Lighthouse scores. It is entirely possible to have a Lighthouse score of 95 and a "Poor" CrUX classification simultaneously.

A site that scores "Poor" in CrUX for LCP faces a confirmed Page Experience ranking penalty. A site with a Lighthouse score of 60 but "Good" CrUX field data faces no such penalty. Always prioritize your GSC Core Web Vitals report over any synthetic lab tool.

Mobile-First Is the Only Standard

Google's CrUX data is segmented by device type. For sites without sufficient desktop traffic, CrUX defaults to the mobile P75. A site that passes CWV on desktop but fails on mobile has a poor Page Experience classification. Always test on a throttled mobile connection — a mid-range Android device on a 4G network is the benchmark device.

Murkuz AI SEO Scorecard Criteria

Target Score: 93/100

LCP Threshold

Largest Contentful Paint under 2.5 seconds at mobile P75 in CrUX field data — not Lighthouse lab scores.

INP Responsiveness

Interaction to Next Paint scores under 200ms. No long tasks (>50ms) blocking the main thread for critical interactions.

CrUX Validation

GSC Core Web Vitals report shows 100% 'Good' URLs for LCP, INP, and CLS across both mobile and desktop segments.

Frequently Asked Questions

What is the difference between Lab Data and Field Data for Core Web Vitals?

Lab Data (also called Synthetic Data) is collected in a controlled environment by tools like Lighthouse, PageSpeed Insights, and WebPageTest. These tools simulate a page load under defined conditions (device type, network speed, CPU throttling). Field Data (also called Real User Monitoring / RUM) is collected from actual users visiting your site via the Chrome User Experience Report (CrUX). Critically, Google's ranking algorithm uses ONLY Field Data from CrUX for the Page Experience ranking signal. Your Lighthouse score is a useful diagnostic tool, but Google does not rank you based on it.

How do I check my Core Web Vitals field data?

The primary source of your CrUX field data is Google Search Console → Experience → Core Web Vitals report. This shows the percentage of your URLs classified as Good, Needs Improvement, or Poor for LCP, INP, and CLS based on real users. You can also check field data in PageSpeed Insights (scroll to 'Field Data' section) and in Chrome DevTools 'Web Vitals' panel. Note: CrUX requires a minimum traffic threshold — very low-traffic pages will show 'Not enough data'.

My Lighthouse score is 90+ but my CrUX shows 'Poor'. Why?

This is the most common Core Web Vitals confusion. Lighthouse tests a single, throttled page load in a lab environment. CrUX aggregates data from real users across all device types, network conditions, and geographic regions. Common causes of a Lighthouse/CrUX gap: (1) Your mobile users on slower devices experience significantly worse performance than your desktop emulation, (2) Third-party scripts (ads, chat widgets) that load asynchronously degrade real-user INP but don't appear in Lighthouse's initial load test, (3) Server response times are worse under real concurrent load than under Lighthouse's single synthetic request.

What tools should I use to monitor Core Web Vitals continuously?

The essential monitoring stack is: (1) Google Search Console for free URL-level CrUX field data, updated weekly, (2) PageSpeed Insights API for on-demand Lab + Field data per URL — useful in CI/CD pipelines, (3) Chrome DevTools → Performance panel and Web Vitals tab for debugging specific interactions, (4) Real User Monitoring (RUM) tools like Murkuz, Vercel Web Analytics, or Datadog for continuous LCP/INP/CLS tracking across your full URL set with granular filtering by device type, geography, and content type.

Written by Junaid Khalid

Track your real-user CWV scores across every page. Monitor Core Web Vitals.

Murkuz integrates real-user field data from your site, alerts you to CWV regressions the moment they appear in CrUX, and surfaces which specific pages are dragging your Page Experience classification.