Core Web Vitals Assessment: Failed, What It Means and How to Fix It
By Toy Wen Da, Co-Founder · Updated · 6 min read · scored 93/100
A "Core Web Vitals assessment: failed" label in Google Search Console means that at least 75% of real visits to a group of pages missed Google's threshold for loading speed, responsiveness or visual stability. Open the Core Web Vitals report in Search Console to see which metric and which URL group is flagged.
Check what's actually failing first
Before you change any code, run your homepage or the flagged URL through the free Website Speed Test. It pulls Lighthouse and Core Web Vitals field data in one pass, so you can see right away whether LCP, INP or CLS is the culprit, and whether it fails on mobile or desktop, without opening Search Console at all.
How Google decides "failed"
Google's Web Vitals documentation says a page passes only if it meets the recommended target at the 75th percentile of page loads, and that this applies to all three metrics at once. The thresholds are:
| Metric | What it measures | "Good" threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content loads | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How fast the page responds to clicks and taps | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much content jumps around while loading | 0.1 or less |
INP became a stable Core Web Vital in 2024 and replaced the First Input Delay metric, according to Google's web.dev Web Vitals guide (https://web.dev/articles/vitals). If your report shows INP failures and you have never heard of the metric, that is why: it is newer than LCP and CLS.
Fixing it inside Google Search Console
Search Console won't fix the problem for you, but it shows where to look.
- Open Search Console and select your property.
- In the left sidebar, under Experience, click Core Web Vitals.
- Two tabs appear, Mobile and Desktop. Check both, because a failed assessment often shows up on one and not the other.
- Click the Open report link under whichever device shows "Poor URLs" or "Needs improvement."
- The report groups failing pages by issue type (for example, "LCP issue: longer than 2.5s") and by URL group. Google's Search Console Help documentation says it assumes similar pages share a similar template.
- Click a row to see sample URLs affected by that issue. Pick two or three examples per group, since a fix to the template repairs every page in it.
- Run each sample URL through PageSpeed Insights or the Website Speed Test for a specific diagnosis: large images, slow server response, unsized ad slots, render-blocking scripts and so on.
- After you deploy a fix, return to Search Console and click Validate fix. It won't give you an instant pass, because Google needs fresh field data first.
Common causes and fixes
| Cause | Metric affected | Typical fix |
|---|---|---|
| Hero image or banner too large or unoptimized | LCP | Compress and resize images, use modern formats, preload the hero image |
| Heavy JavaScript blocking the main thread | INP | Defer non-critical scripts, split large bundles, remove unused third-party tags |
| Ads, embeds, or custom fonts loading without reserved space | CLS | Set explicit width and height on images and embeds, reserve space for ads |
| Slow server or hosting response | LCP | Upgrade hosting, enable caching, use a CDN |
| Too many redirect hops before the page loads | LCP | Flatten redirect chains to a single hop |
When Search Console alone is enough, and when it isn't
Search Console is enough for one page, a one-off regression, or a template-wide pattern it has already grouped for you. It isn't built for root-cause debugging, since it says a URL group is failing but not which line of code or which script is responsible. For a single landing page, the free tools above plus the report usually get you to a fix. A recurring problem across many templates, a Shopify theme, or a site with heavy third-party scripts will likely need deeper auditing than Search Console provides, and Shopify SEO apps that fix Core Web Vitals, schema, and AI visibility cover that gap for ecommerce sites.
Common mistakes when chasing a failed assessment
- Chasing the lab score instead of the field data. A 99 in PageSpeed Insights lab mode doesn't override real-user data from the Chrome User Experience Report, which is what Search Console actually uses.
- Fixing one sample URL and assuming the whole group passes. Fix the shared template or component, not just the example Google happened to show you.
- Expecting an instant status change. Search Console needs weeks of fresh real-user data before a "Poor" label clears, even after a correct fix.
- Ignoring accessibility-related layout issues. Unlabeled interactive elements and shifting focus states often contribute to CLS and INP problems, and fixing them tends to help usability and your accessibility and SEO standing at once.
- Only checking desktop. Most Core Web Vitals failures show up on mobile first, since phones have less processing power and often slower connections.
FAQs
Why does Search Console say failed when PageSpeed Insights shows a good score?
PageSpeed Insights can run a lab test on a fast connection with no real user behavior. Search Console's Core Web Vitals report uses real visitor data over roughly 28 days, which includes slower devices, weak connections and real interactions, so the two can disagree.
How long does it take for a failed status to change after a fix?
Google needs a fresh rolling window of real-user data before it updates the report. That typically means a few weeks after your fix goes live and gets meaningful traffic.
Does a failed Core Web Vitals assessment hurt my rankings?
Google's Search Central blog has said page experience signals, including Core Web Vitals, are part of its ranking systems. They work alongside relevance and content quality rather than overriding them. A failed assessment is a usability problem worth fixing whatever its exact ranking weight.
Can one slow page affect my whole site's report?
Search Console groups similar URLs together, so one slow template used across many pages can show up as a large group of "Poor" URLs, even if only a handful of unique templates exist.
What's the difference between Core Web Vitals and Web Vitals?
Core Web Vitals (LCP, INP, CLS) are the subset of the broader Web Vitals initiative that Google considers essential for every page. They surface in Search Console, PageSpeed Insights and Chrome DevTools.
Get a clear read on where you stand
Start by isolating which metric is failing, LCP, INP or CLS, in the Core Web Vitals report in Search Console. Confirm the diagnosis on the actual URL before you touch any code. The "Core Web Vitals assessment: failed" label clears once real-user data reflects the fix. If you want a fuller picture of how your site's technical health and content perform together, request a sample SEO report.
Resources / References
- Chrome User Experience Report
- page experience signals, including Core Web Vitals, are part of its ranking systems
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.