If you’ve opened Google Search Console and seen a report warning about “poor URLs”, or a developer has sent you a PageSpeed score in red, you’ve already met Core Web Vitals. They’re three measurements Google uses to judge how a page feels to a real visitor: how fast the main content appears, how quickly the page reacts when someone taps or clicks, and whether things jump around while it loads. This guide explains each one in plain terms, what usually causes problems on small business sites, and which fixes are worth paying for.
What Core Web Vitals actually measure
There are three metrics. Each has a “good” threshold, and Google assesses them using data from real Chrome users visiting your site, not just a one-off lab test.
Largest Contentful Paint (LCP): loading
LCP is the time it takes for the biggest visible element on the screen, usually a hero image, a banner or a large heading, to finish appearing. Google considers 2.5 seconds or less to be good. On a typical small business homepage, the culprit is almost always a huge, uncompressed hero photo or a slider loading several large images at once.
Interaction to Next Paint (INP): responsiveness
INP measures how long the page takes to visibly respond after a visitor does something: taps a menu button, opens an accordion, types in a form. Good is 200 milliseconds or less. INP replaced an older metric called First Input Delay in 2024, so if you read older articles that mention FID, that’s why. Poor INP usually comes from too much JavaScript: chat widgets, tracking scripts, heavy page builder add-ons and pop-up tools all competing for the browser’s attention.
Cumulative Layout Shift (CLS): visual stability
CLS scores how much the layout moves unexpectedly while the page loads. You know the experience: you go to tap a link and an advert or cookie banner pushes it down, so you tap the wrong thing. Good is a score of 0.1 or less. Common causes are images without set dimensions, fonts that swap late and change the size of text, and banners injected at the top of the page after it has started rendering.
Do Core Web Vitals affect your Google rankings?
Yes, but probably less than you’ve been told. Google includes them as part of its page experience signals, and it has been clear that great content relevant to the search still matters more. A slow page with exactly the information someone needs can outrank a fast page that doesn’t answer the question.
The stronger reason to care is your visitors. A page that takes several seconds to show anything on a phone, or that moves the “Call now” button just as someone reaches for it, loses enquiries regardless of rankings. Treat these metrics as a customer experience measure that happens to also feed into search engine optimization, rather than a magic ranking lever.
How to check your scores
- Google Search Console. Its page experience reporting groups your URLs into good, needs improvement and poor, separately for mobile and desktop. It uses real visitor data, so it’s the most reliable view. Google’s help article on the Core Web Vitals report explains how to read it.
- PageSpeed Insights. Enter any URL and you’ll see two sections: field data from real users (if your site has enough traffic) and a lab test. Focus on the field data at the top. The lab score below is useful for diagnosing problems, but it’s a simulation on a throttled connection.
- Your own phone. Load your site on mobile data, not office Wi-Fi. Watch what appears first and whether anything jumps. It’s not scientific, but it shows you what customers see.
A note on small sites: if your website gets modest traffic, Google may not have enough real-user data to report on it. In that case you’ll only see lab results, which is fine; use them as a guide.
The fixes that usually matter most
On the WordPress sites I work on, the same handful of issues accounts for most poor scores. In rough order of impact:
For LCP
- Resize and compress the hero image, and serve it in a modern format like WebP or AVIF.
- Don’t lazy-load the main image at the top of the page. Lazy-loading is great for images further down, but applied to the hero it delays the very thing LCP measures.
- Replace auto-playing sliders with a single strong image. They’re heavy, and visitors rarely see past the first slide anyway.
- Use page caching and decent hosting. If the server takes a second just to start responding, everything else is behind before it begins.
For INP
- Audit third-party scripts. Every chat widget, heatmap tool, social feed and ad pixel adds work. Remove the ones nobody looks at.
- Delay non-essential scripts until after the page has loaded or until the visitor interacts.
- Reduce plugin bloat. Several plugins doing overlapping jobs often load scripts on every page, even where they aren’t used.
For CLS
- Give every image and video width and height attributes so the browser reserves the space.
- Reserve space for embeds, ads and cookie banners, or show banners as overlays that don’t push content.
- Preload your main web font and use sensible fallback settings so text doesn’t reflow.
Many of these overlap with the general advice in my guide on how to speed up a WordPress website without breaking it, which goes deeper on caching and image optimisation. Mobile matters most here, since that’s where scores tend to be worst; my post on mobile-friendly website design covers the layout side.
When a quick fix isn’t enough
Sometimes the problem is structural. A theme that loads its entire feature set on every page, or a page builder layout nested ten levels deep, can only be optimised so far with plugins. At that point it may be more cost-effective to rebuild key templates in a lighter theme than to keep stacking optimisation plugins on top. That’s a judgement call that depends on the site, which is why I’d suggest an audit before agreeing to any big spend.
As for cost: a straightforward clean-up of images, caching and scripts on a small site might be a few hours of work. A partial rebuild is a larger project. Be wary of anyone guaranteeing a perfect 100 score; lab scores fluctuate, and chasing the last few points rarely changes anything for your customers.
Frequently Asked Questions
My PageSpeed score is low but Search Console says my pages are good. Which is right?
Search Console, in most cases. It reflects what real visitors experience. The PageSpeed lab score simulates a slow phone on a slow connection, so it’s often harsher. Use the lab report to find issues, not as your pass or fail mark.
How long until changes show up in Search Console?
The field data is based on a rolling 28-day window, so improvements appear gradually over about a month. You can use the “Validate fix” option in Search Console to start tracking.
Can a plugin fix these scores on its own?
A good caching and optimisation plugin helps, but it can’t fix an oversized hero image you upload next week or a heavy theme. Settings also need testing, because aggressive options can break menus and forms.
Need help?
If Search Console is flagging slow pages and you’re not sure where to start, I can review the site and tell you which fixes are worth doing. I offer this as part of my website development work, and you can read what past clients say on the testimonials page. Get in touch with your site address and I’ll reply within 24–48 hours.