The Real Cost of a Slow Website (2026): What Speed Does to Enquiries

Someone taps your link on their phone, watches a blank white screen, counts to three, and taps back to the search results — landing on a competitor whose page had already loaded. You never learn they came. That is the real cost of a slow website: not the slowness itself, but the enquiry that never arrives, and that you never get to miss. Speed is no longer a detail for the developers. In 2026 it is a sales channel, a Google ranking factor, and a condition for being surfaced by AI search at all.

Last updated: June 2026 · UK focus · Numbers measured live on Google PageSpeed Insights, which you can verify yourself

• Speed is a sales channel now, not a technical detail. A slow website does not cost you a slow website — it costs you the enquiry that never arrives, and you never see the loss.
• Google's own guidance is blunt and directional: as a page goes from one second to three to five, the probability of a bounce rises sharply. People decide fast.
• Check your own site in two minutes at pagespeed.web.dev — a free Performance score out of 100, mobile and desktop, plus the real load metrics.
• A good site scores in the 90s. Most page-builder sites score in the 30s to 50s on mobile. That gap is the difference between holding a visitor and losing one.
• Sites are slow for three fixable reasons: heavy page-builders, unoptimised images, third-party script bloat.
• Speed now decides AI visibility too, and our receipts are checkable: Ampliflow runs 94 mobile / 96 desktop, CLS 0, TBT around 40ms; a recent client build measured 96 / 97.

A slow website loses customers you never knew you had

The cost of a slow website is invisible, and that is exactly what makes it dangerous. There is no error message, no bounced email, no angry phone call. There is only a quietly lower number of enquiries than the business should be getting, with no obvious culprit.

The mechanism is human, not technical. A visitor taps your link expecting an answer; if the screen stays blank, they wait, and then they leave. Google's own published guidance has long held that the probability of a bounce rises sharply as load time stretches from one second to three to five. They do not email to say the site was slow — they open the next result, which belongs to a competitor.

A slow site does not lose the argument with the visitor — it loses them before the argument starts.

For a business where each customer is worth hundreds or thousands of pounds, this is not a rounding error. If your site loses even one in ten warm visitors before it renders, and you earn that traffic through ads, SEO or word of mouth, the slowness quietly taxes everything else you do to be found.

The traffic is not the problem. The leak is.

You can measure your own speed in two minutes, for free

Go to Google PageSpeed Insights, paste your URL and run it. It is free, it is Google's own tool, and it shows you exactly what your visitors experience. You do not need a developer to read the result.

PageSpeed returns a Performance score out of 100, separately for mobile and desktop. Check mobile first — most local traffic is on a phone, and mobile is the lower, more honest number. The score is colour-coded: green (90–100) is good, orange (50–89) needs work, red (0–49) is poor.

Below the score sit the metrics Google grades as Core Web Vitals — its own scoring system for real-world experience:

• LCP (Largest Contentful Paint) — how long until the main content appears. Google's "good" threshold is 2.5 seconds or less. This is the blank-screen number, the one that maps most directly to a visitor's patience.
• CLS (Cumulative Layout Shift) — how much the page jumps as it loads. Good is 0.1 or less; the ideal is 0, where nothing moves and nobody taps the wrong thing because a banner shoved the button down.
• INP / TBT (interactivity) — how fast the page responds to a tap. Google measures this in the field as INP; PageSpeed's lab test shows it as Total Blocking Time. Low means the page feels instant; high means it fights you.

Read the mobile Performance score first. Under 50, and visitors are leaving before your copy loads.

A good site scores in the 90s — most page-builder sites score in the 30s

A properly engineered site scores in the 90s on mobile. Most sites built on heavy page-builders score in the 30s to 50s. This is not a gap only an engineer notices. It is the difference between a site that holds the visitor and one that loses them.

We hold ourselves to the standard we sell. Ampliflow's own site measures 94 on mobile and 96 on desktop, with Core Web Vitals strong: CLS of 0, TBT around 40ms, desktop LCP of 1.2 seconds, and mobile LCP around 3.0 seconds — the one number we are still tightening, and we would rather name it than pretend it is perfect.

A recent client build, a local catering site, measured 96 on mobile and 97 on desktop. Every figure here is checkable: drop either URL into PageSpeed Insights yourself.

Most articles on slow websites quote a borrowed statistic and move on. We would rather hand you real receipts and the tool to check your own.

Slow sites are slow for three fixable reasons

Slow sites are rarely slow by accident. Three predictable, fixable causes explain almost all of them. Knowing which one is hurting you tells you whether a refresh will do, or whether the foundation needs replacing.

1. Heavy page-builders. Drag-and-drop platforms — many Wix, Squarespace and bloated WordPress theme-builder setups — buy their convenience with weight. They ship generic code to cover every possible layout, and the visitor downloads all of it whether the page uses it or not.
2. Unoptimised images. A photo straight off a phone or a stock library can weigh several megabytes. Put a few above the fold with no compression and no modern format, and the page cannot paint until they all arrive. Images are the most common single cause of a slow LCP.
3. Third-party script bloat. Chat widgets, popups, multiple analytics tags, social embeds, review carousels — each is more code from someone else's server, and each is a new point of delay. A well-built site is still dragged into the red by plugins nobody audited.

