Core Web Vitals are Google’s three measurements of real-world page experience: how fast the main content loads, how quickly the page responds to clicks and taps, and how stable the layout is while loading. Passing them makes your site feel fast and trustworthy, and it removes a common technical drag on SEO. This guide explains each metric, the official thresholds and exactly what to fix first.
- LCP (Largest Contentful Paint): good at 2.5 seconds or less.
- INP (Interaction to Next Paint): good at 200 milliseconds or less. It replaced FID in March 2024.
- CLS (Cumulative Layout Shift): good at 0.1 or less.
- A page passes when at least 75 percent of real visits meet the “good” level for all three, measured across mobile and desktop.
What are the Core Web Vitals?
Web Vitals is a Google initiative that simplifies performance into a few signals that matter to users. The Core Web Vitals are the subset every site owner should monitor. Each one covers a different part of the experience:
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP | Loading: how quickly the largest visible element appears | 2.5 s or less | Over 4 s |
| INP | Responsiveness: how quickly the page reacts to interactions | 200 ms or less | Over 500 ms |
| CLS | Visual stability: how much the layout jumps around | 0.1 or less | Over 0.25 |
Google recommends judging each metric at the 75th percentile of page loads, segmented by mobile and desktop. A page passes when it meets the recommended target for all three.
Do Core Web Vitals affect SEO?
Page experience is part of Google’s guidance for creating successful pages, including for its generative AI search features. Core Web Vitals will not rescue thin content, and great content can still rank with imperfect scores. But on competitive keywords, a slow, jumpy page loses visitors before they read, which hurts engagement and conversions as well as rankings. Treat speed as a conversion feature that also supports SEO. Our technical SEO checklist puts it in context.
How to measure Core Web Vitals correctly
- Field data comes from real users and is what counts. See it in PageSpeed Insights (the “Discover what your real users are experiencing” section) and in the Core Web Vitals report in Search Console.
- Lab data (Lighthouse) simulates a load and is ideal for debugging because it is repeatable. It can differ from field results.
- Test your key templates: home page, a service page, a blog post and a product or contact page. Fixing a template fixes every page that uses it.
How to improve LCP (loading)
- Find your LCP element. It is usually the hero image or the main heading block.
- Optimize that image. Serve the correct dimensions in WebP or AVIF, compress it and never lazy-load the image that appears first on screen.
- Preload the critical resource (the hero image and the main font).
- Improve server response. Quality hosting, page caching and a CDN reduce time to first byte.
- Cut render-blocking CSS and JavaScript. Defer non-critical scripts and inline only the CSS needed above the fold.
- Handle fonts well. Self-host fonts, preload the primary one and use font-display to avoid invisible text.
How to improve INP (responsiveness)
- Reduce JavaScript. Every script competes for the main thread. Remove what you do not use.
- Audit third-party scripts. Chat widgets, tag managers, heatmaps and ad pixels are frequent culprits. Load them after interaction or delay them.
- Break up long tasks. Split heavy work so the browser can respond between chunks.
- Keep the DOM small. Thousands of nested elements, often from heavy page-builder layouts, slow every interaction.
- Keep event handlers light. Do the minimum work on click, and defer the rest.
How to improve CLS (visual stability)
- Set width and height on images, videos and embeds so the browser reserves space.
- Reserve space for banners, cookie notices and ads instead of pushing content down after load.
- Do not inject content above content that is already visible.
- Stabilize fonts so text does not reflow when the web font loads.
- Animate with transform and opacity, not with properties that change layout.
WordPress and Elementor: a practical speed plan
WordPress powers about 39.6 percent of all websites according to W3Techs, and Elementor is used on roughly a third of those, so these fixes apply to a large share of the web. Most slow WordPress sites share the same causes.
| Fix | Helps | Effort |
|---|---|---|
| Page caching and a CDN | LCP | Low |
| Compress and resize images, serve WebP | LCP | Low |
| Remove unused plugins and heavy add-ons | INP, LCP | Medium |
| Self-host and preload fonts | LCP, CLS | Low |
| Delay third-party scripts | INP | Medium |
| Use a lightweight theme and lean page-builder layouts | All three | Medium |
| Set image dimensions and reserve space for banners | CLS | Low |
| Use current PHP and good hosting | LCP | Low |
Tip: Fix in order of impact: images and hosting first, then scripts, then layout. Re-test after each change so you know what worked.
Speed is built in to how we work. On this site, for example, fonts are self-hosted and preloaded and scripts are deferred. If you want your website audited and fixed, see our web development services, which include speed optimization and Core Web Vitals work.
How long until Core Web Vitals improve?
Lab scores update immediately after a fix. Field data in Search Console reflects real visits over a rolling period, so expect several weeks before the report catches up. That delay is normal.
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 page loads.
Did INP replace FID?
Yes. Interaction to Next Paint replaced First Input Delay as the responsiveness metric in Core Web Vitals in March 2024.
Why is my PageSpeed score different from Search Console?
PageSpeed Insights shows lab data from a simulated load as well as field data from real users. Search Console uses field data only, which is what Google evaluates.
Can a WordPress site pass Core Web Vitals?
Yes. With good hosting, caching, optimized images, a lean theme and controlled third-party scripts, WordPress sites can pass comfortably.
Do I need a perfect 100 score?
No. Aim to pass all three Core Web Vitals for real users. A perfect lab score is not required and rarely worth the effort.
