Everyone agrees that websites should be fast. Then a new feature gets added, a few large photos get uploaded, another plugin goes in, a chat widget, a cookie banner, a tracking script, and slowly the site gets heavier.
Nobody notices, because the people who work on the site visit it on fast office Wi-Fi with everything already cached. Your customers aren’t so lucky. They’re on a phone, on a train, with one bar of signal.
Why speed matters
People leave. A visitor who waits too long for a page often doesn’t wait at all. They hit back and choose the next result. You never see them, so you never know what you lost.
First impressions stick. A slow, jumpy page feels unprofessional, however good it looks once it loads.
Search engines notice. Google uses page experience signals, including how fast and stable a page feels, as part of how it ranks pages. Speed alone won’t put a weak page at the top, but slowness can hold a strong page back.
It affects everything else. Every advert you pay for, every email you send and every social post that links to your site leads to the same slow page.
What Google measures
Google’s Core Web Vitals are a useful way to think about speed, because they measure what visitors actually experience:
- Largest Contentful Paint (LCP): how long the main content takes to appear. Google suggests aiming for 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Aim for 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the page jumps around while it loads. Aim for 0.1 or less.
You can check any page for free with Google’s PageSpeed Insights.
The usual causes
In our experience, slow small-business websites usually come down to a handful of things:
- Huge images. A photo straight from a camera or phone can be many times bigger than it needs to be. This is the most common problem and the easiest to fix.
- Too many plugins and scripts. Every slider, widget, font and tracking tool adds weight. Some load on every page even when they’re used on just one.
- Cheap or overloaded hosting. If the server is slow to respond, everything else waits.
- No caching. Without it, the site rebuilds every page from scratch for every visitor.
- Heavy fonts and video. Several font families in many weights, or autoplaying background video, add up quickly.
Quick wins
- Resize and compress images before uploading, and use modern formats like WebP.
- Remove what you don’t use: old plugins, unused widgets, tracking scripts from tools you’ve stopped using.
- Turn on caching and use a content delivery network if your host offers one.
- Limit fonts to the families and weights you actually need.
- Lazy-load images and videos further down the page, so they only load when someone scrolls to them.
Most of these can be done without touching your design. If they don’t get you far enough, the next step is usually better hosting or a leaner rebuild of the heaviest pages.
Questions people also ask
How fast should my website be?
Aim to meet Google’s Core Web Vitals on mobile: main content visible within about 2.5 seconds, quick responses to taps and no jumping layout. More importantly, test it yourself on a phone using mobile data and see how it feels.
Does page speed affect SEO?
Yes, but as one factor among many. Relevance and quality of content matter more. Speed matters most when you’re competing with pages of similar quality, and it always matters to the visitors who arrive.
Will a new website automatically be faster?
Not automatically. A new site built with speed in mind usually is, but a new design can be just as slow as the old one if it’s packed with heavy images, effects and plugins. Ask your designer how they’ll keep it fast.