Most slow websites don't feel slow to the person who runs them. You're on fast office broadband, your browser has the site cached, and pages snap into view. Meanwhile a prospective customer on a three-year-old phone with patchy mobile signal waits four seconds, gives up, and goes to a competitor. You never even see it happen.
Speed isn't a vanity metric. It directly affects how many visitors stay, how many convert, and where Google ranks you. Since Google made Core Web Vitals a ranking factor, a sluggish site is a double penalty: fewer visitors find you, and more of those who do leave early.
What Core Web Vitals actually measure
Google distilled 'fast and pleasant to use' into three measurable things:
- Largest Contentful Paint (LCP) — how long until the main content appears. Target: under 2.5 seconds.
- Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. Target: under 200 milliseconds.
- Cumulative Layout Shift (CLS) — how much the page jumps around as it loads. Target: under 0.1.
You can check your own scores free in Google PageSpeed Insights or the Core Web Vitals report in Search Console, which shows real-world data from actual visitors.
What usually slows sites down
In our experience, the same handful of culprits account for most slow UK small-business sites:
Oversized images
A 4MB photo straight off a phone camera is the most common offender. Images should be sized to their display dimensions, compressed, and served in modern formats like WebP. This alone often halves load time.
Too much code loading too early
Heavy themes, a dozen plugins, chat widgets, multiple tracking scripts and big font libraries all pile up. Each one is another file the browser must fetch before the page is usable.
Slow hosting
If the server itself is slow to respond, nothing downstream can fix it. Cheap shared hosting stuffed with hundreds of sites is a frequent cause of poor server response times.
No caching or CDN
Without caching, the server rebuilds every page from scratch on each visit. A content delivery network stores copies closer to your visitors so pages arrive faster, especially for users far from your server.
The highest-impact fixes, in order
| Fix | Effort | Typical impact |
|---|---|---|
| Compress and resize images | Low | High |
| Enable caching | Low | High |
| Remove unused plugins/scripts | Low-medium | Medium-high |
| Add a CDN | Medium | Medium-high |
| Upgrade hosting | Medium | High if server is the bottleneck |
| Optimise code / lazy-load | High | Medium |
Fixing layout shift and responsiveness
Speed isn't only about loading. Layout shift — when a button moves just as you go to tap it because an ad or image loaded late — frustrates users and hurts your CLS score. The fix is to reserve space for images, ads and embeds so nothing jumps. Responsiveness (INP) usually improves when you reduce heavy JavaScript that blocks the browser from reacting to taps.
Speed work compounds with everything else: a faster site converts more of the traffic your SEO efforts bring in, so the investment pays back twice.
When to bring in a developer
You can handle image compression, caching plugins and removing obvious bloat yourself. But render-blocking resources, server tuning, code splitting and database optimisation need someone who knows what they're doing — and a clumsy attempt can break the site. If your scores are still poor after the easy wins, that's the moment to get expert help.
Performance specialists can usually deliver a dramatic improvement in a fixed, affordable engagement. Browse experienced web development agencies in our directory, share your PageSpeed results, and ask for a before-and-after estimate before you commit.