Website speed optimisation.

A slow website is the most expensive problem most businesses don't know they have. It costs you rankings, it costs you customers who leave before the page loads, and it costs you the sales those customers would have made — silently, every single day.

The short answer

Website speed optimisation means reducing how long a page takes to become usable, then keeping it fast as the site grows. The biggest wins for most sites are: compressing and correctly sizing images, removing unnecessary JavaScript, optimising fonts, enabling browser caching and compression, using a CDN, and hosting on decent infrastructure. Speed is measured by Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift — which are confirmed Google ranking factors. It matters commercially because conversion rates fall measurably with every extra second of load time, and because AI crawlers now budget how much of your site they'll read based partly on how fast it responds.

Why speed is a business problem, not a technical one

Speed gets filed under "technical" and ignored by the people it affects most — the owners losing money to it. Here's the chain in plain terms: a visitor arrives, the page is slow, a proportion leave before it loads, and every one of those was a potential customer. The slower the site, the bigger that proportion. Google has published research for years showing bounce probability climbing sharply as load time grows; the exact numbers vary, but the direction never does.

There are three compounding costs. Lost visitors who leave before the page appears. Lower rankings, because Google uses speed signals to rank pages, so a slow site gets less traffic to lose visitors from in the first place. And lower conversion among the visitors who do stay, because a sluggish, janky experience erodes trust before you've said a word. In our audit of 421 local business websites, slow, heavy sites were the norm rather than the exception — which means for most local businesses, being genuinely fast is a competitive advantage sitting unclaimed.

What actually makes a website slow

Nearly all slowness comes from a short list of causes, and knowing which one you have tells you what to fix:

CauseHow commonTypical fix
Large, unoptimised imagesExtremely commonCompress, resize, modern formats, lazy-load
Too much JavaScriptVery common (esp. builders/plugins)Remove, defer, or replace heavy scripts
Render-blocking resourcesCommonDefer non-critical CSS/JS; inline critical CSS
Web fonts loaded badlyCommonSubset, preload, use font-display: swap
No caching or compressionCommonEnable browser caching + Gzip/Brotli
Slow hostingCommon on cheap shared plansBetter host, or a CDN in front
Bloated themes/page buildersVery common on WordPressLean theme or hand-coded build
Third-party scripts (chat, analytics, ads)CommonAudit, remove, or load asynchronously

The pattern: most slow sites aren't slow because of one dramatic problem, but because of a dozen small ones stacked up — a heavy theme, a few oversized images, five plugins each adding scripts, a chat widget, three tracking tags. Speed work is usually subtraction.

Images: the single biggest lever

For most sites, images are the largest chunk of page weight and the fastest win. Three things to get right:

Size them correctly. A photo displayed at 400 pixels wide should not be a 3,000-pixel file scaled down in the browser — the visitor still downloads the whole thing. Export images at the size they're shown, and serve smaller versions to phones.

Compress them. Most images can lose 50–80% of their file size with no visible quality loss. Modern formats — WebP and AVIF — do this far better than old JPEGs and PNGs, and every current browser supports them.

Lazy-load below-the-fold images so the browser only fetches them as the visitor scrolls near, rather than all at once on load. This is a simple attribute (loading="lazy") that most modern sites should use by default.

Quick check: right-click any image on your site, and if the downloaded file is measured in megabytes rather than kilobytes, that single image is probably costing you visitors on mobile data.

JavaScript, fonts and the rest of the diet

JavaScript

JavaScript is the heaviest thing on many modern sites because it must be downloaded, parsed and executed before the page becomes interactive. The fixes, in order of impact: remove scripts you don't need (that abandoned chat widget, the second analytics tag); defer scripts that aren't needed immediately so they don't block the initial render; and be sceptical of any feature that pulls in a large library to do something small. Page builders and plugin-heavy sites are the usual offenders — every plugin tends to add its own scripts whether the page uses them or not.

