
Is Your Website Fast Enough? Core Web Vitals Explained
If you run a small business, you have probably wondered whether your website is fast enough. You do not need to be technical to find out. Google publishes clear targets for page experience, called Core Web Vitals, and a short list of fixes covers many of the common causes of a slow page.
This article explains the three targets in plain English, shows how Google decides whether a page passes, and gives you the first three fixes to check.
What are Core Web Vitals?
Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor. Google's targets are:
- Loading (LCP, Largest Contentful Paint): the main content of the page, often a large image or heading, should appear within 2.5 seconds of when the page first starts loading.
- Interactivity (INP, Interaction to Next Paint): the page should respond to taps and clicks in 200 milliseconds or less.
- Visual stability (CLS, Cumulative Layout Shift): the page should not jump around as it loads. The target is 0.1 or less.
In simple terms: the page should show up quickly, react quickly and stay still while people read it.
How does a page pass?
A page passes Core Web Vitals when it meets all three targets at the 75th percentile of page loads, measured across mobile and desktop. In other words, it is not enough for the page to be fast for some visitors. At least three out of every four visits need to meet the targets. That is why a site that feels fine on your office computer can still fail: your visitors may be on slower phones and weaker connections.
Why speed matters to your sales
Speed is a business matter as well as a technical one. One well-known example comes from Vodafone, which ran an A/B test on its website. Google's write-up of the test reports that a 31% improvement in LCP led to 8% more sales.
Be careful with that figure. It is one company's test, not a promise. A small business with a different site, audience and product may see a different result, or none. What the example does show is that loading speed can be tested against real sales, rather than treated as a purely technical score.
Fix 1: do not lazy-load your main image
Lazy loading tells the browser to wait before loading an image, which is useful for pictures far down the page. Google's guidance on optimising LCP is blunt about the main image at the top: never lazy-load it, because that always leads to unnecessary delay before the image starts to load.
What to check:
- Is the large image at the top of your page set to lazy-load? If so, turn that off for this one image.
- Is the image present in the page's initial HTML, so the browser can find it straight away, rather than being added later by a script?
- Has the image been given high fetch priority, so the browser loads it before less important files?
Many website builders and WordPress plugins apply lazy loading to every image automatically, so this is worth checking even if you never chose it.
Fix 2: cut out redirects
If your server seems slow to respond, the cause may not be the server at all. Google notes that a common cause of a slow response on an otherwise fast site is visitors arriving through multiple redirects.
A redirect sends a visitor from one address to another before the page loads. Each hop adds waiting time. You might have a chain such as the http version of your address, then the https version, then the version with "www", then a final page. Check the links you control, such as your Google Business Profile, social media bio, email signature and adverts. They should point straight to the final address, not to an old one that bounces visitors onward.
Fix 3: shrink the image, use a CDN and cache
The third fix has three parts, all aimed at the time it takes to download your main image and other files:
- Make the main image smaller. A large photograph straight from a camera or phone is far bigger than a web page needs. Resize and compress it before uploading.
- Serve it from a CDN. A content delivery network keeps copies of your files on servers in many places, so visitors receive them from one nearby.
- Use caching. Google describes caching as the best way to cut resource load time. A returning visitor's browser can reuse files it already has instead of downloading them again.
While you are looking, ask your developer or website provider about scripts. Google advises that it is almost never necessary to add synchronous scripts, because they can block the page from being drawn. Remove any you do not need, such as old tracking tools or widgets nobody uses.
How to start
- 1Pick the page that matters most, usually your home page or main service page.
- 2Run it through a free speed testing tool and note whether it meets the three targets above.
- 3Work through the three fixes in order, changing one thing at a time so you can see what made the difference.
- 4Test again, and keep checking from a mobile phone, since that is where many sites struggle.
Results vary from site to site, and no speed improvement can promise more customers. But removing needless delays is rarely wasted effort, and these three checks are a sensible place to begin.
If you would like help reviewing your site's speed, get in touch and we can talk through what to look at first.
Continue Reading
Discover more insights and stories


