If your site feels fast to you but still shows “poor” in Search Console, you’re in good company. Only 48% of mobile sites and 56% of desktop sites currently pass all three at once, per the HTTP Archive’s 2025 Web Almanac. This checklist covers what each metric means and how to run a proper core web vitals test, then walks through exactly what to fix first.
Whether you’re fixing a single page or auditing a whole site, core web vitals is now table stakes for technical SEO. This guide is written for site owners, developers, and marketers. It’s a practical core web vitals checklist, not a theoretical overview. You can act on it today, on WordPress, a custom build, or an e-commerce platform. We’ll cover Google’s exact thresholds, the most common causes behind a failing score, and the fastest fixes — so you’re not guessing at what “good” Core Web Vitals looks like for your site.
Quick Answer
Core Web Vitals are three Google metrics — LCP (loading speed), INP (responsiveness), and CLS (visual stability). A page passes when at least 75% of real visits meet the “good” threshold on all three, based on real Chrome user data (CrUX), not a lab test. Check your score for free in Google Search Console or PageSpeed Insights.
48%
56%
75%
Key Takeaways
- Core Web Vitals = LCP (loading), INP (responsiveness), CLS (visual stability) — three metrics, one pass/fail threshold each.
- A page passes only when 75% of real visits meet "good" on all three; this is field data, not a lab score.
- LCP is the hardest metric to pass on mobile, at roughly 62% of pages passing.
- Good scores act as a tie-breaker in rankings, not a guarantee — content quality still comes first.
- Scores update on a rolling 28-day window, so fixes take about a month to show as "passed."
What Are Core Web Vitals?
Core Web Vitals are three user-centric metrics that judge page experience: loading speed, responsiveness, and visual stability. They’re a subset of Google’s broader Web Vitals initiative — a wider set of metrics for measuring page quality. But these three carry ranking weight, which is why they get “Core” in the name. Unlike most SEO advice, they aren’t opinion-based. They come straight from real Chrome users, collected through the Chrome User Experience Report (CrUX).
The Three Metrics:
Largest Contentful Paint (LCP)
how fast the main content loads
Interaction to Next Paint (INP)
how quickly the page responds to a tap or click
Cumulative Layout Shift (CLS)
how much the layout jumps around while loading
A fourth metric, First Contentful Paint (FCP), measures how long it takes for any content to appear on screen. It isn’t officially “Core,” but most testing tools report it anyway. It’s a useful early signal that something upstream, usually server response, is slowing everything else down.
Good scores don’t guarantee higher rankings on their own. Google evaluates content usefulness, accessibility, and overall page experience together — performance is one input, not a shortcut. If you haven’t nailed the fundamentals of on-page SEO yet, that’s usually the higher-leverage place to start. Chase those before chasing millisecond improvements here.
Are Core Web Vitals a Ranking Factor?
Yes, but as a tie-breaker, not a trump card. They’re part of Google’s confirmed page experience signals. If two pages have similar content quality, the faster one tends to win the position. But a perfect score won’t rescue thin content, and a slightly slow page won’t sink genuinely great content on its own. In competitive niches, where several pages already satisfy intent equally well, that tie-breaker is often exactly where rankings get decided.
Do Core Web Vitals Affect AI Mode and AI Overviews?
There’s no separate Core Web Vitals score that guarantees inclusion in AI-generated answers. Google’s current guidance for AI search emphasizes the same fundamentals as classic search: helpful, original content, strong page experience, crawlable pages, and content that’s accurate and easy to parse. Fast, stable pages are simply easier for AI crawlers and answer engines to read and extract from. Treat Core Web Vitals as part of your technical SEO foundation. Pair it with real work on AEO and GEO, and SEO for the AI era if AI visibility specifically matters to you.
Core Web Vitals Thresholds
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
|
Largest Contentful Paint (LCP) |
Loading Speed |
≤ 2.5s |
2.5s – 4s |
> 4s |
|
Interaction to Next Paint (INP) |
Responsiveness |
≤ 200ms |
200ms – 500ms |
> 500ms |
|
Cumulative Layout Shift (CLS) |
Visual Stability |
≤ 0.1 |
0.1 – 0.25 |
> 0.25 |
Google measures all three at the 75th percentile of real Chrome users, over a rolling 28-day window. That single detail explains most of the confusion around a failed report. Your page can look fast on your own laptop. But if a quarter of your real visitors are on older phones or slower networks, it can still fail.
According to the 2025 Web Almanac, LCP is the hardest metric to meet on mobile. Only about 62% of pages pass it, compared with roughly 77% for INP and 81% for CLS. That’s why LCP fixes usually move your overall assessment the most.
Fixing Each Metric
Largest Contentful Paint (LCP)
That’s usually a hero image, a banner, a video poster, or a large heading. This is almost always what people mean when they say a site “feels slow.”
- Compress and resize hero images before uploading, and convert them to WebP or AVIF.
- Add fetch priority="high" to your LCP image and skip lazy-loading it.
- Preload the LCP image using — but don't preload everything; competing preloads can make performance worse.
- Cut server response time. A faster host or a CDN is often the real fix.
- Remove or defer render-blocking CSS and JavaScript, and preload key fonts with font-display: swap.
Interaction to Next Paint (INP)
INP replaced First Input Delay (FID) as the official responsiveness metric on March 12, 2024. If a guide still mentions FID, it’s outdated. It’s measured across the whole session — not just the first interaction.
- Audit and remove unnecessary third-party scripts — chat widgets, trackers, and pop-up libraries are frequent offenders.
- Break long-running JavaScript tasks into smaller chunks so the browser can respond to input between them.
- Reduce DOM size. Large, deeply nested pages respond more slowly to every interaction.
- Defer non-critical JavaScript until after the page becomes interactive.
Cumulative Layout Shift (CLS)
Picture tapping a button, only for an ad to load in above it at the last second. You end up tapping the wrong thing. Of the three, a good CLS score is usually the easiest to reach.
- Set explicit width and height on every image, video, and iframe.
- Reserve space for ads and dynamic content before it loads in.
- Use font-display: swap so text doesn't jump when custom fonts load.
- Avoid inserting new content above existing content unless a user triggers it.
How to Check Your Core Web Vitals Score
There are two kinds of data here, and mixing them up causes most of the confusion around a “failed” report.
Lab data
Comes from a core web vitals checker like PageSpeed Insights running a simulated test — great for diagnosing one issue before you fix it.
Field data
Comes from real visitors, collected through CrUX — this is what Google actually uses for ranking, and it’s what shows up in Search Console.
A page can score perfectly in a lab test and still show “poor” in Search Console. That’s not a bug. It means real visitors on real devices are having a rougher time than your test environment.
Where to run a free core web vitals test
Google Search Console
Core Web Vitals report — field data, grouped by URL
PageSpeed Insights
Lab and field data side by side, free, no login
Chrome DevTools Lighthouse Panel
Good for testing fixes before you deploy them
Chrome UX Report (CrUX) Dashboard
A broader, aggregated view of real-user data
If Search Console shows “not enough data,” that URL likely doesn’t get enough Chrome traffic for a reliable sample. Use PageSpeed Insights for that page instead.
Core Web Vitals Checklist
Work through this in order of impact. LCP fixes usually deliver most of the improvement in your overall assessment on their own.
- LCP is 2.5 seconds or less
- INP is 200 milliseconds or less
- CLS is 0.1 or less
- Hero images are compressed, correctly sized, and served in WebP/AVIF
- The LCP image is not lazy-loaded and is preloaded where appropriate
- Server response time (TTFB) has been reviewed
- Render-blocking CSS and JavaScript have been removed or deferred
- Unnecessary third-party scripts have been audited and trimmed
- Long JavaScript tasks have been broken up
- Images, videos, and iframes all have explicit dimensions
- Space is reserved for ads and dynamic content
- Fonts use font-display: swap
- Mobile performance has been tested separately from desktop
- Field data in Search Console has been reviewed, not just a lab score
Get the Core Web Vitals Checklist Template
Download the same 30-item checklist, organized by section, as a printable PDF or as an Excel tracker with a live progress counter:
Download the Checklist PDF
Print-ready · tick as you go
Get the Excel / Sheets Template
Track owner, status & due dates
Fixing Core Web Vitals WordPress Issues
If you’re troubleshooting Core Web Vitals WordPress problems specifically, start simple. WordPress sites pass Core Web Vitals at meaningfully lower rates than the rest of the web. That’s largely because themes and plugins quietly stack up extra CSS and JavaScript over time. Work through these before considering custom development:
Optimise images
Use appropriately sized images instead of a large one displayed small.
Review caching
A properly configured plugin reduces server processing, but avoid switching on every optimisation option without testing the result first.
Audit plugins
Remove what's unused, and check whether the plugins you keep are loading scripts on pages where they aren't needed.
Reduce third-party scripts
Chat tools, analytics, and social widgets add up fast; keep only what earns its place.
Check the theme
Unused CSS, large font files, sliders, and animation libraries are common theme-level bloat.
Picking the right WordPress SEO plugins and auditing what’s already installed usually clears the bulk of the problem. A full rebuild is rarely necessary.
Why Your Assessment Might Show "Failed"
Search Console can show “Core Web Vitals assessment failed” for a group of URLs. This means at least one metric missed the “good” threshold for 75% of visits. It can happen even if the other two metrics pass. A few things worth checking first:
One metric is failing, not all three. A page can have good LCP and CLS but poor INP. Identify the specific metric before changing anything.
Mobile is usually weaker than desktop. Google scores them separately, and mobile users typically have slower connections and less powerful devices.
A shared template can drag down a whole group. If the same header, banner, or script runs across hundreds of URLs, one technical problem affects the entire group’s average, even if most individual pages are fine.
Low-traffic pages may show “not enough data” instead of a real score. That’s a sample-size issue, not a failure — use PageSpeed Insights for those pages instead.
This kind of diagnostic work sits squarely inside technical SEO — a different discipline from on-page or off-page work. Still, all three need to work together for rankings to hold.
Tools to Test and Monitor Core Web Vitals
| Tool | Best for |
|---|---|
|
Page Speed Insights |
Quick lab + field check for one URL, free |
|
Google Search Console |
Ongoing field data across your whole site |
|
Lighthouse (Chrome DevTools) |
Testing fixes locally, before deployment |
|
GTmetrix |
A deeper waterfall view of what loads and when |
|
Chrome UX Report (CrUX) |
Aggregated real-user data at scale |
|
Server response + crawl logs |
Best for confirming AI/LLM crawlers can actually load your page fast enough to parse it |
Re-check your scores after any major update. A new plugin, a redesigned banner, or a bulk image upload can quietly undo weeks of work. And because CrUX runs on a 28-day rolling window, it takes time for a fix to show up in your reported score.
Writing for AEO, GEO, and AI Mode — Not Just Classic SEO
Answer Engine Optimization and Generative Engine Optimization aren’t a separate trick layered on top of SEO. They reward the same fundamentals: direct answers, descriptive headings, technical terms defined clearly, and information kept close to the heading it belongs under. A short, self-contained answer like the one under “What Are Core Web Vitals?” above is easy for a reader to scan. It’s just as easy for an answer engine to lift cleanly.
One structured-data note worth knowing: Google removed FAQ rich results from Search on May 7, 2026. Search Console reporting and Rich Results Test support followed in June 2026, and Search Console API support ended in August 2026. FAQPage schema is still valid — Google says it continues to use it to understand page content. It just no longer produces the expandable dropdown in Google Search. That means FAQ schema is worth keeping for the benefit of other crawlers (AI/LLM retrieval systems, Bing) rather than for a Google SERP feature. There’s no confirmed method for guaranteeing an LLM cites a specific page. The safest strategy is still genuinely useful, accurate, well-structured content.
Ready to Pass Your Core Web Vitals?
Now that you know how to check and fix LCP, INP, and CLS, implementing them correctly is where the real results come from.
Frequently Asked Questions
What are Core Web Vitals?
Core Web Vitals are three Google metrics — LCP, INP, and CLS. They measure a page’s loading speed, responsiveness, and visual stability using real visitor data collected from Chrome. A page passes when all three hit the “good” threshold for at least 75% of real visits.
How do I improve Core Web Vitals?
Fix whichever metric is furthest into the “poor” range first. That’s usually LCP, since only around 62% of mobile pages currently pass it. For LCP, optimise your hero image and cut server response time. INP needs unnecessary third-party scripts removed and long JavaScript tasks broken up. For CLS, set fixed dimensions on every image, video, and iframe.
How do I fix Core Web Vitals if I don't know how to code?
Most issues on WordPress and similar platforms come from un optimized images, an unconfigured caching plugin, or too many third-party scripts. All of that is fixable through plugin settings, not custom code. Even when development work is genuinely needed, it’s usually a one-time fix.
How do I check Core Web Vitals?
Use the Core Web Vitals report in Google Search Console for real-user field data grouped by URL. Or run a single page through Page Speed Insights for a quick check that shows lab and field data side by side.
Why does PageSpeed Insights show a good score while Search Console shows Core Web Vitals as poor?
Page Speed Insights can show lab data — a single simulated test — even when Search Console shows poor field data from real visitors. A page can score perfectly in a controlled test and still fail for real users on slower devices or networks. Field data in Search Console is what Google actually uses for ranking.
What is a good LCP score?
A good Largest Contentful Paint score is 2.5 seconds or less, measured at the 75th percentile of real visits.
What is a good INP score?
Interaction to Next Paint is considered good at 200 milliseconds or less, measured at the 75th percentile of real visits.
What is a good CLS score?
Cumulative Layout Shift is considered good at 0.1 or less, measured at the 75th percentile of real visits.
How long does it take for Core Web Vitals to update after a fix?
Around 28 days. Scores come from a rolling 28-day window of real Chrome user data. A fix deployed today typically won’t show as “passed” until roughly four weeks of fresh traffic has been collected.
Are Core Web Vitals a ranking factor?
Yes, but as a tie-breaker rather than a primary signal. Between two pages of similar content quality, the faster one tends to rank higher. Good scores alone won’t outrank genuinely better, more relevant content.
Why are Core Web Vitals important beyond SEO?
Faster, more stable pages lower bounce rate and lift conversions directly — users abandon slow pages regardless of ranking. Clean, stable pages are also easier for AI search tools to read and extract accurately.
What does a Core Web Vitals assessment failed message mean?
It means at least one of the three metrics missed the “good” threshold for 75% of real visits to a group of URLs. That can happen even if the other two metrics passed. Mobile and desktop are scored separately, so a page can pass one and fail the other.
Core Web Vitals aren’t about chasing a perfect PageSpeed score. They’re about fixing three specific, measurable parts of the user experience. Start with real-user data from Search Console when it’s available. Use PageSpeed Insights and Lighthouse to diagnose individual problems, and prioritise whichever metric is furthest from “good.” Strong performance can’t replace useful content or relevance, but it removes friction that costs you both rankings and conversions.
Not sure where your site stands? Run a free check through Search Console or PageSpeed Insights. If the report raises more questions than it answers, Digital Roop’s technical SEO audits can tell you exactly what to fix first — and how it fits into your broader on-page and site-wide SEO strategy.
