Introduction
Core Web Vitals are three measurements Google uses to judge how a page feels to use: how fast the main content appears (LCP), how quickly the page reacts when someone taps or clicks (INP), and whether things jump around while it loads (CLS).
For a business site, that’s more than a technical score. A page that crawls on someone’s phone is a page they leave before they’ve read your offer. This guide explains the three metrics in plain English, how to test them, and which fixes to make first. If you’re still making the case for your site, start with why a professional website matters for every business.
What are the three Core Web Vitals?
They’re LCP, INP and CLS, and each one measures a different moment of the visit.
| Metric | What it measures | Good score | In plain English |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long the biggest thing on screen, usually a hero image or headline, takes to appear | 2.5 seconds or less | Does the page load quickly? |
| INP (Interaction to Next Paint) | How long the page takes to respond when someone clicks, taps or types | 200 milliseconds or less | Does it react when I tap? |
| CLS (Cumulative Layout Shift) | How much the layout moves around while the page loads | 0.1 or less | Does it jump around? |
Google measures these on real visitors’ devices, with mobile and desktop counted separately. To count as “good”, at least 75% of visits need to hit the target. One more thing: INP replaced an older measure called FID in March 2024, so if an article still talks about FID, it’s out of date.
Do Core Web Vitals affect rankings?
Yes, but only as one signal among many. Google counts them as part of its page experience signals. They won’t rescue a thin page, and relevance still matters far more.
The bigger reason to care is the visitor. A slow, jumpy site loses people before they read a word, and that costs you leads whatever your ranking is. So treat Core Web Vitals as a visitor experience problem first and a ranking factor second.
How do you test your Core Web Vitals?
You can do a first check in a few minutes, and it’s free:
- Run your key pages through PageSpeed Insights. Start with the homepage, your top service pages and the contact page.
- Read the real-visitor results first. PageSpeed Insights shows field data (real visitors) and lab data (a simulated test). Field data tells you how you’re really doing, and lab data helps you find the cause.
- Check the Search Console report. The Core Web Vitals report groups your pages into good, needs improvement and poor, so you can see which sets of pages to tackle.
- Test mobile first. Most of your visitors are probably on a phone, and phones are where problems show up.
New or low-traffic pages may have no field data yet. In that case, use the lab results to spot problems and check again after a few weeks.
What should you fix first?
Start with images, hosting and third-party scripts. They’re the usual suspects, and they’re often the quickest wins.
Heavy images (helps LCP). Resize them to the size they’re actually shown, compress them, and use modern formats like WebP. Don’t lazy-load the main image at the top of the page, because that makes it appear later.
Slow hosting and no caching (helps LCP). If your server is slow to respond, nothing else will feel fast. Good hosting, caching and a content delivery network (CDN) make a real difference.
Third-party scripts (helps INP and LCP). Chat widgets, tracking tags, ad scripts and social embeds all add weight. Remove the ones you don’t use, and load the rest as late as you can.
Layout jumps (helps CLS). Set a width and height on images and videos, and reserve space for cookie banners and adverts, so the page doesn’t shuffle as things load.
Heavy themes and plugins (helps INP). Every plugin adds code. If your site feels sluggish when people click, look at what you can remove or replace.
Does your platform make a difference?
Yes, because it decides how much you can change. Website builders are quick to launch, but you can’t always fix what’s slowing a page. A well-built custom site gives you the most control. A headless setup can be very fast, but only if the front end is built carefully. We compare the options in our guide to custom website vs website builder vs headless CMS.
If you’re planning a rebuild, speed is far cheaper to build in from the start than to fix later. Our website development services are one place to start.
How do you keep your scores healthy?
Speed problems tend to creep back in after updates, so a one-off fix isn’t enough. A few habits help:
- Check the Search Console report once a month.
- Test before you add a new plugin, chat widget or tracking script.
- Compress images before they’re uploaded.
- Run a speed check after every redesign or big update.
Regular testing is a big part of this, which we cover in our piece on improving website performance through QA testing. Fast, clean pages are also easier for search and AI systems to read, and our AI search readiness checklist shows what else to check.
Common Core Web Vitals mistakes
Chasing a perfect 100. A top score in a lab test isn’t the goal. Passing with real visitors is.
Testing only on desktop. A site can look fine on a fast office computer and crawl on a phone.
Fixing only the homepage. Your service and contact pages matter just as much.
Compressing images but keeping a dozen tracking scripts. The scripts often cost more than the images.
Adding a plugin to fix a plugin. Another plugin usually means more code to load.
Ignoring real-visitor data. Lab scores can look fine while real visitors have a poor experience.
"One pattern we see again and again on business websites is a homepage that loads far too much at once. A large hero image, a chat widget, three or four tracking tags and a cookie banner all compete for the same few seconds, and the visitor still can’t read a word. Each one was added for a good reason, but nobody went back to ask what they cost together. Resizing that one hero image and trimming the scripts is often the quickest improvement available."
"Picture a typical service page. It opens with a photo that’s far bigger than the space it fills, then loads a chat widget, an analytics tag, an ad pixel and a cookie banner that shoves the text down when it finally appears. On a fast office connection it feels fine. On a mid-range phone, the visitor sees a blank gap and then a page that jumps. Resize the image, hold the chat widget back until someone scrolls, and reserve space for the banner, and the same page usually feels like a different site."
Not sure what’s slowing your site down? Talk to our team about a website speed review.
Frequently Asked Questions
01. What is a good Core Web Vitals score?
For “good”, aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, for at least 75% of visits.
02. Do Core Web Vitals affect SEO?
Yes, as one of several page experience signals. They help, but they won’t make up for weak or irrelevant content, and the bigger benefit is keeping visitors on the page.
03. How long do improvements take to show in Search Console?
Allow about a month. The report is based on a rolling 28 days of real-visitor data, so it takes time to reflect your fixes.
04. What is INP?
INP (Interaction to Next Paint) measures how quickly a page responds when someone clicks, taps or types. It replaced FID as a Core Web Vital in March 2024.
