Site speed and Core Web Vitals explained for non-developers

At some point, someone will run your website through a speed test, show you a red score and suggest it’s the reason you’re not ranking. Sometimes they’re right. Often they’re overstating it. Core Web Vitals are worth understanding before you act on that score.

Speed does matter, both for search and, more importantly, for whether visitors stay. But it’s one factor among many, and chasing a perfect score can waste money that would be better spent elsewhere.

Here’s what you need to know, without the jargon.

What Core Web Vitals are

Core Web Vitals are a set of measurements Google uses to judge how a page feels to use. At the time of writing there are three, though Google has changed the set before and may again:

• Largest Contentful Paint (LCP). How long it takes for the main content, usually the big image or heading at the top, to appear. Put simply: does the page look loaded quickly?
• Interaction to Next Paint (INP). How quickly the page responds when someone taps or clicks something. Does it feel sluggish?
• Cumulative Layout Shift (CLS). How much things jump around while loading. The classic example is going to tap a button and an advert loads above it, so you tap the wrong thing.

Google publishes thresholds for “good”, “needs improvement” and “poor” for each one. Search Console shows how your pages are doing in its Core Web Vitals report, based on data from real Chrome users where there’s enough of it.

How much does it affect rankings?

Google has said that page experience, including Core Web Vitals, is part of how it ranks pages, but it has also been clear that relevance and helpful content matter more. A fast page that doesn’t answer the search won’t beat a slightly slower page that does.

A sensible way to think about it:

• If your site is genuinely slow, especially on mobile, fixing that is worthwhile for rankings and for enquiries.
• If your site is already reasonably quick, squeezing out the last few points rarely moves rankings much. Your time is usually better spent on content, local SEO or links.

Speed is a tiebreaker for Google and a dealbreaker for visitors. Fix it for the people first, and you’ll usually satisfy the search engine too.

Lab scores versus real-world data

This is where much of the confusion comes from. Tools like PageSpeed Insights show two kinds of data:

• Field data comes from real visitors over recent weeks. It’s what Google uses for Core Web Vitals assessments. Smaller sites may not have enough traffic for this to appear.
• Lab data is a simulated test run there and then, usually on a throttled mobile connection. It’s useful for diagnosing problems, but the score can vary between runs.

So a lab score of 62 doesn’t necessarily mean your real visitors have a bad time, and a 98 doesn’t guarantee they have a good one. Look at field data first where it’s available.

The usual culprits on small business sites

In our experience, a handful of issues cause most speed problems on typical WordPress and page-builder sites:

1. Oversized images. A photo straight off a phone or camera can be many times bigger than it needs to be. Resizing and using modern formats like WebP is often the single biggest win.
2. Too many plugins and scripts. Every chat widget, slider, pop-up, tracking pixel and social feed adds weight. Many sites carry scripts for tools nobody uses any more.
3. Cheap or overloaded hosting. If the server is slow to respond, everything else waits. Budget shared hosting can be a false economy.
4. Heavy page builders and themes loading lots of code on every page, whether it’s needed or not.
5. Autoplaying video backgrounds and big sliders at the top of the page, which directly hurt LCP.
6. Web fonts loaded from several sources or in many weights.
7. Images and embeds without set dimensions, which cause layout shift as they load.

Fixing the problems

What you can do without a developer

• Resize images before uploading. For most website use, images rarely need to be wider than about 2,000 pixels, and often much less.
• Audit your plugins and third-party tools. If you can’t say what one does, find out, then remove it if it’s not needed.
• Question anything that autoplays at the top of the homepage.
• Ask your host what caching is in place, and whether you’re on a plan suitable for your traffic.
• Test your key pages, not just the homepage. Service pages are often slower and matter more.

When to get technical help

Some fixes, such as deferring scripts, improving how CSS loads or restructuring a heavy theme, need someone who knows what they’re doing, because it’s easy to break things. Ask for a clear list of what they’ll change, which pages they’ll test, and how they’ll measure before and after using both lab and field data.

Be wary of any plugin or service promising a perfect score in minutes. Some achieve it by hiding problems from the testing tool rather than fixing them for visitors.

Where to start

Check the Core Web Vitals report in Search Console, then run your three most important pages through PageSpeed Insights on mobile. If you’d like someone to interpret the results and fix the real issues, our technical SEO service covers it, and our website hosting is set up with speed in mind from the start.