Fonts

Custom fonts make sites feel designed, but loaded carelessly they cause invisible text and layout jumps. Do three things: subset fonts to the characters you use, preload the critical font file, and set font-display: swap so text shows immediately in a fallback while the custom font loads. Self-hosting fonts (rather than loading from a third party) also removes a network round-trip and a privacy concern.

Caching, compression and clean code

Browser caching tells returning visitors' browsers to reuse files they already have rather than re-downloading them. Compression (Gzip or the newer Brotli) shrinks files in transit — typically 70%+ on text-based files, for a one-time server setting. And clean, lean code underpins all of it: a hand-built page carrying only what it needs will always beat a heavy template doing the same job, because there's simply less to download and run.

Hosting, CDNs and where your site lives

You can optimise everything on the page and still be held back by where it's served from. Two levers:

Hosting quality. The cheapest shared hosting crowds thousands of sites onto one server; when a neighbour gets busy, you slow down. Decent hosting — even still affordable — gives you consistent response times. For UK businesses, a server in or near the UK reduces the physical latency of every request. Our hosting guide covers the trade-offs in full.

A CDN (Content Delivery Network) stores copies of your site's static files on servers around the world and serves each visitor from the nearest one. It cuts latency, absorbs traffic spikes and adds a layer of security. For a local business it's often optional; for anyone with a national or international audience it's close to essential, and services like Cloudflare offer a capable free tier.

Core Web Vitals: how speed is actually measured

Google measures real-world experience through three Core Web Vitals, and they're confirmed ranking factors. Briefly:

MetricMeasuresGoodCommon cause when poor
LCP (Largest Contentful Paint)How fast the main content appears≤ 2.5sSlow server, huge hero image, render-blocking resources
INP (Interaction to Next Paint)How fast the page responds to taps/clicks≤ 200msHeavy JavaScript blocking the main thread
CLS (Cumulative Layout Shift)How much the layout jumps around≤ 0.1Images/ads without dimensions, late-loading fonts

INP replaced the older FID metric in 2024 and is stricter — it measures responsiveness across the whole visit, not just the first interaction. The full mechanics, and how to diagnose each one, are in our dedicated Core Web Vitals guide. Measure yours free with Google's PageSpeed Insights.

Performance budgets and continuous optimisation

Speed isn't a one-time fix — sites get slower over time as content, images, plugins and tracking accumulate. Two habits keep it under control.

A performance budget sets a ceiling: a maximum page weight, a maximum number of requests, a target load time. Anything that would breach the budget has to earn its place or be optimised first. It turns speed from an afterthought into a constraint that shapes decisions — the same discipline that stops a house-move turning into a hoard.

Continuous monitoring catches regressions before your customers do. Check Core Web Vitals in Search Console monthly, re-test key pages after any significant change, and treat a sudden speed drop as the warning it is. Our free website checker gives a fast plain-English read whenever you want one.

AI crawler efficiency and crawl budget

Here's a 2026 dimension most speed guides miss. Search engines and AI systems allocate a crawl budget — a finite amount of time and resource they'll spend fetching your pages. A slow server means each page costs more to fetch, so fewer of your pages get crawled and indexed in a given window. For large sites especially, speed directly affects how much of your content ever makes it into Google's index or an AI system's knowledge.

The AI-search angle sharpens this: assistants like ChatGPT, Gemini and Perplexity fetch pages to answer questions, often under tight time limits. A page that responds slowly may simply be skipped in favour of a faster competitor's. Being fast isn't only about the human visitor any more — it's about being reachable by the machines that increasingly decide who gets cited. The broader picture is in our guide to SEO in the AI era.

Frequently asked questions

Why is my website so slow?

Almost always a stack of small issues rather than one big one: oversized images, too much JavaScript, no caching or compression, web fonts loaded badly, a heavy theme or page builder, and slow hosting. Run PageSpeed Insights or our free checker to see which apply to your site.

