Why website speed affects enquiries (and how to fix it)
Speed feels like a technical detail. It isn't — it's a business metric. A slow website loses visitors before they ever see your offer, drags down your Google ranking, and quietly costs you enquiries you never knew you missed. The good news: it's usually one of the cheapest, highest-return things you can fix.
Speed is a business metric, not a vanity one
Visitors decide whether to stay within the first couple of seconds. Industry research consistently finds that conversions drop by roughly 7% for every extra second of load time, and a large share of mobile visitors leave a page that takes more than three seconds. Every one of those is a customer who never reached your contact form.
Google has also confirmed that speed and Core Web Vitals are ranking factors. So a slow site loses twice: fewer people find you, and more of the ones who do give up before they convert.
What "fast" actually means
Google measures real-world experience with three Core Web Vitals. You don't need to be an engineer to understand them:
- LCP (Largest Contentful Paint) — how quickly the main content appears. Aim for under 2.5 seconds.
- INP (Interaction to Next Paint) — how fast the page responds when you tap or click. Aim for under 200 milliseconds.
- CLS (Cumulative Layout Shift) — how much the page jumps around as it loads. Aim for under 0.1.
Why your site is probably slow
- Huge images — photos uploaded straight from a phone or camera, unoptimised.
- Plugin and script bloat — every add-on and tracker loads more code.
- Cheap or distant hosting — the server takes too long to respond.
- No caching or CDN — every visitor rebuilds the page from scratch.
- Render-blocking code — fonts and scripts that hold up the first paint.
How to fix it
- Compress and serve images in modern formats (WebP/AVIF), sized for the device.
- Strip out unused plugins, scripts and tracking you don't need.
- Add browser and server caching, and a CDN to serve content from nearby.
- Defer non-critical scripts so the page shows content first.
- Fix the biggest offender first — performance work follows the 80/20 rule.
How to measure it yourself
Run your site through Google PageSpeed Insights (free). A score below 90, or any Core Web Vital flagged in the red, means there's work to do. It'll even list the biggest opportunities — though knowing *why* each one is happening, and which to tackle first, is where a developer earns their keep.
Common questions
Does website speed really affect Google rankings?
Yes. Google has confirmed that page speed and Core Web Vitals are ranking signals. They're not the only factor — relevant content still matters most — but between two similar sites, the faster one has the edge, and faster sites convert better regardless of ranking.
How fast should my website be?
Aim for the main content to appear in under 2.5 seconds, interactions to respond in under 200 milliseconds, and minimal layout shift. In Lighthouse terms, 90+ for Performance is a sensible baseline — it's the standard we build every site to.
Can you speed up my site without rebuilding it?
Usually, yes. If the foundation is sound, a focused optimisation pass — images, caching, code cleanup, removing bloat — often delivers a big improvement for a fraction of a rebuild. If the foundation is broken, we'll be honest that rebuilding is the better spend.
Why is my WordPress site so slow?
Almost always plugin bloat, unoptimised images and shared hosting. WordPress itself can be fast — it's usually the accumulation of add-ons and heavy themes that drags it down. Those are exactly the things a speed audit identifies and fixes.
Let's talk
Let's talk about your project.
Whether you've got a clear brief or just an idea, tell us what you have in mind and we'll give you an honest recommendation — even if that's a smaller project than you expected.