Back to Blog
Performance

Core Web Vitals and INP in 2026: What the Numbers Mean

By Ashker Published August 15, 2026 6 min read
Core Web Vitals dashboard showing LCP, INP and CLS scores for a UAE website.

Short Answer

Core Web Vitals are LCP, INP and CLS, and a page passes at 2.5 seconds, 200 milliseconds and 0.1. INP replaced FID on 12 March 2024 and is graded on 28 days of real Chrome data.

On 12 March 2024, Google swapped First Input Delay for Interaction to Next Paint in its Core Web Vitals. Plenty of UAE sites that had shown green for years dropped into amber within weeks of the change. Nothing on those sites changed that day. The measuring stick did, and many owners still have not rechecked their Search Console report since then.

This guide explains what each metric measures, the thresholds Google publishes on web.dev, and how the scoring really works. You will see why INP catches problems the old metric missed entirely. We also show where to find your real-user data for free. The aim is simple: know which number to fix first, and why it matters for your visitors.

What are the three Core Web Vitals in 2026?

The three Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. LCP tracks loading, INP tracks responsiveness to taps and clicks, and CLS tracks layout jumps. Google's web.dev rates a page good at 2.5 seconds, 200 milliseconds and 0.1.

Poor starts above 4 seconds for LCP, above 500 milliseconds for INP and above 0.25 for CLS. Every value in between is labelled needs improvement. The same bands appear in Google's PageSpeed Insights documentation, so any Google tool you use should report the same labels.

Quick Answer

Google's 2026 Core Web Vitals are LCP, INP and CLS. A page passes when LCP is 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or lower.

How is INP different from First Input Delay?

FID measured only the wait before the browser began handling the first interaction on a page. INP observes every click, tap and key press during the visit and reports close to the slowest one. It also counts the time until the next frame is painted.

web.dev splits each interaction into input delay, processing duration and presentation delay. A menu button can start quickly yet spend 400 milliseconds inside its event handler, which FID never saw. That is why script-heavy sites with busy menus slipped once INP became stable in 2024.

Quick Answer

INP officially replaced First Input Delay as a Core Web Vital on 12 March 2024. It measures the full delay from a tap or click to the next visual update.

Why do field data and lab scores disagree?

Core Web Vitals are judged on field data from real Chrome users, not on one lab test. PageSpeed Insights shows Chrome UX Report results from the previous 28 days. Google assesses each metric at the 75th percentile of visits, split by mobile and desktop.

Lighthouse simulates one mid-range phone on a throttled connection, so its numbers are a diagnosis tool. A lab score of 95 can sit beside failing field INP, because Lighthouse never clicks anything. Quiet pages may show no field data, since CrUX only includes sufficiently popular URLs.

Quick Answer

Google grades Core Web Vitals on 28 days of real Chrome user data at the 75th percentile. Lighthouse lab scores help diagnose problems but cannot confirm that a page passes.

What fixes each metric fastest?

For LCP, find the largest element above the fold, usually a hero image or heading, and make it load before everything else. Serve it compressed, sized and never lazy-loaded. For CLS, give images, embeds, cookie banners and promo bars fixed dimensions so nothing pushes content down.

INP needs a different approach, because the cost sits in JavaScript running on the main thread. Remove scripts that no longer earn their place, delay the rest, and break long tasks into smaller pieces. Chat widgets, tag managers and heavy sliders are common suspects.

Quick Answer

Fix LCP by prioritising the hero image and server response, and fix CLS by reserving space. Fix INP by reducing and splitting main-thread JavaScript, especially third-party chat and tracking widgets.

How do you check Core Web Vitals for your own site?

Start with the Core Web Vitals report in Google Search Console, which groups URLs by status using field data. Then open PageSpeed Insights for one representative URL from each failing group. Check the mobile tab first, since phones usually fail before desktops do.

Write down the failing metric, the element named in the diagnostics and the exact date you last checked. After a fix ships, let the 28-day window roll forward before judging the result. Search Console's Validate Fix button then tracks that issue group across a fresh 28-day period.

Quick Answer

