Quick answer
Core Web Vitals are Google’s three measures of real-world page experience: Largest Contentful Paint (loading, aim for 2.5 seconds or less), Interaction to Next Paint (responsiveness, 200 milliseconds or less) and Cumulative Layout Shift (visual stability, 0.1 or less). Check them in Search Console and PageSpeed Insights, then fix the slowest templates first.
Last updated: November 2026
Few SEO topics generate as much jargon as Core Web Vitals. The idea behind them is simple: pages should load quickly, respond promptly when someone taps or clicks, and stay still while they load. Google measures those things using data from real Chrome users.
Page experience is not the strongest ranking factor, and content relevance still wins most contests. But slow, jumpy pages lose visitors and leads long before rankings come into it, and when two pages are otherwise similar, experience can be a tie-breaker.
This guide explains each metric in plain English, what good scores look like, how to measure your own site and the fixes that make the biggest difference on typical WordPress sites.
In this guide
- What Core Web Vitals are
- Largest Contentful Paint (LCP): how fast the main content loads
- Interaction to Next Paint (INP): how responsive the page feels
- Cumulative Layout Shift (CLS): how stable the layout is
- How to measure your Core Web Vitals
- The biggest fixes for WordPress sites
- Page builders and Elementor
- Do Core Web Vitals really affect rankings?
- A realistic example
- Monitoring and maintenance
- Quick checklist
- FAQs
What Core Web Vitals are
Core Web Vitals are a set of metrics Google uses to describe the real-world experience of a page. They are drawn from the Chrome User Experience Report, which collects anonymised data from Chrome users, so they reflect what actual visitors experience, not just what a lab test shows.
Google evaluates them at the 75th percentile, meaning that at least 75 percent of visits should meet the “good” threshold for a page or group of pages to pass. That is a demanding standard, and it explains why a site that feels fine on your fast office connection can still fail in the field.
Largest Contentful Paint (LCP): how fast the main content loads
LCP measures how long it takes for the largest visible element, usually a hero image, banner or main heading block, to appear. A good score is 2.5 seconds or less, and anything over 4 seconds is poor.
The usual culprits are oversized images, slow server response, render-blocking CSS and JavaScript, and heavy page builders or sliders in the hero section. Compressing and correctly sizing the hero image, serving modern formats such as WebP or AVIF, and using fast hosting and caching often fix LCP quickly.
Interaction to Next Paint (INP): how responsive the page feels
INP replaced First Input Delay in 2024. It measures how long the page takes to respond visually after a user interaction such as a tap, click or key press, and reports the slowest typical interaction. A good score is 200 milliseconds or less.
Poor INP usually comes from too much JavaScript: chat widgets, tracking scripts, sliders, popups and heavy plugins. Reducing third-party scripts, deferring non-essential code and removing unused plugins are the most effective fixes.
Cumulative Layout Shift (CLS): how stable the layout is
CLS measures unexpected movement of page elements while the page loads, such as text jumping when an image or ad appears. A good score is 0.1 or less. Layout shift is annoying and causes mis-taps, such as hitting the wrong button.
Fix it by setting width and height attributes on images and videos, reserving space for ads, embeds and cookie banners, and avoiding injecting content above existing content. Web fonts that swap late can also cause shifts, so preload key fonts and use sensible fallbacks.
How to measure your Core Web Vitals
Start with Google Search Console, which has a Core Web Vitals report grouping URLs into good, needs improvement and poor, based on real user data. Then use PageSpeed Insights on key pages: the field data at the top shows real users, while the lab data below helps diagnose specific issues.
Check mobile first, because most traffic and Google’s indexing use the mobile version. Test your homepage, a main service page, a blog post and any page with forms or heavy scripts. Pages built from the same template usually share the same problems, so fix templates before individual pages.
The biggest fixes for WordPress sites
- Choose quality hosting with fast server response and enable page caching, for example with LiteSpeed Cache or a similar plugin.
- Compress images, serve them in WebP or AVIF, and use responsive sizes with lazy loading for below-the-fold images.
- Remove unused plugins and heavy sliders, and avoid loading scripts on pages that do not need them.
- Defer or delay non-critical JavaScript and minimise third-party tags such as chat widgets and trackers.
- Preload your main font and hero image, and set dimensions on all media to prevent layout shift.
- Use a content delivery network if you serve visitors from many places.
Page builders and Elementor
Page builders add flexibility but can add weight. Elementor sites can perform well when built carefully: use the latest version, enable built-in performance features such as optimised DOM output and lazy loading of backgrounds, avoid deeply nested containers, and limit add-on plugins.
Our WordPress website design service builds pages with performance in mind from the start, and our technical SEO service fixes problems on existing sites without a rebuild.
Do Core Web Vitals really affect rankings?
Google has said page experience signals are used in ranking, but they are one of many factors and rarely override relevance and quality. In competitive niches where many pages are similar, a poor experience can hold you back, and a good one can help.
The stronger effect is on behaviour. Faster, steadier pages convert better. Many studies of retail and lead-generation sites show that speed improvements correlate with higher conversion and lower bounce rates, so the business case is there regardless of ranking effects.
A realistic example
Imagine a Leeds accountancy website with a large hero image, a chat widget, a cookie banner and a slider. Its mobile LCP is 4.8 seconds, because the hero image is 2 MB, and its CLS is 0.25 because the cookie banner pushes content down.
Compressing the hero image to 150 KB, preloading it, replacing the slider with a static image, delaying the chat widget until interaction and reserving space for the banner can bring LCP below 2.5 seconds and CLS below 0.1 within a few days of work. None of this needs a redesign, just attention to what loads first and what moves.
Monitoring and maintenance
Core Web Vitals change as you add plugins, scripts, images and campaigns. Check Search Console monthly, retest key pages after major changes, and ask whoever adds tracking tags or widgets to test impact first. Real-user data updates over a rolling 28 days, so improvements take a few weeks to show.
Set a simple performance budget: for example, no page over 2 MB, no more than a set number of third-party scripts, and every new image compressed before upload. Small rules prevent big regressions.
Quick checklist
- Check Search Console and PageSpeed Insights on mobile.
- Fix the hero image and server response first.
- Remove or delay heavy third-party scripts.
- Set dimensions for images, videos and embeds.
- Reserve space for banners and ads.
- Retest after changes and monitor monthly.
Technical SEO Services
Crawling, indexing, speed and schema fixed properly.
Frequently asked questions
What are good Core Web Vitals scores?
LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real user visits.
Does INP replace First Input Delay?
Yes. INP replaced FID as a Core Web Vital in March 2024 and measures overall responsiveness through the visit, not just the first interaction.
Why does PageSpeed Insights show different results from Search Console?
PageSpeed Insights lab data is a simulated single test, while Search Console and the field data section use real visitor data over 28 days. Real-user data is what Google uses.
How long do improvements take to show in Search Console?
Because data is aggregated over 28 days, expect several weeks before the report reflects improvements.
