Google ranks websites partly based on how well they perform for real users.
Core Web Vitals are the specific metrics Google uses to measure this. They track three aspects of user experience: how quickly your main content loads, how fast your site responds to interactions, and whether page elements shift around while loading.
These aren’t just technical benchmarks. Poor Core Web Vitals can cost you visitors, and Google’s ranking systems take them into account.
I wrote this guide for WordPress site owners who want to know what each Core Web Vital measures and how to improve their scores.
In This Article:
What Are Core Web Vitals?
Core Web Vitals are three specific measurements Google uses to judge how good a page’s experience is for real visitors.
Think of them like a health check for your site. Just like a doctor measures your blood pressure, heart rate, and temperature, Google measures your site’s loading speed, responsiveness, and visual stability.
Core Web Vitals are part of Google’s page experience ranking on both mobile and desktop. That means your scores are one of the signals that can affect where your pages show up in search results.
Fewer than half of WordPress sites (about 48%) meet Google’s “good” threshold on all three Core Web Vitals on mobile, according to HTTP Archive’s Core Web Vitals Technology Report.
Why Core Web Vitals Matter for Your Business
Core Web Vitals affect your bottom line, not just your technical to-do list. They can influence how many people find your site, how many stay, and how many convert into customers.
Impact on Search Rankings
Core Web Vitals are part of Google’s page experience signals. Google says Core Web Vitals “are used by our ranking systems,” and it also says “there is no single signal.”
Content quality and relevance come first. In Google’s words, “Google Search always seeks to show the most relevant content, even if the page experience is sub-par.”
Page experience can still tip the balance in competitive niches where content quality is similar. For many searches, plenty of helpful pages are available, and Google says a great page experience “can contribute to success in Search, in such cases.”
Impact on Conversions and Revenue
The business impact of Core Web Vitals goes beyond SEO, because speed can also change how many visitors buy.
In a Deloitte study commissioned by Google, a 0.1-second improvement in mobile site speed lifted retail conversions by 8.4% and average order value by 9.2%.
Here are some verified examples from real businesses:
- Vodafone: Improved LCP by 31% in an A/B test, resulting in an 8% increase in sales
- Rakuten 24: Optimized a landing page for Core Web Vitals and saw a 53% increase in revenue per visitor and a 33% higher conversion rate
- redBus: Improved INP on its search page by 72%, which led to a 7% increase in sales
In each case, the company made the same pages load or respond faster, and sales or conversions went up.
Impact on User Experience
Core Web Vitals measure how frustrating or enjoyable your site is to use, and research shows that speed can change how visitors behave.
In Google’s 2017 mobile research, the probability of a bounce rose 32% as page load time went from one second to three. At six seconds, it rose 106%.
Slow loading, laggy clicks and content that jumps around unexpectedly are the kind of experience that can send visitors away.
A fast, stable site gives visitors fewer reasons to leave and more chances to convert. The opposite is also true. A frustrating experience can cost you more than the current visit, because it can make people less likely to come back.
The Three Core Web Vitals Metrics Explained
Each Core Web Vital has its own “good” threshold, and knowing what each one measures tells you which kind of fix a low score needs.
1. Largest Contentful Paint (LCP)
LCP measures how long it takes for the main content on your page to load.
More specifically, it tracks when the largest image or text block becomes visible. This is usually your hero image, main heading, or the biggest piece of content above the fold.
- Good LCP: 2.5 seconds or faster
- Needs Improvement: 2.5 to 4.0 seconds
- Poor LCP: Over 4.0 seconds
Four common causes of a slow LCP are:
- Large, unoptimized images
- Slow server response times
- Render-blocking JavaScript and CSS
- Client-side rendering delays
Slow server response is the first of these to rule out, because every other part of the page load waits on it.
2. Interaction to Next Paint (INP)
INP measures how quickly your site responds when someone clicks, taps, or types.
This metric replaced First Input Delay (FID) in 2024, so you may still see FID in older tools and articles. Unlike FID, which only measured the first interaction, INP looks at every click, tap and key press during a page visit.
It then reports roughly the slowest one. On very busy pages, Google ignores one outlier for every 50 interactions.
- Good INP: 200 milliseconds or less
- Needs Improvement: 200 to 500 milliseconds
- Poor INP: Over 500 milliseconds
Think about it from a user’s perspective. You click a button and nothing happens, so you click again, and there’s still nothing.
When something finally loads half a second later, that frustration can make people leave.
Four common causes of a slow INP are:
- Heavy JavaScript execution
- Long tasks blocking the main thread
- Slow event handlers
- Excessive third-party scripts
INP pass rates are lower on mobile than on desktop, so it’s worth testing your site on a phone, not just a laptop.
3. Cumulative Layout Shift (CLS)
CLS measures how much your page content moves around as it loads.
If you’ve ever been reading an article when the text suddenly jumped down because an ad loaded, you’ve seen layout shift.
It can also move a button just as you’re about to click it, so you end up clicking something else by mistake.
- Good CLS: 0.1 or less
- Needs Improvement: 0.1 to 0.25
- Poor CLS: Over 0.25
A stable layout helps visitors trust that they’ll tap what they meant to tap.
Yahoo! JAPAN News fixed a CLS problem of about 0.2. Afterward, it saw 15.1% more page views per session, 13.3% longer sessions, and a bounce rate 1.72 percentage points lower.
Five common causes of layout shifts are:
- Images without defined width and height attributes
- Ads, embeds, and iframes that load after other content
- Dynamically injected content
- Web fonts that cause text to jump
- Actions waiting for a network response before updating DOM
These causes have one thing in common: the browser doesn’t know how much space an element needs until it loads.
How to Measure Your Core Web Vitals
Before you can improve your Core Web Vitals, you need to know where you stand.
Google provides several free tools to measure these metrics, and you can also check them inside WordPress.
1. Google PageSpeed Insights
Google PageSpeed Insights is my go-to tool for a quick check of a single page. It’s free, easy to use, and gives you specific recommendations.
All you have to do is go to PageSpeed Insights and enter your URL. Then, click Analyze and wait about 30 seconds for the results.
You’ll get separate results for Mobile and Desktop. The Discover what your real users are experiencing panel shows field data, meaning real-visitor data from Chrome users who visit your site.
Google Search uses that field data, known as CrUX, for page experience. Further down, a lab test (a simulated page load) diagnoses performance issues. Lab tests can’t measure INP, so the lab section uses Total Blocking Time instead.
Pay extra attention to the Mobile results. Mobile scores tend to run lower than desktop scores. Google assesses page experience separately for each device, so your mobile Core Web Vitals count toward mobile search.
2. Google Search Console
If you’ve verified your site with Google Search Console, you already have access to Core Web Vitals data.
Go to Experience » Core Web Vitals in the left sidebar, and you’ll see:
- Which URLs have poor, need improvement, or good scores
- Trends over time
- Specific issues affecting your pages
The advantage of Search Console is that it groups similar pages across your site, which helps you spot patterns and decide which fixes to make first.
3. MonsterInsights Site Speed Report (Inside WordPress)
If you’re running a WordPress site, I recommend checking your Core Web Vitals with the Site Speed report in MonsterInsights, the WordPress analytics plugin. It puts your scores in your WordPress dashboard, so you don’t need to leave your site to check them.
Go to Insights » Reports » Site Speed and click Run Audit to test your site. MonsterInsights runs a Google PageSpeed Insights audit and shows the results in your dashboard.
The report opens in desktop view, so click the phone icon to see your mobile results.
The mobile view below has an Overall Score and cards for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. It also shows Server Response Time, First Contentful Paint and Total Blocking Time.
Under the cards, the How to Improve list starts with the metric that scored lowest, so the first item is the one to fix first.
The report gives you one site-level result rather than a score for each page. For page-by-page detail, PageSpeed Insights tests any single URL, and Search Console groups similar pages across your site. The Site Speed report is available on MonsterInsights Plus and above.
4. Chrome User Experience Report (CrUX)
CrUX provides real-world data from actual Chrome users. It’s the same real-visitor data Google Search uses for page experience.
You can access CrUX data through:
- PageSpeed Insights (it shows CrUX data automatically)
- CrUX Vis, Google’s tool for charting CrUX data over time
- BigQuery or the CrUX API for bulk data analysis
CrUX only includes your site if it gets enough Chrome traffic, so smaller sites might not have CrUX data available.
Whichever tool you use, I’d check your scores on several pages, not just your homepage. Product pages, blog posts and landing pages can perform quite differently, so start with the pages that get the most traffic or drive the most conversions.
6 Steps to Improve Core Web Vitals in WordPress
Below are the practical steps that actually work for improving Core Web Vitals in WordPress. I’ll focus on changes you can make right now without being a developer.
The steps start with your hosting, move on to site-wide trims and the fixes for each metric, and end with how to check your progress.
Step 1: Check Whether Your Hosting Is Slowing Down Your Pages
Before a browser can show anything on your page, your server has to answer. That wait is called Time to First Byte (TTFB), and it’s the first part of every LCP measurement.
TTFB isn’t a Core Web Vital itself, but it sets the floor for your loading speed. Google’s web.dev guide to LCP warns that “a high TTFB can make achieving a 2.5 second LCP challenging, or even impossible.”
On a well-optimized page, web.dev suggests TTFB should take up roughly 40% of LCP. WordPress sites have room to improve here. The same HTTP Archive report shows only about 23% of WordPress sites have a good TTFB on mobile, about half the rate for the web overall.
How to Tell If Hosting Is the Bottleneck
I’d recommend checking your server response time before you pay for a new host or another plugin, so you know whether the server is really the problem.
In PageSpeed Insights, look in the Discover what your real users are experiencing panel under Other notable metrics for Time to First Byte (TTFB). web.dev rates a TTFB of 0.8 seconds or less as good and anything over 1.8 seconds as poor.
In the lab section further down, the LCP breakdown insight shows how much of your LCP is server time. Lighthouse’s Document request latency check also flags server responses over 600 ms. You’ll find it under Insights, or under Passed audits if your server is already fast.
If you use MonsterInsights, the Site Speed report gives you a second check. Open Server Response Time under How to Improve, and you’ll see a goal of 600ms or less, the same limit Lighthouse uses.
The panel’s advice is to use a caching plugin, which is the right first move. How your TTFB behaves once caching is on tells you where the rest of the delay comes from.
If TTFB stays high even on simple cached pages, like a blog post viewed while logged out, the server or its location is the likely limit. If it’s high only on pages that can’t be cached, like WooCommerce cart, checkout and account pages, the PHP and database work behind them could be the cause.
More server resources or object caching can help with those uncached pages.
What Your Host Controls
Some TTFB fixes are in your hands, and others only your host can make. Knowing which is which keeps you from buying another plugin to solve a server problem.
Your host controls the server’s resources, such as CPU, memory and PHP workers, and whether you share them with other sites. Google’s guide to optimizing TTFB notes that shared hosting is generally slower, and it says “hosting should be the first thing you consider.”
Your host also controls server software versions, server-level page caching and, often, a CDN. You control your plugins, theme, caching-plugin settings, redirects and image sizes.
If your host turns out to be the bottleneck, Levamo is managed WordPress hosting with several of these server-side fixes built in. It runs on LiteSpeed, with server-level page caching for anonymous visitors, so cached pages aren’t rebuilt for every visit. Every plan includes Cloudflare’s Enterprise CDN, which serves your site’s files from 300+ locations close to your visitors. Each site also runs in its own isolated container with dedicated CPU, RAM and PHP workers, so another customer’s traffic spike doesn’t eat into your site’s resources. On Business plans and above, a KeyDB and Redis object cache keeps carts, checkouts and logged-in pages from repeating the same database lookups.
Levamo’s site quotes customer Chris Klosowski, President of Easy Digital Downloads: “Our time to first byte was cut in half, if not more, right out of the gate.” Levamo’s team also handles migrations for free, with little to no downtime.
To compare your options, see our list of the best managed WordPress hosting providers.
Check Before You Switch
If your TTFB is still poor after you’ve set up caching, a faster host is likely to do more for your LCP than another optimization plugin.
Once your server answers quickly, the next place to look is the code your theme and plugins add to every page.
Step 2: Trim Your Theme and Plugins
A few site-wide changes, like a lighter theme and fewer plugins, can help more than one Core Web Vital at the same time.
Use a Lightweight Theme
A bloated theme can add extra code to every page on your site. I’d recommend a theme that markets itself on speed, like Sydney, GeneratePress, or Kadence.
Before you switch, test the new theme on a staging copy of your site, so a layout problem doesn’t reach your live pages.
Delete Unused Plugins
Every active plugin can add code to your pages, so an active plugin you no longer need is pure cost. If you have been adding lots of plugins to your site without much thought, I recommend running a plugin audit.
Start with the plugins that are switched on. Go to Plugins » Installed Plugins in your WordPress dashboard, click Active, and click Deactivate under any plugin your site no longer needs.
Before you deactivate one, check that your site doesn’t depend on it right now, for example for forms, security or the page builder behind your live pages.
WordPress doesn’t load inactive plugins, so removing them won’t make your pages faster. It’s still worth doing, because it keeps your plugin list short and easy to review. Click Inactive to see the plugins you’ve switched off, then click Delete under any you won’t use again.
Choosing new plugins carefully from here on keeps your site from slipping back into the same problem.
Step 3: Fix Your Loading Speed (LCP)
LCP is the Core Web Vital that WordPress sites miss most often. Only about 55% of WordPress sites have a good LCP on mobile, according to the same HTTP Archive report, which is the lowest pass rate of the three.
That makes LCP the best place to start once your server is fast.
Optimize Your Images
On most mobile pages, the largest element is an image, so how that image is delivered matters. Here’s what to do:
- Compress images before uploading with a free tool like TinyPNG
- Install ShortPixel to optimize new uploads automatically
- Resize images to the size they’re displayed at and serve WebP or AVIF (a plugin like Imagify can convert them for you)
- Don’t lazy-load the main image at the top of the page, since that delays when it starts downloading
Smaller, properly sized images shorten the part of LCP your image settings control: the time the main image takes to download.
Enable Caching
Caching saves a ready-made copy of each page, so your server doesn’t rebuild the page for every visitor. That cuts server response time. A speed plugin like WP Rocket or W3 Total Cache (a free option) handles the technical work for you.
Once it’s installed, turn on page caching and browser caching in its settings.
Add a CDN
A Content Delivery Network (CDN) serves your site’s files from servers near each visitor, which cuts the time to first byte.
We’ve compared the best CDNs for WordPress if you’d like help picking one.
Step 4: Fix Responsiveness (INP)
INP fixes can take more work than image or caching changes, because they involve JavaScript. You can start with the two changes below, which don’t require a developer.
Reduce Third-Party Scripts
Each chat widget, ad network and tracking script you add can keep the browser busy, so it’s slower to respond to clicks and taps. That’s why I’d recommend removing any you no longer need.
To see which ones load on a page, check the 3rd parties insight in your PageSpeed Insights results.
Delay Non-Essential JavaScript
Many caching and performance plugins include a setting to delay or defer JavaScript. In WP Rocket, the setting is called Delay JavaScript execution, on the File Optimization tab. W3 Total Cache Pro has a similar feature called Delay Scripts.
Delaying scripts tells your site to load important content first and scripts second. After you turn it on, check that your menus, forms and sliders still work.
For more fixes, see web.dev’s guide to optimizing Interaction to Next Paint.
Step 5: Fix Visual Stability (CLS)
Most CLS fixes work by reserving space for content before it loads.
Set Image Dimensions
Setting a width and height on each image lets the browser hold the right amount of space, so content doesn’t jump around when the image loads.
Many page builders do this automatically. If you’re using the block editor, WordPress handles it for you in newer versions.
Reserve Space for Ads and Embeds
If you use ads, tell your ad plugin to reserve space. Many ad plugins have a setting for this.
For videos and other embeds, give the container a fixed size or aspect ratio, so it doesn’t grow after the embed loads.
Avoid Pop-ups That Push Content Down
Pop-ups that push your content down the page cause layout shifts. An overlay, or a notification that slides in from the side, shows the same message without moving anything.
Load Web Fonts Without Shifting Text
Web fonts can make text jump when the browser swaps in the final font. Preloading your main font, or using font-display: optional, can stop that swap from moving your text.
For more fixes, see web.dev’s guide to optimizing Cumulative Layout Shift.
Step 6: Track Your Progress
A quick re-check after each fix shows whether the change actually moved your Core Web Vitals.
The MonsterInsights Site Speed report shows only your latest audit, so write down your current numbers before you make a change. Afterward, re-test the mobile view first: click the phone icon beside the report title, then click Run Audit.
A site note is a handy place to keep your before numbers. On the Overview report, click the Site Notes tab under the traffic graph to open the panel, then click Add New Site Note.
Give the note a date and a name that includes your before score, such as “Compressed hero images, mobile LCP was 4.2s.” The note then marks that date on the traffic graph.
To find out whether visitors behaved differently after a fix, open Charlie Chat by clicking the purple mascot icon in the bottom-right corner of any report page. You can then ask a question such as “How did bounce rate change after October 6?” Charlie Chat is included on every plan, with a monthly allowance of questions.
For real-visitor data, open the Core Web Vitals report in Search Console and click Validate fix once you’ve fixed an issue. Google then starts a 28-day monitoring session, so improvements show up gradually.
Frequently Asked Questions About Core Web Vitals
Does hosting affect Core Web Vitals?
Yes. Your host affects server response time, also called Time to First Byte (TTFB), which is the first part of every Largest Contentful Paint (LCP) measurement. A slow or overloaded server delays everything that loads after it. Caching and a CDN can help, and you can check your TTFB in PageSpeed Insights under Other notable metrics.
Are Core Web Vitals a ranking factor?
Yes. Google says Core Web Vitals are used by its ranking systems, and it highly recommends good Core Web Vitals for success with Search. They became part of page experience ranking on mobile in 2021 and on desktop in 2022.
How long does it take to improve Core Web Vitals?
It depends on the fix. Turning on caching can take minutes, while JavaScript changes can take longer. Search Console’s Core Web Vitals report uses a rolling 28-day window of real-user visits, so improvements show up gradually over about four weeks. After you fix an issue, click Validate fix to start Google’s 28-day monitoring session.
Can I check Core Web Vitals in Google Analytics?
Google Analytics doesn’t have a built-in Core Web Vitals report. If you use MonsterInsights for WordPress, its Site Speed report shows your Core Web Vitals in the same WordPress dashboard as your Google Analytics reports.
What’s the best tool to track Core Web Vitals?
It depends on what you need. Google Search Console shows real-visitor data grouped across your site, and PageSpeed Insights tests any single page. In WordPress, the MonsterInsights Site Speed report shows your scores in your dashboard and lists the lowest-scoring metric first.
What is the most important Core Web Vital?
Google treats all three as equally part of the assessment, so a page needs good scores on all three to pass. On WordPress sites, LCP is the one most often missed, which makes it a sensible first fix.
Will fixing Core Web Vitals guarantee higher rankings?
No. Core Web Vitals are one of many signals Google uses. Google says its search “always seeks to show the most relevant content, even if the page experience is sub-par.” However, when you’re competing with similar content, good Core Web Vitals can help set your pages apart.
Improving Core Web Vitals doesn’t just help your rankings. It makes your site better for real people, with faster loading, quicker responses and stable layouts.
Start with whichever metric your own report shows as weakest, and check your server response time first. You don’t need perfect scores, either. The goal is to meet the “good” thresholds consistently across your most important pages.
I hope this article helped you understand and improve your Core Web Vitals. If you liked this article, check out the following beginner-friendly guides:
- Google Ranking Factors for 2026 (The 10 Most Important)
- How to Increase Organic Traffic in 2026 (12 Best Ways)
- How to Add Google Analytics to WordPress
- Smart Tactics to Reduce Shopping Cart Abandonment
- How to Optimize for E-E-A-T (Proven Strategies That Work)
Follow us on Twitter, Facebook, and YouTube for more Google Analytics tips.