The common thread is weight. Speed is, in large part, the discipline of shipping less.

Fast is not a trade-off — our own site runs at 94 on mobile

A fast site is not a slow site with the speed turned up. It is built lean from the first line. The techniques are well established; the difference is that an engineering-led build applies them by default rather than bolting them on afterwards.

We use a modern production build process that puts performance first. Pages are served close to the visitor where possible, images are compressed and sized to the device, and code is kept lean so a visitor downloads only what the page needs.

None of this is exotic. It is what "built properly" means in 2026, and it is why a site carries rich design and motion and still scores in the 90s.

The idea that a site must be plain to be fast — or slow to be beautiful — is not a law of nature. It is a symptom of the wrong tools.

Slow pages get cited less by AI search — the newest cost

There is now a third reader judging your site at speed, beyond the human visitor and the Google crawler: the AI assistant. When someone asks ChatGPT, Gemini, Perplexity or Google's AI Overviews "who is a good [your trade] near me?", those systems crawl and render real pages to build an answer.

A page that is slow, heavy or hard to render is at a disadvantage. If a competitor's page answers the same question and loads cleanly and instantly, it is the easier source to read and quote. The logic mirrors classic SEO, but the stakes are higher: being left out of the answer is worse than ranking second.

Speed has quietly become part of being cited, not just being ranked — and a citation in an AI answer is becoming as valuable as a page-one position. We cover that shift in our guide to generative engine optimisation for UK businesses.

The same fast, lean page wins the human, the crawler and the AI at once. A slow one loses all three.

Frequently asked questions

How fast should a website load in 2026?

Aim for Google's Core Web Vitals "good" threshold: the main content of the page (Largest Contentful Paint) appears in 2.5 seconds or less, and the page feels usable almost immediately. On PageSpeed Insights, that translates to a Performance score in the 90s on mobile. Past three to four seconds to first meaningful content, you start losing visitors who decided to leave before the page was ready.

How do I check if my website is slow?

Go to Google PageSpeed Insights, paste your URL and run it — it is free and it is Google's own tool. Read the mobile Performance score first: under 50 (red) means visitors are likely leaving before the page loads, 50–89 (orange) means real work to do, 90+ (green) is good. The metrics below — LCP, CLS and TBT — tell you specifically what is slow.

Is a slow website really losing me customers?

Yes, and the loss is invisible, which is what makes it dangerous. A visitor who leaves because a page was slow does not complain — they close the tab and choose a competitor. Google's published guidance is that the probability of a bounce rises sharply as load time goes from one to three to five seconds. If you pay for traffic through ads or earn it through SEO, a slow site taxes every visitor you worked to attract.

What is a good PageSpeed score?

On PageSpeed Insights, 90–100 is good (green), 50–89 needs improvement (orange), and 0–49 is poor (red). Check mobile and desktop separately; mobile is usually lower and more representative of real traffic. A properly engineered site sits in the 90s on mobile — our own site measures 94 mobile / 96 desktop, and you can verify that yourself.

Why is my website so slow?

Almost always one of three causes: a heavy page-builder shipping more code than your page uses, large unoptimised images that delay the main content, or a stack of third-party scripts each adding delay. A PageSpeed report points to the dominant one. When the platform itself is the bottleneck, a rebuild costs less over time than repeatedly patching it.

Will making my website faster increase enquiries?

It removes a specific, measurable cause of lost enquiries: visitors who leave before the page loads. Speed alone is not a strategy — the page still needs a clear message, an obvious next step and real proof — but a fast site converts the visitors you already have at a higher rate, ranks better on Google, and is more likely to be surfaced in AI search. It compounds with everything else you do.

Does website speed affect SEO and AI search?

Both. Google has used page experience signals, including Core Web Vitals, as a ranking factor for years. AI search engines — ChatGPT, Gemini, Perplexity, Google AI Overviews — crawl and render real pages to build answers, so a slow page is surfaced and cited less. The same fast, lean page wins in classic search and AI search at the same time.

Related reading

• ↑ Small Business Website Design UK: The Honest 2026 Guide — the pillar guide to what a site should cost and do
• ↔ Website Redesign UK: Costs, Process & What You Actually Get — when a refresh fixes speed and when only a rebuild will
• ↔ Generative Engine Optimisation for UK Businesses — why speed now affects whether AI search surfaces you

Find out what your site is costing you

The fastest way to know whether your website is helping or quietly costing you is to measure it. Send us your URL and we will review the speed, mobile experience, trust signals and enquiry path, then tell you the first fix worth making.

Send us your URL for a free review →

You already suspect the answer. The two-minute version is one tab away — run your own site through PageSpeed, then send us the number you would rather not have seen.