Does Website Speed Affect SEO? What Actually Matters

On this page

1. Does website speed affect SEO?
2. What are Core Web Vitals?
3. How to check your website speed
4. What slows a small business website down?
5. Case study: how we got our own site showing its first content 3× faster
6. Quick wins you can make today
7. When it’s time to rebuild instead
8. Frequently asked questions

If you’ve ever run your website through a speed test and felt your heart sink, you’re not alone. Slow websites are one of the most common problems we find when we review small business sites. So, does website speed affect SEO? Yes, but it’s only part of the picture, and fixing it properly is as much about the people visiting your site as it is about pleasing Google.

In this guide we’ll explain what Google actually measures, how much speed matters for rankings, what usually slows a website down, and the exact changes we made to our own site.

Does website speed affect SEO?

Yes. Google uses page experience signals, including a set of speed and stability measurements called Core Web Vitals, as part of how it ranks pages. Google’s own Core Web Vitals documentation says that achieving good scores “aligns with what our core ranking systems seek to reward”.

But speed isn’t a magic switch. Google ranks the most relevant, helpful page for each search, so a fast page with thin content won’t beat a slightly slower page that answers the question properly. Think of speed as a tiebreaker and a multiplier: when two pages are equally useful, the better experience tends to win, and a fast site makes every visitor more likely to stay.

Where speed really pays off is after the click. Slow pages lose people before they’ve seen what you offer, especially on mobile data. That means fewer enquiries and fewer sales from the traffic you already have.

What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to judge the real-world experience of a page. Google recommends aiming for:

• Largest Contentful Paint (LCP) within 2.5 seconds. How long it takes for the main content, usually the hero image or headline, to appear.
• Interaction to Next Paint (INP) under 200 milliseconds. How quickly the page responds when someone taps a button or opens a menu.
• Cumulative Layout Shift (CLS) under 0.1. How much the page jumps around as it loads, like a button moving just as you go to tap it.

Google measures these from real visitors using Chrome, so your scores reflect how your site performs for actual customers on actual phones, not just in a lab test.

How to check your website speed

You don’t need special software. Three free tools from Google will tell you most of what you need:

1. PageSpeed Insights. Enter your web address to see real-user Core Web Vitals (if your site has enough visitors) plus a lab test with a list of suggested fixes.
2. Google Search Console. The Core Web Vitals report groups your pages into good, needs improvement and poor, using real visitor data.
3. Lighthouse, built into Chrome’s developer tools. Useful for testing changes before they go live.

Always check the mobile result first. Most local searches, like “electrician in Burnley”, “dentist in Blackburn” or “café near me”, happen on phones, and Google mainly uses the mobile version of your site when it indexes your pages.

What slows a small business website down?

In our experience, a handful of issues cause most of the problems:

• Oversized images. A photo straight off a phone can be several megabytes. Resized to the size it actually appears on screen, it could often be a fraction of that.
• Too many plugins and scripts. Every chat widget, slider, tracking script and pop-up adds weight and work for the browser, and template sites tend to pile them up.
• Fonts loaded from other servers. If the page waits for a font to download from a third party before showing text, visitors stare at a blank space.
• Heavy page builders. Some drag-and-drop builders add a lot of code to every page, whether it’s needed or not.
• Slow hosting. If the server takes a long time to respond, everything else waits.
• Animations that block the page. Eye-catching effects are fine, as long as they don’t stop the important content appearing first.

Case study: how we got our own site showing its first content 3× faster

We practise what we preach, so we ran Google Lighthouse on ggscaled.com, found what was slowing it down and fixed it. Here are the real before-and-after figures:

The three changes that made the biggest difference:

1. We stopped building the logo into the page code. Our logo was embedded in the HTML twice as text-encoded image data, so every visit downloaded it as part of the page. We replaced it with one small image file (211 KB down to 12 KB) that browsers download once and remember.
2. We hosted our font ourselves. The page was waiting on Google’s font server before it showed any text. Now the font loads from our own site and the browser is told to fetch it first, so text appears straight away.
3. We made our 3D animation wait its turn. Our homepage has an animated 3D knot. It was loading before the headline and keeping phones busy. Now the words load first, and the animation fades in a moment later.

None of these changed how the site looks. They changed the order and weight of what loads.

Quick wins you can make today

If you manage your own website, start here:

• Resize and compress images before uploading them. Images shouldn’t be much bigger than the size they’re displayed at, and modern formats like WebP are usually much lighter.
• Remove plugins and apps you don’t use. If you can’t remember why something’s there, test the site without it.
• Limit pop-ups and third-party widgets, especially on mobile.
• Check your hosting. If PageSpeed Insights flags a slow server response, cheap hosting may be costing you more than it saves.
• Re-test after every change, so you know what actually helped.

When it’s time to rebuild instead

Sometimes the honest answer is that a site can’t be made fast without starting again. If your website runs on a heavy template or page builder, has years of plugins layered on top, or fails Core Web Vitals on every page, a rebuild can be quicker and cheaper than patching. A bespoke website can be built to load only what each page needs.

If your site is too slow to fix and you’re thinking about a rebuild, take a look at our web design service.

Frequently asked questions