Most businesses underestimate what a slow website costs them. It's invisible: there's no invoice for the customers who bounced before the page loaded. But the data is brutal — every extra second of load time drags down conversion, search ranking and brand trust simultaneously.
The numbers: what a one-second delay actually costs
Portent's research puts the conversion rate of a page loading in one second at 39% — by five seconds, it's 22%. That's not a rounding error; it's nearly half your potential customers gone before they decide. For a business generating £200k in annual revenue from their website, a two-second speed improvement could recover tens of thousands in sales that were silently leaking away.
What Google actually measures: Core Web Vitals explained
Google uses three specific signals as ranking factors. Largest Contentful Paint (LCP) measures when the main content appears — good is under 2.5 seconds. Cumulative Layout Shift (CLS) measures whether elements jump around while loading — good is under 0.1. Interaction to Next Paint (INP) measures how quickly the page responds to clicks and taps — good is under 200 milliseconds. Check your scores for free at PageSpeed Insights. Most small business sites built on WordPress with lots of plugins fail at least two of these.
The compounding cost
Search engines treat speed as a ranking signal, so a slow site is harder to find. Once found, slow pages convert worse — visitors abandon carts and contact forms before they submit. And the people who do stay quietly downgrade their impression of your brand. Slow reads as careless, even when your product is excellent. Each of these effects compounds the others: lower rankings mean less traffic, lower conversion means less revenue from the traffic you have.
The hidden costs beyond conversion
Slow sites cost you in ways that won't appear in your analytics. Every second of load time increases bounce rate — Google records this as a signal that your page wasn't useful, which feeds back into lower rankings over time. Slower pages get crawled less frequently, meaning new content takes longer to get indexed. On mobile (which is now the majority of web traffic), a slow page doesn't just annoy users — it can actively exhaust their data on metered connections, making your site hostile to a significant portion of your audience.
Why most slow websites stay slow
The most common reason slow sites don't get fixed is that the speed problems are architectural, not cosmetic. Page builders like Elementor or Divi generate bloated HTML and load enormous CSS and JavaScript bundles that can't be optimised away after the fact. No caching plugin can fully compensate for a fundamentally overweight codebase. Understanding whether you're dealing with a fixable performance issue or a structural one determines whether you should patch or rebuild.
The fixes that actually matter
Most speed problems come down to a handful of culprits: oversized images, render-blocking scripts, bloated page builders and no performance budget. The high-impact fixes are: compressing every image to WebP format and lazy-loading below-the-fold images; deferring or removing third-party scripts like chat widgets and marketing pixels; and choosing a host that includes a CDN. A good web design and development team treats performance as a design constraint from day one, not an afterthought.
Quick wins you can do today
Run your key pages through PageSpeed Insights and note your LCP, CLS and INP scores. Install a caching plugin if you're on WordPress (WP Super Cache is free and effective). Run all your images through an online compression tool like Squoosh. Remove any plugins or scripts you don't actively use — one removed plugin can recover more speed than ten optimisation settings. Check whether your hosting plan includes a CDN — edge delivery is one of the fastest single improvements available.
When patching isn't enough: the case for a rebuild
Some websites can't be made genuinely fast with patches. If your site is built on a heavy page builder, the performance ceiling of that setup is too low to rank competitively against leaner sites. A clean rebuild — a lean framework, hand-coded or headless front-end with a performance budget enforced from the start — often recovers the rebuild cost in six to twelve months through better conversion rates and lower paid acquisition costs needed to compensate for poor organic rankings.
Build it fast from day one
The cheapest way to have a fast website is to build it fast from the start — clean front-end code, optimised media, and performance budgets baked in — rather than attempting fixes later. If your current site feels sluggish, a focused rebuild often pays for itself in recovered conversions within months. The question to ask any studio you commission: what is your performance budget, and how do you enforce it?
Benchmarking: how to know if you've improved
Before making changes, capture your baseline. Run your key pages through PageSpeed Insights three times and average the scores. Also check Core Web Vitals in Google Search Console under the Experience tab — this shows real-world data from actual visitors, which is more meaningful than the lab test. After making changes, wait two to four weeks for sufficient real-world data before judging impact. Track LCP as your primary north-star metric: it has the highest correlation with conversion rate improvements.