Use the Google Search Console Core Web Vitals report to find failing URL groups, then PageSpeed Insights to diagnose one page. Allow 28 days after a fix before judging results.

Main Takeaways

Core Web Vitals in 2026 are LCP, INP and CLS, with good thresholds of 2.5 seconds, 200 milliseconds and 0.1. INP replaced FID on 12 March 2024 and exposes heavy JavaScript that older tests ignored. Google grades real Chrome users over 28 days at the 75th percentile. Diagnose problems with Lighthouse, but confirm success only in Search Console field data.

What to do with your Core Web Vitals this month

Core Web Vitals reward pages that load their main content quickly, respond to taps without lag and stay visually still while people read. INP is the metric many UAE sites now miss, and the fix is usually less JavaScript rather than a pricier hosting plan. Lab scores from Lighthouse guide the day-to-day work. Real-user field data decides whether it truly worked.

Open Search Console today and note which metric fails on mobile. Our website speed optimisation checklist orders the fixes, and the guide to why sites slow down on phones covers mobile causes. Prefer to hand it over? The Auronix Web Studio Core Web Vitals and SEO performance service can review your field data and fix whichever metric is failing.

Sources & References

  • Google web.dev: Web Vitals, last updated 31 October 2024
  • Google web.dev: Interaction to Next Paint (INP), last updated 2 September 2025
  • Google web.dev blog: Interaction to Next Paint becomes a Core Web Vital on March 12, 2024
  • Google for Developers: About PageSpeed Insights
  • Google Search Central: Understanding Core Web Vitals and Google search results, last updated 10 December 2025
  • Chrome for Developers: CrUX methodology
  • FAQs

    Questions readers usually ask next

    These FAQs are written to match the topic of this post and to help readers move from understanding to action.

    What replaced FID in Core Web Vitals?

    Interaction to Next Paint replaced First Input Delay on 12 March 2024. Google gave developers until 9 September 2024 to move off FID in its tools, and INP covers responsiveness.

    What is a good INP score?

    A good INP is 200 milliseconds or less at the 75th percentile of page visits. Between 200 and 500 milliseconds needs improvement, and anything above 500 milliseconds is rated poor.

    Do Core Web Vitals affect Google rankings?

    Google says Core Web Vitals align with what its core ranking systems reward, alongside other page experience signals. Google Search Central adds that the most relevant content can still rank.

    Why does PageSpeed Insights say there is no field data?

    The Chrome UX Report only includes pages and origins with enough visitors. Newer or low-traffic pages often lack data, so rely on origin-level results and Lighthouse diagnostics until traffic grows.

    Is TTFB a Core Web Vital?

    No, Time to First Byte is not a Core Web Vital, although web.dev treats 0.8 seconds or less as good. A slow TTFB still delays LCP, so it deserves attention.

    How long do Core Web Vitals take to update after a fix?

    Field data in PageSpeed Insights covers the previous 28 days, so improvements appear gradually. Expect roughly four weeks before the 75th percentile fully reflects a fix across your real visitors.

    Does CLS count layout shifts after the page loads?

    Yes, CLS includes unexpected layout shifts throughout the life of the page, not just loading. Shifts that follow shortly after a user interaction, such as opening an accordion, are excluded.

    Can a WordPress site pass Core Web Vitals?

    Yes, WordPress sites can pass when the theme is light, images are sized and plugins are limited. Failures usually trace to page builders and plugin scripts rather than WordPress core.

    Should I check mobile or desktop Core Web Vitals first?

    Check mobile first, because Google reports mobile and desktop separately and phones are slower. A page can pass on desktop while failing INP on mid-range Android phones in the UAE.

    Which tools show INP while testing a page?

    The Performance panel in Chrome DevTools shows live INP values as you click through a page. Google's open-source web-vitals JavaScript library can also send INP from real visitors into analytics.

    Related Resources

    Need your website to load faster on mobile?

    We help UAE businesses remove weight, simplify templates, and improve Core Web Vitals without breaking the site structure or search intent.

    Built for search-ready UAE websites that need faster pages, clearer journeys, and stronger conversion rates.

    WhatsApp Start project chat