Guide · Performance

Why website speed matters more than you think

Speed is one of the few things on your website that affects rankings and sales at the same time — and most small-business sites are quietly losing both to it. Here's what slow really costs, what 'fast' means in 2026, and how to fix it.

By Elliot · Last updated 19 June 2026 · 6 min read

The cost

What a slow website actually costs you

Six ways a slow site quietly drains rankings, customers and money.

Lower Google rankings

Google uses page experience, including Core Web Vitals, as a ranking signal. Two sites with similar content won't rank equally if one is fast and one is slow — and in competitive local search, that gap decides positions.

Lost visitors and sales

People abandon slow pages. Every extra second of load time pushes more visitors to the back button before they've seen what you offer. On a lead-gen site, that's enquiries walking away; on a shop, it's sales.

A worse deal on mobile

Most local searches happen on a phone, often on a patchy connection and weaker hardware. A heavy page that's tolerable on a desktop can be painful on mobile — exactly where most of your customers are.

More expensive ads

If you run Google Ads, a slow landing page drags down your Quality Score and your Ad Rank, so you pay more per click for the same position. Speed quietly inflates your ad bill.

A weaker first impression

Speed is the first thing a visitor experiences, before they read a word. A page that loads instantly feels professional and trustworthy; one that hangs makes a business feel amateur, fairly or not.

Compounding SEO drag

Slow sites get crawled less efficiently and frustrate users, which feeds back into rankings over time. Speed isn't a one-off fix — it's a foundation that every other SEO effort sits on top of.

The standard

What “fast” actually means in 2026

“Fast” isn't a feeling — Google measures it with three numbers called Core Web Vitals. Largest Contentful Paint (LCP) is how quickly your main content appears; the target is under 2.5 seconds. Interaction to Next Paint (INP) is how fast the page responds when someone taps or clicks; the target is under 200 milliseconds. Cumulative Layout Shift (CLS) is how much the page jumps around as it loads; the target is under 0.1. Hit all three on mobile and you have a genuinely fast site by Google's own definition.

The crucial word is mobile. Most local searches happen on a phone, often on a weaker connection, and that's where pages are hardest to keep fast. A site that scores well on a desktop and poorly on mobile is, for ranking and conversion purposes, a slow site. You can check your own scores free with Google PageSpeed Insights, or run your URL through our website checker.

The causes

What actually makes a website slow

Six usual suspects — most sites are guilty of several at once.

Heavy, unoptimised images

The single most common cause. Uploading full-resolution photos straight from a phone or camera forces every visitor to download megabytes they don't need. Correct formats, sizing and compression usually deliver the biggest single win.

Too many third-party scripts

Chat widgets, analytics, pixels, review embeds, fonts and tag managers each add weight and block rendering. Five 'small' add-ons together can dominate your load time.

Page builders and plugin bloat

Builders like Elementor, Divi and WPBakery — and stacks of WordPress plugins — generate bloated HTML and load code for features you don't use. It's convenience paid for in performance.

No caching or CDN

Without proper caching and a content delivery network, every visit hits your server from scratch and is served from one location, however far away the visitor is. Both make pages slower than they need to be.

Render-blocking code

CSS and JavaScript that load before the page can display delay the moment a visitor sees anything. Deferring and splitting that code is a core part of building for speed.

Cheap or overloaded hosting

Budget shared hosting puts your site on a crowded server with hundreds of others. Modern edge hosting serves pages from close to the visitor, fast, every time.

FAQ

Common questions

Does website speed actually affect Google rankings?

Yes. Google uses page experience signals, including Core Web Vitals, as part of how it ranks pages. Speed isn't the only factor — content and relevance still matter most — but between two otherwise comparable pages, the faster one tends to win, and in competitive local markets that's often the deciding margin.

What is a good website speed score?

Google's 'good' thresholds for Core Web Vitals are a Largest Contentful Paint under 2.5 seconds, an Interaction to Next Paint under 200 milliseconds, and a Cumulative Layout Shift under 0.1 — measured on mobile, where it's hardest. As a rough proxy, aim to land in the green (90+) on Google PageSpeed Insights for mobile.

What are Core Web Vitals in plain English?

They're three measures of how a page feels to use. Largest Contentful Paint (LCP) is how long until the main content appears — loading speed. Interaction to Next Paint (INP) is how quickly the page responds when you tap or click — responsiveness. Cumulative Layout Shift (CLS) is how much things jump around as the page loads — visual stability. Good scores on all three mean a page that loads fast, reacts instantly and doesn't move under your thumb.

Why is my WordPress or Squarespace site slow?

Usually a combination of heavy images, a page builder or plugin stack generating bloated code, and third-party scripts. Some of it is fixable with optimisation; some is baked into how the platform works. Where a site is fundamentally slow because of how it's built, a rebuild on a fast modern stack is often better value than endlessly patching it.

How fast can a website realistically be?

A properly built site — hand-coded, image-optimised, served from a CDN — should paint its main content in well under a second and score in the green on Core Web Vitals on mobile. That's the standard we build to in Next.js; it's not a stretch goal, it's the default.

References

Sources & further reading

The guidance on this page is grounded in primary sources. Follow the links to read them in full.

Find out how fast your site really is

Send us your URL and we'll run a Core Web Vitals audit — and tell you honestly what's slowing it down and what it would take to fix.