Google made Core Web Vitals a ranking factor in 2021 and the SEO industry responded with a level of alarm that wasn't entirely proportional to the actual impact. Agencies started selling "Core Web Vitals optimization" as an urgent fix. Tools started surfacing failing scores on dashboards. Business owners started asking whether their site was going to disappear from Google because their Largest Contentful Paint was 3.2 seconds instead of 2.5.
The reality is more measured. Core Web Vitals matter, but they operate as a tiebreaker more than a primary ranking signal. A site with mediocre page speed and excellent content, strong backlinks, and good technical fundamentals will nearly always outrank a site with a perfect performance score and weak content. Google’s page experience documentation is explicit about this: “Great page experience doesn’t override having great, relevant content.” The signal exists. It’s just not the one to panic about first.
That said, poor Core Web Vitals do have real costs beyond rankings, and those costs are often more immediate than any SEO impact.
What the Three Metrics Actually Measure
Largest Contentful Paint (LCP) measures how long it takes for the main content element on the page to become visible. For most pages, this is the hero image, the main headline, or the primary block of text. Google’s threshold is 2.5 seconds for a Good score. The reason this matters beyond SEO is that users who land on a page and don’t see content within 2–3 seconds leave at significantly higher rates. A Google and Deloitte study found that a 0.1-second improvement in mobile site speed improved conversion rates by 8% for retail sites. LCP is the metric most directly tied to whether someone waits for your page to load.
Interaction to Next Paint (INP) replaced First Input Delay in 2024 and measures how long it takes your page to respond after a user clicks, taps, or types. A page that takes 500 milliseconds to respond after someone clicks a button feels broken, even if it eventually works. Google’s Good threshold is below 200ms. This one matters most for interactive pages, contact forms, calculators, filter interfaces, booking tools. For simple informational pages, it’s rarely the main issue.
Cumulative Layout Shift (CLS) measures visual stability, specifically, whether elements on the page move around while it’s loading. When a button shifts right as an image loads and the user accidentally clicks the wrong thing, that’s a CLS problem. When the page re-renders mid-read and loses your place, that’s CLS. Google’s Good threshold is below 0.1. This one is often the most annoying to experience even if it’s the least dramatic in terms of direct ranking impact.
| Metric | What It Measures | Good Score | Where It Hurts Most |
|---|---|---|---|
| Largest Contentful Paint (LCP) | Time for main content to appear | Under 2.5s | High-traffic landing pages, paid ads destinations |
| Interaction to Next Paint (INP) | Page response after user input | Under 200ms | Interactive tools, forms, booking pages |
| Cumulative Layout Shift (CLS) | Visual stability during load | Under 0.1 | Any page with ads, images, or late-loading fonts |
How Much Core Web Vitals Actually Affect Rankings
Google has confirmed Core Web Vitals as a ranking signal, but multiple studies since 2021 have tried to quantify the impact and arrived at similar conclusions: the effect is real but modest. A Searchmetrics analysis from 2022 found that pages with poor Core Web Vitals scores did rank lower on average, but the effect was smaller than signals like backlink authority, content relevance, and keyword targeting.
The practical implication is this: if your site is competing for a high-difficulty keyword against pages with similar authority, content quality, and technical optimization, Core Web Vitals can be the difference. If your site has a content or authority gap compared to the pages ranking above you, fixing your LCP score will not close that gap. You’d be solving the wrong problem.
Where Core Web Vitals have outsized impact is on landing pages served through Google Ads. Google factors page experience into ad Quality Score, and a poor landing page experience score raises your cost per click while lowering your ad rank. A slow landing page costs you twice: lower organic rankings and higher paid CPCs. We cover the landing page cost problem in more depth in Your Landing Page Is Costing You Twice.
The Problems Worth Fixing vs. The Problems Worth Ignoring
Fix These First
Unoptimized images are responsible for a large portion of LCP failures. An image served at 2,400px wide to a mobile screen that renders it at 400px is loading six times more data than necessary. Compressing images and serving them in modern formats (WebP, AVIF) is the highest-leverage LCP fix for most sites and doesn’t require a developer for the initial implementation.
Render-blocking resources, JavaScript and CSS that must load before the browser renders the page, cause LCP delays on many WordPress and e-commerce sites. Deferring non-critical JavaScript is a standard fix that typically improves LCP by 0.3–0.8 seconds and requires minimal risk.
Font loading without a fallback causes text to be invisible until the web font downloads, which contributes to both LCP and CLS. Adding font-display: swap to your CSS tells the browser to show a fallback font immediately and swap to the custom font when it’s ready. It takes 30 seconds to add and visibly improves perceived performance.
Don’t Lose Sleep Over These
A PageSpeed Insights score of 65 vs. 72 is not a meaningful ranking difference. The score is a diagnostic tool, not a grade. Chasing a specific number rather than fixing identifiable problems is how agencies bill hours without producing results.
Desktop Core Web Vitals scores are less important than mobile scores for most businesses. Google’s page experience ranking signal is based on mobile data. Your desktop score can be perfect while your mobile score is in the red, and the ranking impact comes from mobile. Check mobile first.
Third-party scripts (chat widgets, analytics, tag managers, advertising pixels) almost always hurt performance scores. You’re not going to remove your CRM chat widget to get a better PageSpeed score. Accept that trade-off, fix what’s within your control, and don’t report the score as though the third-party scripts don’t exist.
How to Check Your Own Scores
Google Search Console has a Core Web Vitals report built in, under Experience in the left navigation. It shows you which URLs have Good, Need Improvement, or Poor scores based on real user data from Chrome, not the lab-based score from PageSpeed Insights. The Search Console report is the one that matters for rankings because it uses field data.
PageSpeed Insights is useful for diagnosing what to fix on specific pages. Enter any URL and it shows you both field data (real user experience) and lab data (simulated load), plus a list of specific opportunities ranked by estimated impact. Work down that list by estimated savings, not by what’s easiest to explain to a client.
If your SEO provider has never mentioned Core Web Vitals, that’s worth asking about. If Core Web Vitals is all they talk about while your non-branded organic traffic is flat, they’ve got the priorities backwards. Our technical SEO services include a page experience audit as part of the baseline, and we tell you what’s worth fixing and what’s not before we touch anything.
