Core Web Vitals are Google’s three main user experience measurements: how quickly your main content loads, how fast the page responds when someone taps or clicks, and whether the layout jumps around while loading. In plain English, they tell you whether your website feels fast, stable and usable.
What Core Web Vitals actually measure
Core Web Vitals measure real user experience, not whether your website looks pretty in a designer’s portfolio. Google uses them to understand whether a page is pleasant to use, especially on mobile, where most small business websites quietly fall apart.
They sit inside the wider “page experience” idea. That includes things like mobile usability, HTTPS, intrusive pop-ups and general usability. Core Web Vitals focus on three measurable parts of the experience:
- Loading speed
- Interaction speed
- Visual stability
That means Google is not just asking, “Does this page have the right words on it?” It is also asking, “Can a normal person actually use this thing without wanting to throw their phone into a hedge?”
For a business owner, that matters because people are impatient. If your page takes ages to load, buttons lag, or the page jumps just as someone tries to tap “Call now”, you are making enquiries harder than they need to be. And making enquiries harder is a daft commercial strategy.
The three Core Web Vitals in plain English
There are three Core Web Vitals: LCP, INP and CLS. The names sound like someone sneezed into a spreadsheet, but the ideas are simple enough.
| Metric | Full name | What it means | Good score |
|---|---|---|---|
| LCP | Largest Contentful Paint | How quickly the main visible content loads | 2.5 seconds or less |
| INP | Interaction to Next Paint | How quickly the page responds to clicks, taps and typing | 200 milliseconds or less |
| CLS | Cumulative Layout Shift | How much the layout moves around while loading | 0.1 or less |
LCP usually relates to the big thing people came to see first: a hero image, heading, banner, product image or main block of text.
INP replaced FID as a Core Web Vital in 2024. It measures responsiveness across the visit, not just the first click.
CLS measures jumpiness. You know when you go to tap a button and an advert, image or cookie banner shoves everything down? That is CLS being a pain in the backside.
What counts as a good Core Web Vitals score
Google groups Core Web Vitals into three buckets: good, needs improvement and poor. These scores are based on field data where available, which means real users on real devices, not just a lab test on your office Wi-Fi.
According to Google’s Core Web Vitals guidance, a page should meet the recommended thresholds for at least 75% of page visits. So if your site performs brilliantly for you on your expensive laptop but badly for customers on patchy 4G, Google is more interested in the customer experience. Fair enough, really.
A good score does not mean every page must be instant. It means the experience is fast enough, responsive enough and stable enough for most users.
Here is the simple version:
| Status | What it usually means | What to do |
|---|---|---|
| Good | The page is broadly fine | Monitor it and avoid breaking it |
| Needs improvement | There are issues, but probably fixable | Prioritise the worst templates or pages |
| Poor | Users are likely having a bad time | Fix it before obsessing over new content |
If several key pages are poor, that is not “just a developer thing”. That is a lead generation problem.
Why Core Web Vitals matter for SEO
Core Web Vitals are a ranking factor, but they are not magic ranking dust. If your page is useless, making it fast will simply create a fast useless page. Congratulations, you have built a Ferrari with no steering wheel.
Google still cares most about relevance, content quality, trust and whether your page answers the search properly. But when competing pages are similar, user experience can help tip the balance. A fast, stable, usable page is a better result than one that loads like it is being powered by a hamster on a treadmill.
Core Web Vitals are part of technical SEO. They sit alongside crawlability, indexation, site structure, redirects, canonical tags, schema and all the other boring-but-important stuff that keeps a website from collapsing quietly in the background.
If you want the wider technical side looked at properly, SEO Bridge offers technical SEO services for businesses that need someone to find the mess, explain it clearly and fix what actually matters.
For more detail on the speed side specifically, I’ve also written about page speed and why slow websites suffer in Google.
Why Core Web Vitals matter for leads
SEO rankings are useful, but leads pay the bills. Core Web Vitals matter because poor performance quietly kills enquiries after people have already found you.
A slow website creates friction. A laggy form creates doubt. A jumpy page creates mistakes. None of that helps when someone is comparing three local businesses and wants the easiest one to contact.
This is especially important for local service businesses. If someone searches for an emergency plumber, solicitor, accountant, wedding venue or builder, they are not settling in with a cup of tea to admire your brand story. They want proof, price clues, trust signals and a clear next step. Fast.
Bad Core Web Vitals can affect:
- Calls from mobile visitors
- Form submissions
- Quote requests
- Product purchases
- Trust before someone contacts you
This also matters for AI search and answer engines. Clear, fast, well-structured pages are easier for systems to crawl, understand and recommend. That is why services like SEO Bridge’s AI, AEO and GEO work still depend on solid technical foundations. The same applies outside the UK too, where agencies such as Kell Web Solutions for Answer Engine Optimization in Orange County focus on turning visibility into real enquiries.
How to check your Core Web Vitals
Start with Google Search Console. It is free, and if your site is verified, it will show Core Web Vitals reports for mobile and desktop. This is the first place I would look because it uses grouped URL data and real user signals where Google has enough information.
If you are not using it yet, sort that out. I’ve written a plain-English guide to Google Search Console for small businesses if you need help getting past the “what the hell am I looking at?” stage.
You can also use PageSpeed Insights. It gives you two types of information:
- Field data, based on real users where available
- Lab data, based on a controlled test
Field data is usually more useful for SEO decisions. Lab data is useful for diagnosis. Do not panic if the lab score changes between tests. Speed tools are not blood pressure monitors, and even those can be dramatic.
Look first at your most important pages: homepage, service pages, location pages, product categories and enquiry pages. Fixing a random blog post nobody reads is not the priority.
The usual things that ruin Core Web Vitals
Most Core Web Vitals problems come from the same suspects. Once you have seen enough websites, the crime scene becomes depressingly familiar.
Common causes include:
- Huge images uploaded straight from a camera
- Cheap hosting that struggles under basic traffic
- Bloated WordPress themes doing 400 things you do not need
- Too many plugins fighting each other like drunk uncles at a wedding
- Tracking scripts, chat widgets and pop-ups loading everywhere
- Sliders, animations and video backgrounds slowing the first view
- Fonts loading badly and shifting the page around
- Cookie banners pushing content after the page loads
The problem is rarely one thing. It is usually the combined weight of years of “just add this quick plugin” decisions.
This is why Core Web Vitals work should start with diagnosis, not random fixes. Compressing images might help LCP. Removing unused JavaScript might help INP. Reserving image space might help CLS. But if you guess, you waste time.
And if your developer says “it works fine on my machine”, congratulations, you have discovered the least useful sentence in web development.
How to improve LCP
LCP is about how quickly the main content appears. If your LCP is poor, the page feels slow because the thing people actually need is taking too long to show up.
The usual fixes are practical:
- Compress large images without making them look like they were faxed in 1998
- Use modern image formats where appropriate, such as WebP or AVIF
- Avoid massive hero images on mobile when a smaller one will do
- Improve hosting if server response time is poor
- Remove render-blocking CSS and JavaScript where possible
- Use caching and a sensible content delivery network if the site needs it
Do not start by deleting half your website. Start with the biggest element above the fold. On many small business sites, that is a huge banner image with text baked into it, which is bad for speed, accessibility and SEO. A proper heading in HTML plus a properly sized image is usually better.
Also check whether the same heavy template is used across all service pages. Fixing one template can improve dozens of URLs. That is the sort of win we like.
How to improve INP
INP measures how quickly your page responds when someone interacts with it. If users tap a menu, click a button or type into a form and the page hesitates, INP can suffer.
This often comes from too much JavaScript. Modern websites love JavaScript. Sometimes they love it the way toddlers love glitter: everywhere, unnecessary, and somehow still appearing weeks later.
To improve INP, focus on reducing the work the browser has to do when someone interacts with the page. That may mean removing unnecessary scripts, delaying non-essential code, simplifying heavy features or replacing bloated plugins.
Common INP troublemakers include:
- Chat widgets loading on every page
- Complex booking tools
- Heavy sliders and animations
- Poorly built forms
- Excessive tracking tags
- Page builders producing messy code
You do not have to remove every useful feature. You do need to decide whether each feature earns its keep. If a live chat widget adds half a second of delay and nobody uses it, bin it. If a booking system drives actual enquiries, optimise it rather than ripping it out.
Business impact matters more than technical purity.
How to improve CLS
CLS is about layout stability. A page with poor CLS moves around while loading. This is annoying for users and terrible for trust.
The classic example is someone going to tap “Book a consultation” and the page suddenly shifts, so they tap something else. That is not a small issue. That is your website physically moving the goalposts while the customer is trying to pay you.
To reduce CLS, make sure your page reserves space for things before they load. Images, videos, adverts, embeds, banners and forms should not suddenly shove content down the screen.
Practical fixes include:
- Set width and height attributes for images and videos
- Reserve space for banners, maps and embeds
- Avoid injecting content above existing content after load
- Load fonts in a way that prevents sudden text shifts
- Make cookie notices overlay cleanly instead of pushing the page around
CLS can also come from sloppy design decisions. If mobile pages are full of sticky bars, pop-ups, banners and review widgets, things start jumping. Your site does not need to attack the visitor from every angle. Calm down. Give them the information and a clear action.
Why WordPress sites often struggle
WordPress is not bad for Core Web Vitals. Bad WordPress builds are bad for Core Web Vitals. There is a difference.
A clean WordPress site on decent hosting can perform very well. The problems usually start when a site has a heavy theme, a drag-and-drop builder, 37 plugins, three analytics tools, two chat widgets and a homepage video because someone thought it looked “premium”.
If you have just paid for a new website and it looks nice but gets no leads, Core Web Vitals may be part of the problem. Not always, but often enough to check.
WordPress performance work normally involves looking at:
- Hosting quality
- Theme and builder bloat
- Plugin load
- Image handling
- Caching setup
- Database clutter
- Mobile templates
This is also where SEO and development need to talk to each other. Pretty design, technical health and search visibility cannot live in separate boxes. If your WordPress site is struggling, WordPress SEO support can help connect the technical fixes with the pages that need to rank and convert.
Do not chase perfect scores like a lunatic
A perfect PageSpeed score is not the goal. More enquiries are the goal. If you forget that, you can waste days polishing tiny issues while your service pages still say nothing useful.
Core Web Vitals should be prioritised based on commercial impact. Fix the pages that matter first. Your homepage, main service pages, high-traffic blog posts, product pages and enquiry paths deserve attention before obscure pages buried six clicks deep.
Here is the sensible way to think about it:
| Bad priority | Better priority |
|---|---|
| Chasing 100/100 on every page | Getting key pages into the “good” range |
| Fixing tiny warnings with no user impact | Fixing slow, unstable mobile templates |
| Removing useful features blindly | Measuring which features hurt performance |
| Testing only on desktop | Checking mobile performance first |
| Treating speed as separate from leads | Tracking enquiries after fixes |
If a page already loads quickly, ranks well and converts, do not break it chasing a prettier score. Google does not hand out trophies for pleasing tools. Users do not care whether your score is 96 or 100. They care whether the page works.
What to do next if your scores are poor
If your Core Web Vitals are poor, do not panic and do not immediately approve a full redesign. A redesign can help, but it can also make things worse if nobody protects the SEO foundations. I have seen that particular car crash plenty of times.
Start with a simple order of attack:
- Check Google Search Console for affected URL groups.
- Test the most important pages in PageSpeed Insights.
- Identify whether the main issue is LCP, INP or CLS.
- Fix template-wide problems before individual one-off pages.
- Retest after changes and wait for field data to update.
- Track enquiries, calls and form submissions, not just scores.
If the site is new, slow and generating nothing, get it checked properly before throwing more money at content or ads. Sending paid traffic to a slow, jumpy site is like pouring water into a bucket with a hole in it, then blaming the water.
And if you want someone to tell you what actually matters rather than bury you in a 90-page report nobody reads, that is exactly what proper technical SEO is for.
Frequently Asked Questions
Are Core Web Vitals a Google ranking factor? Yes, Core Web Vitals are part of Google’s page experience signals. They can influence rankings, especially when competing pages are otherwise similar. They are not more important than relevance, quality content or trust. A fast page with poor content will still struggle, but a slow page can hold back otherwise decent SEO work.
What are the three Core Web Vitals? The three Core Web Vitals are LCP, INP and CLS. LCP measures how quickly the main visible content loads. INP measures how quickly the page responds to user interactions. CLS measures how much the layout shifts while loading. Together, they show whether a page feels fast, responsive and stable.
How do I check Core Web Vitals for my website? Use Google Search Console first, because it shows Core Web Vitals data for your site using real user information where available. You can also test individual pages with PageSpeed Insights. Check mobile results carefully, as many business websites perform worse on phones than desktops, especially with large images and heavy scripts.
What is a good Core Web Vitals score? A good score means LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less. Google generally assesses this at the 75th percentile of page visits. In plain English, most users should get a fast, responsive and stable experience most of the time.
Can I fix Core Web Vitals without a developer? You can fix some basics yourself, such as compressing images, removing unused plugins and choosing better hosting. More complex issues involving JavaScript, render-blocking resources, layout shifts or server performance usually need technical help. If you are not confident, do not guess wildly. Guessing can break layouts, tracking or forms.
Do Core Web Vitals matter for local SEO? Yes, but they are only one part of local SEO. Your Google Business Profile, reviews, service pages, location relevance and local authority still matter more overall. Core Web Vitals help because mobile visitors from local searches need fast pages and clear enquiry paths. Slow pages can reduce calls and form submissions, even when rankings are decent.
