Website speed and Core Web Vitals explained for business owners

A slow website costs you customers before they have read a word. Someone on a mobile connection in a busy market, a commuter on a train or a customer on an older phone will simply go back and tap the next result. Google has a set of measurements for this called Core Web Vitals. This guide explains them without jargon, shows how to check your own site, and lists the fixes that most often help small business websites.

What Core Web Vitals are

Core Web Vitals are three measurements of how a page feels to a real visitor: how quickly the main content appears, how quickly the page responds when you tap something, and whether things jump around while it loads. Google's documentation on web.dev describes them in detail, and Google Search uses them as part of its page experience signals.

It's worth being clear about their weight. Google's Search Central documentation says that good page experience is one factor among many, and that relevant, helpful content still matters most. A fast page with weak content won't rank on speed alone. But between two similar pages, the one that loads well can have the edge, and it will almost certainly convert more of its visitors into enquiries.

The three measurements in plain words

These thresholds come from web.dev's guidance, which also explains that a page is judged at the 75th percentile of real visits. In simple terms, most of your visitors, not just the ones on fast connections, should get a good experience. INP replaced an older measurement called First Input Delay in 2024, so if you read older articles mentioning FID, that's why.

An everyday way to think about them

• LCP is how long a customer waits at the door before the shop lights come on.
• INP is how long the shopkeeper takes to look up when you ask a question.
• CLS is the shelf moving just as you reach for something, so you grab the wrong item. On a website, it is when you go to tap "Call" and an advert pushes the button down, so you tap something else.

How to check your site for free

1. Go to PageSpeed Insights and enter the address of your homepage.
2. Look first at the top section, which shows real-user data if Google has enough visits to your site. This reflects what your actual visitors experience. Smaller sites may not have enough data, which is normal.
3. Then look at the lab test lower down. It simulates a mid-range phone and lists specific problems under "Diagnostics" and opportunities to improve.
4. Repeat for your most important pages, such as your main service page and contact page, not just the homepage.
5. In Google Search Console, open the Core Web Vitals report to see which groups of pages are rated good, needing improvement or poor.

Don't chase a perfect 100 score in the lab test. The score is a helpful guide, but what counts is whether real visitors get a good experience and whether the three measurements pass.

The fixes that usually make the biggest difference

For a slow LCP

• Shrink your images. This is the most common problem we see. A photo straight from a phone can be several megabytes; resized to the size it is actually shown and saved in a modern format such as WebP or AVIF, it is often a small fraction of that.
• Don't lazy-load the main image. Lazy loading is good for images further down the page, but the hero image at the top should load straight away.
• Replace a heavy slider with a single strong image. Sliders load several large images and scripts for something few visitors watch.
• Use decent hosting. If the server itself takes a long time to respond, nothing else will fully fix it. For customers in several countries, a content delivery network (CDN) serves files from closer to each visitor.

For a poor INP

• Cut third-party scripts. Chat widgets, several analytics tools, social feeds, pop-up tools and tracking pixels all compete for the phone's processor. Remove the ones you don't actively use.
• Trim plugins and page builders. Some themes load large amounts of JavaScript on every page, whether it is needed or not.
• Test on a real, ordinary phone. If menus and buttons feel sluggish on a budget Android handset, many of your customers feel it too.

For a high CLS

• Give images and videos set dimensions so the browser reserves space before they load.
• Reserve space for banners and ads, rather than letting them push content down when they appear.
• Load web fonts carefully. Fonts that swap in late can reflow text. A developer can set them up so the change is barely noticeable.

A simple step-by-step plan

1. Test your five most important pages and write down the three measurements for each.
2. Fix the images first: resize, compress and convert them. Re-test.
3. List every plugin, widget and script on the site. Remove anything you can't name a clear reason for. Re-test.
4. If LCP is still slow, ask your host about server response time and whether a CDN or caching is set up.
5. Recheck in Search Console after a few weeks. Real-user data updates slowly because it is collected over a rolling period.

When speed problems come from how the site was built

Sometimes the issue isn't one image or one plugin; it's the whole build. A heavy theme with a page builder, a dozen plugins and several tracking tools can be hard to make fast however much you tune it. In that case, rebuilding on a lighter setup is often cheaper in the long run than endless fixes. We build sites to pass Core Web Vitals from the start; you can read about our approach on the website design page.

Speed also helps beyond Google's rankings. AI search tools and assistants fetch pages to read them, and a clean, light page is easier for them to read too. Our guide to SEO for AI search covers that side.

Not sure where your site stands? Run our free website check for a quick read on speed and the other basics. If the results need more than a few image fixes, ToBrand can help you find and fix what's slowing it down.