Site Speed
Core Web Vitals in 2026: What INP Actually Means for Your Conversion Rate
Core Web Vitals in 2026 are still three metrics: Largest Contentful Paint (LCP, good under 2.5s), Interaction to Next Paint (INP, good under 200ms) and Cumulative Layout Shift (CLS, good under 0.1). The thresholds didn’t change this year — Google just got stricter about how it measures INP, which means sites that scraped by before may now be failing without anyone touching the code.
I get a version of this message a few times a year: “our Search Console just turned red and we didn’t change anything.” Usually they’re right — they didn’t change anything. Google did. Core Web Vitals aren’t a one-time checkbox; they’re a moving measurement of a moving target, and 2026 is a good example of why “we passed this once” isn’t the same as “we still pass.”
The three metrics, in plain English
Each one measures a different kind of frustration:
How long until the main content actually appears — the “is this thing loading?” moment.
How fast the page responds to a click, tap or keypress — the “did that register?” moment.
How much content jumps around while loading — the “why did I just tap the wrong thing” moment.
Google measures all three from real visitor data — the Chrome UX Report (CrUX) — at the 75th percentile, over a rolling 28-day window. That detail matters: your page doesn’t need to be fast for your fastest visitor, it needs to be fast for the fourth-slowest one out of every four, typically someone on a mid-range phone with a patchy connection.
Why INP replaced FID (and why it’s a stricter test)
Until March 2024, the responsiveness metric was FID (First Input Delay), and it had a real blind spot: it only measured the delay before a visitor’s first interaction. A page could pass FID with a snappy first click and then completely lock up the moment someone opened a filter, submitted a form, or expanded a menu — and FID would never know, because it stopped watching after that first click.
INP fixed that by watching every interaction for the whole visit and reporting the worst one. It’s a stricter, more honest test — and it’s also why a lot of sites that comfortably passed FID for years are now sitting in “needs improvement” without having changed a line of code.
What actually changed in Google’s 2026 update
The published thresholds didn’t move. What did change, according to analysis from teams tracking the rollout closely, is the methodology underneath INP: Google tightened how it calculates sustained interaction latency and expanded Core Web Vitals support for single-page applications that use soft navigation instead of full page reloads. TTFB (Time to First Byte) also became a more visible diagnostic in PageSpeed Insights, without becoming a ranking signal on its own.
The practical effect: if your INP was borderline under the old measurement, it may be failing under the new one, and most site owners haven’t re-checked yet.
That’s the part worth sitting with: Core Web Vitals aren’t primarily a ranking trick. Their bigger, more reliably measurable effect is on whether people actually complete the thing they came to do — fill the form, finish the checkout, book the call. A widely cited industry benchmark puts it starkly: a one-second delay in load time can cost up to 7% in conversions on its own.
That’s the part worth sitting with: Core Web Vitals aren’t primarily a ranking trick. Their bigger, more reliably measurable effect is on whether people actually complete the thing they came to do — fill the form, finish the checkout, book the call. A widely cited industry benchmark puts it starkly: a one-second delay in load time can cost up to 7% in conversions on its own.
Field data vs. lab data: why two tools give you different answers
This trips up almost every client the first time they compare tools. PageSpeed Insights and Lighthouse run a single, simulated test on a single connection — that’s lab data. Google Search Console’s Core Web Vitals report, on the other hand, pulls from CrUX: real measurements from real visitors on real devices over the past 28 days — that’s field data, and it’s what actually determines your ranking signal. It’s entirely possible to get a green Lighthouse score and a red Search Console report at the same time, because your test connection was faster than most of your actual visitors’ phones. When the two disagree, trust the field data — it’s describing what people genuinely experienced, not what a lab condition allowed.
What’s actually breaking INP on most sites
- Heavy filtering or faceted navigation on shop and listing pages
- Embedded forms (booking widgets, HubSpot/Fluent forms) loading blocking third-party scripts
- Chat widgets and personalization scripts running on every page, whether needed or not
- Sticky headers and animated menus recalculating layout on every scroll
What’s actually breaking LCP
- Hero images shipped as multi-megabyte PNGs instead of compressed WebP or AVIF
- Render-blocking CSS and JavaScript that delays the page from painting at all
- Slow server response time (TTFB) — often a hosting or database problem, not a front-end one
- No preload hint on the largest above-the-fold image, so the browser discovers it too late
Where to start
- Check your real-visitor scores in Google Search Console, not just a single PageSpeed test.
- Compress and correctly size every hero image — this alone fixes most LCP failures.
- Audit every third-party script (chat, analytics, forms) for what it’s actually costing you.
- Re-test INP specifically if you last checked before 2026 — the methodology has shifted.
- Fix the worst-performing template first; Core Web Vitals are now evaluated more holistically across similar pages, not just one URL in isolation.
This is exactly the work covered in our Core Web Vitals service, usually alongside a full technical SEO audit so speed fixes and crawlability get handled together instead of in separate, disconnected passes.
Not sure where your site currently stands?
I’ll check your real Search Console data — not just a single test — and tell you honestly what’s actually costing you conversions.
Start a projectFrequently asked questions
What are the Core Web Vitals in 2026?
The three Core Web Vitals are Largest Contentful Paint (LCP, good under 2.5 seconds), Interaction to Next Paint (INP, good under 200 milliseconds) and Cumulative Layout Shift (CLS, good under 0.1). Google evaluates all three using real-visitor field data at the 75th percentile, not lab tests.
What is INP and why did it replace FID?
INP (Interaction to Next Paint) measures how responsive a page feels across every click, tap and keypress during a visit, and reports the worst-case result. FID (First Input Delay) only measured the delay before the very first interaction, so a page could pass FID while still freezing later when someone used a filter, form or menu. INP officially replaced FID as a Core Web Vital in March 2024.
Did Google change the Core Web Vitals thresholds in 2026?
No. The published “good” thresholds — LCP under 2.5s, INP under 200ms, CLS under 0.1 — stayed the same in 2026. What changed was the measurement methodology: Google tightened how sustained INP latency is calculated and expanded support for single-page applications, so some sites that were borderline before are now measuring differently.
Do Core Web Vitals actually affect my Google ranking?
Yes, as part of Google’s page experience signal, though it’s one of many ranking factors rather than the dominant one. Its bigger, more measurable impact is usually on conversion rate — slow, unresponsive pages lose visitors and sales regardless of where they rank.
How do I check my site’s Core Web Vitals score?
Use the Core Web Vitals report in Google Search Console for real-visitor field data over the last 28 days, or PageSpeed Insights for a one-off check of a specific URL. Search Console is the more reliable source since it reflects how actual visitors experienced your site, not a single lab test.