Core Web Vitals are a set of metrics Google uses to measure real-world user experience on web pages. They focus on three simple questions: does the page load quickly, does it respond quickly when people interact with it, and does it stay visually stable while loading? These metrics are part of Google’s page experience signals and are also good indicators of whether visitors will enjoy using your site.
The names and abbreviations can sound intimidating, but the ideas behind them are straightforward. This guide explains each metric in plain language and shows you practical ways to improve them.
The Three Core Web Vitals
| — | — | — | — | — |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed of main content | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP (Interaction to Next Paint) | Responsiveness to user input | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | Unexpected layout movement | ≤ 0.1 | 0.1–0.25 | > 0.25 |
Largest Contentful Paint (LCP)
LCP measures how long it takes for the largest visible element, usually a hero image, featured image or large block of text, to appear on screen. It reflects how quickly a visitor feels the page has loaded.
Common causes of slow LCP
- Slow server response time
- Large, unoptimised images
- Render-blocking CSS and JavaScript
- Lazy-loading the main image
- Heavy page builders, sliders and third-party scripts
How to improve LCP
- Use good hosting and enable page caching
- Compress and resize your featured or hero image and serve WebP
- Do not lazy-load the main above-the-fold image; consider preloading it
- Remove unused CSS and defer non-critical JavaScript
- Use a content delivery network to serve files from locations closer to visitors
Interaction to Next Paint (INP)
INP measures how quickly a page responds when a user clicks, taps or types. It looks at interactions throughout the visit and reports one of the slowest. A high INP means the page feels sluggish, for example when a menu takes a moment to open after a tap.
INP replaced First Input Delay (FID) as a Core Web Vital in 2024 because it captures responsiveness across the whole visit, not just the first interaction.
Common causes of poor INP
- Long JavaScript tasks that block the main thread
- Too many third-party scripts such as trackers, chat widgets and ad scripts
- Complex page builders and animations
- Large DOM size with thousands of elements
How to improve INP
- Remove unnecessary plugins and scripts
- Delay non-essential JavaScript until user interaction
- Break up long tasks in custom code
- Simplify page layouts and reduce DOM size
- Load widgets such as chat tools only when needed
Cumulative Layout Shift (CLS)
CLS measures how much the page layout moves unexpectedly while loading. You have probably experienced this: you try to tap a link and the page jumps because an image or ad loaded above it. That frustration is exactly what CLS captures.
Common causes of high CLS
- Images and videos without width and height
- Ads, embeds and iframes without reserved space
- Content injected above existing content, such as banners
- Web fonts that cause text to shift when they load
How to improve CLS
- Always set width and height attributes on images and videos
- Reserve space for ad slots and embeds with fixed containers
- Avoid inserting banners above content after the page loads
- Use font-display settings and preload important fonts
How Core Web Vitals Are Measured
There are two types of data:
- Field data: collected from real users through the Chrome User Experience Report. This is what Google uses for page experience assessment.
- Lab data: collected by tools such as Lighthouse in a controlled environment. Useful for testing and debugging, but it may differ from real-world results.
Google assesses the 75th percentile of page loads, meaning at least three out of four visits should meet the “good” threshold.
Tools to Check Core Web Vitals
| — | — | — |
|---|---|---|
| Google Search Console | Field | Site-wide groups of URLs |
| Lighthouse (Chrome DevTools) | Lab | Debugging specific issues |
| Web Vitals extension | Field-like, live | Quick checks while browsing |
Core Web Vitals on WordPress
WordPress sites can perform very well with the right setup. Choose a lightweight theme, keep plugins to the essentials, use a caching plugin, optimise images automatically, and avoid loading heavy page-builder assets on every page. Test after every major change, because a single new plugin can add significant scripts.
How Much Do Core Web Vitals Affect Rankings?
Core Web Vitals are a ranking signal, but relevance and content quality remain far more important. A fast page with poor content will not outrank a slower page that answers the query much better. However, when competing pages are similar in quality, page experience can make a difference. More importantly, faster and more stable pages keep visitors engaged.
Improvement Workflow
- Check the Core Web Vitals report in Search Console to find problem URL groups
- Test a representative URL in PageSpeed Insights
- Identify the main issue for each failing metric
- Fix the biggest problems first, such as images, caching or a heavy script
- Validate the fix in Search Console and monitor over 28 days
Frequently Asked Questions
Are Core Web Vitals a major ranking factor?
They are one of many signals. Helpful, relevant content matters more, but good page experience can help in close competition.
Why do my lab and field scores differ?
Lab tests use a simulated device and network, while field data reflects real visitors with different devices and connections.
How long does it take for improvements to show?
Field data is based on a rolling 28-day window, so changes typically take several weeks to be fully reflected.
Do ads affect Core Web Vitals?
Ads can affect all three metrics. Reserving space for ad slots helps prevent layout shift.
What replaced First Input Delay?
Interaction to Next Paint (INP) replaced FID as the responsiveness metric in March 2024.
Do I need a developer to fix Core Web Vitals?
Many improvements, such as image optimisation, caching and removing plugins, can be done without a developer. Complex JavaScript issues may need technical help.
Conclusion
Core Web Vitals measure what visitors feel: speed, responsiveness and stability. Focus on fast loading of your main content, lightweight scripts and stable layouts. Use PageSpeed Insights and Search Console to find issues, fix the biggest problems first and monitor progress. Better Core Web Vitals mean happier visitors and a stronger foundation for SEO.