How fast should a website load?

Aim for the main content to appear within 2.5 seconds (Google's 'good' threshold for Largest Contentful Paint) and for the page to respond to taps within 200 milliseconds. Faster is always better, particularly on mobile connections.

Does website speed affect Google rankings?

Yes. Core Web Vitals — which measure loading, responsiveness and visual stability — are confirmed Google ranking factors. Speed also affects rankings indirectly by influencing how much of your site gets crawled and how long visitors stay.

What is the biggest cause of slow websites?

For most sites, unoptimised images are the single largest contributor to page weight, followed closely by excessive JavaScript from themes, page builders and plugins. Both are usually fixable without rebuilding the site.

How do I make my images load faster?

Size them to the dimensions they're displayed at, compress them (most images can shrink 50–80% with no visible loss), use modern formats like WebP or AVIF, and lazy-load images below the fold so they only download as the visitor scrolls.

What are Core Web Vitals?

Three metrics Google uses to measure real-world page experience: Largest Contentful Paint (how fast the main content appears), Interaction to Next Paint (how quickly the page responds to input), and Cumulative Layout Shift (how much the layout jumps). All three are ranking factors.

Will a CDN make my website faster?

Usually yes, especially if your visitors are geographically spread or your hosting is slow. A CDN serves your static files from a server near each visitor, cutting latency and handling traffic spikes. For a purely local business it's often optional but still helpful.

Does hosting affect website speed?

Significantly. Cheap shared hosting packs many sites onto one server, so you slow down when neighbours get busy. Better hosting gives consistent response times, and UK-based hosting reduces latency for UK visitors. Hosting is often the invisible ceiling on an otherwise well-optimised site.

Is WordPress slow?

WordPress isn't inherently slow, but it's commonly made slow by heavy themes, page builders and too many plugins, each adding scripts and requests. Built properly — a lean custom theme, minimal plugins, good hosting and caching — it can be perfectly fast. Our WordPress guide covers doing it right.

What is a performance budget?

A self-imposed ceiling on page weight, number of requests and load time. Anything that would push a page over budget must be optimised or justified first. It stops sites getting gradually slower as content and features accumulate over time.

How does website speed affect conversions?

Directly and measurably: conversion rates fall as load time rises, because slow pages lose visitors before they act and erode trust among those who stay. Speed improvements are one of the few changes that can lift both traffic and conversion at once.

How can I test my website speed for free?

Google's PageSpeed Insights gives a detailed Core Web Vitals report and specific recommendations. Google Search Console shows real-world Core Web Vitals across your whole site. Our free website checker gives a fast, plain-English summary including speed signals.

Related: Core Web Vitals explained · Hosting guide · Technical SEO · Free health checker

Free tool: Work out how much page weight you can afford with the performance budget calculator — set a target load time and connection speed, and see your budget for images, scripts and fonts.

Key takeaways

  • Slow sites cost money three ways: lost visitors, lower rankings, and reduced conversion among those who stay.
  • Most slowness is a stack of small issues — images, JavaScript, fonts, caching, hosting — so speed work is usually subtraction.
  • Images are the biggest lever: size correctly, compress, use WebP/AVIF, lazy-load.
  • Core Web Vitals (LCP, INP, CLS) are confirmed Google ranking factors — measure them free in PageSpeed Insights.
  • Hosting quality is the invisible ceiling on an otherwise fast site; a CDN helps spread-out audiences.
  • Set a performance budget and monitor monthly — sites drift slower as content and plugins accumulate.
  • In 2026, speed also affects crawl budget and whether AI assistants can fetch and cite your pages in time.

Is your site costing you customers before it even loads?

Send me your address and I'll run a proper speed and Core Web Vitals check, then tell you honestly what's slowing it down and what's worth fixing. Every site I build is fast by design — hand-coded, lean, no plugin bloat.

Chat on WhatsApp