Core Web Vitals are Google's official page experience metrics that directly affect your search rankings. If your pages score "Poor" on LCP, CLS or INP, you are at a ranking disadvantage compared to competitors with better scores. This guide explains what each metric measures, what score to aim for, and exactly how to fix common issues.
What Are Core Web Vitals?
Core Web Vitals are a set of three specific metrics Google uses to measure the real-world user experience of a web page. They became an official Google ranking signal in 2021 and continue to be weighted in search rankings. Pages that score well on Core Web Vitals have a measurable advantage in Google search, all else being equal.
The three Core Web Vitals are:
- LCP — Largest Contentful Paint
- CLS — Cumulative Layout Shift
- INP — Interaction to Next Paint
LCP — Largest Contentful Paint
LCP measures how long it takes for the largest visible element on the page to load. This is usually a hero image, a large heading, or a video thumbnail. It represents perceived load speed — how quickly the user sees the main content.
Good: Under 2.5 seconds
Needs improvement: 2.5–4 seconds
Poor: Over 4 seconds
How to improve LCP:
- Compress and resize hero images — use WebP format
- Remove render-blocking CSS and JavaScript
- Use a fast hosting provider with good server response times
- Add
fetchpriority="high"to your hero image tag
CLS — Cumulative Layout Shift
CLS measures how much the page layout shifts unexpectedly while loading. You have experienced high CLS when you go to click a button and it suddenly moves because an image or ad loaded above it. This is frustrating for users and penalised by Google.
Good: Under 0.1
Needs improvement: 0.1–0.25
Poor: Over 0.25
How to improve CLS:
- Always set width and height attributes on images and videos
- Reserve space for ads before they load
- Avoid inserting content above existing content dynamically
- Use CSS transform animations instead of layout-triggering properties
INP — Interaction to Next Paint
INP replaced FID (First Input Delay) in March 2024. It measures the time from a user interaction (click, tap, keyboard press) to when the browser visually responds. It captures overall interactivity throughout the entire page visit, not just the first interaction.
Good: Under 200ms
Needs improvement: 200–500ms
Poor: Over 500ms
How to improve INP:
- Reduce JavaScript execution time — break long tasks into smaller ones
- Defer non-critical JavaScript
- Remove unused JavaScript and third-party scripts
How to Check Your Core Web Vitals
Several free tools let you check your Core Web Vitals scores:
- Google Search Console — shows field data (real user data) under Core Web Vitals report
- PageSpeed Insights — shows both lab and field data for any URL
- Chrome DevTools — Lighthouse tab gives a full audit
Always prioritise fixing the pages with the most traffic first — those improvements will have the biggest impact on your overall rankings.
Core Web Vitals and SEO Rankings
Google uses Core Web Vitals as a tiebreaker — when two pages have similar relevance and authority, the page with better page experience scores will rank higher. For new sites competing against established domains, having excellent Core Web Vitals gives you an edge that many larger sites neglect. Make sure your meta tags and content are also optimised alongside your technical performance for maximum ranking potential.
Core Web Vitals matter most when you are competing for keywords where multiple pages have similar content quality and backlink profiles. At that point, page experience signals like LCP and CLS can be the deciding factor. Neglecting Core Web Vitals essentially caps your ranking potential even when everything else is optimised.
Core Web Vitals Quick Reference
| Metric | What It Measures | Good | Poor |
|---|---|---|---|
| LCP | Largest element load time | Under 2.5s | Over 4s |
| CLS | Layout shift during load | Under 0.1 | Over 0.25 |
| INP | Response to user interactions | Under 200ms | Over 500ms |
According to Google's Core Web Vitals documentation, these three metrics became official ranking signals in 2021 and continue to be weighted in Google's page experience scoring.
Real-World vs Lab Data for Core Web Vitals
When checking Core Web Vitals, you will encounter two types of data:
- Lab data (Lighthouse) — a simulated test run in a controlled environment with predefined device and network settings. This is what PageSpeed Insights shows in its "Diagnose performance issues" section. Lab data is consistent and comparable across runs, making it useful for debugging. However, it does not reflect real user experience on actual devices and connections.
- Field data (CrWUX) — real performance metrics collected from real Chrome users visiting your site. This is what Google Search Console's Core Web Vitals report shows, and what Google uses for ranking purposes. Field data reflects actual user experience but requires sufficient traffic volume to generate meaningful data.
For ranking purposes, focus on improving field data first. If your field data shows "Good" but your lab data shows "Needs Improvement", your rankings are not penalised — the field data is what counts. However, consistently improving lab data tends to improve field data over time as more users experience the faster page.
How to Prioritise Core Web Vitals Fixes
Not all pages need the same level of Core Web Vitals optimisation. Focus your effort strategically:
- Fix your highest-traffic pages first — a CWV improvement on a page with 1,000 monthly visits has 10x more impact than fixing a page with 100 visits
- Fix "Poor" scores before "Needs Improvement" — pages with "Poor" ratings are actively penalised; "Needs Improvement" is less urgent
- Prioritise mobile over desktop — Google uses mobile-first indexing; mobile scores matter more than desktop
- Address LCP before CLS before INP — LCP has the most direct user-visible impact and is most frequently the bottleneck for a site's overall page speed score
After making changes, re-run PageSpeed Insights and wait 28 days for field data in Search Console to update — real-user data takes time to accumulate. Do not judge results on a single run of the lab test.
Use our Readability Checker and Meta Tag Generator alongside your Core Web Vitals work — technical performance and content quality together determine your final ranking position.
Free and Paid Tools for Monitoring Core Web Vitals
Tracking Core Web Vitals requires both lab tools (which test on-demand) and field tools (which show real-user data). Here are the best options at each level:
Google PageSpeed Insights (free) — the primary tool for checking CWV. Enter any URL to get LCP, CLS and INP scores for both mobile and desktop. The report shows "Field Data" (real-user measurements from Chrome users) and "Lab Data" (controlled test environment). Field data is what Google actually uses for rankings.
Google Search Console — Core Web Vitals report (free) — shows field data aggregated across all pages on your site, colour-coded by score status. This is the best place to identify which pages need the most urgent attention. Pages are grouped into "Poor," "Needs Improvement" and "Good" — address the "Poor" group first.
Chrome DevTools — Lighthouse (free) — the Lighthouse tab in Chrome DevTools runs a comprehensive performance audit with specific, actionable recommendations. The "Opportunities" section shows exactly which assets to optimise, with estimated time savings for each fix. Essential for developers diagnosing specific performance bottlenecks.
WebPageTest (free) — provides filmstrip and waterfall views of page loading, helping identify exactly what is causing LCP delays. The visual timeline makes it easy to see which resources are blocking the initial render.
For larger sites, commercial tools like Ahrefs Site Audit, Semrush Site Audit and Screaming Frog integrate CWV data with broader SEO auditing — useful for bulk analysis across hundreds of pages.
Frequently Asked Questions
Are Core Web Vitals a confirmed Google ranking factor?
Yes. Google officially announced Core Web Vitals as ranking signals in May 2021 as part of the Page Experience update. LCP, CLS and INP are the three current metrics. Pages that score "Poor" on these metrics may rank lower than similar pages with better scores.
How do I check my Core Web Vitals scores?
Use Google PageSpeed Insights (pagespeed.web.dev) for lab data on any URL. For real-user field data, check the Core Web Vitals report in Google Search Console. Chrome DevTools Lighthouse tab also provides a full audit with specific recommendations.
What is the difference between LCP and FCP?
FCP (First Contentful Paint) measures when the first element appears on screen. LCP measures when the largest visible element finishes loading. LCP is more important for user experience because it represents when the main content of the page is visible — the moment a user can start reading or interacting.
My LCP is slow — what is the quickest fix?
The most common cause of poor LCP is an oversized hero image. Compress your hero image to under 200KB, convert it to WebP format, and add fetchpriority="high" to the image tag. These three changes alone often reduce LCP by 1–2 seconds on mobile.
How long does it take for Core Web Vitals improvements to affect rankings?
Google updates its Core Web Vitals field data roughly every 28 days using a rolling 28-day window of real-user Chrome data. After making a performance improvement, allow 4–6 weeks before expecting to see ranking changes. Monitor the Core Web Vitals report in Google Search Console — once the "Poor" pages move to "Needs Improvement" or "Good," you should start seeing positive ranking signals take effect.