Why website speed matters, and how to fix yours
Speed is the rare thing that is both a ranking factor and a conversion factor, and it is measurable for free in about a minute. Here is how to measure yours honestly, and what to fix in what order.
Why it matters more than it sounds like it should
People do not wait. Google’s own research has consistently found that as a mobile page goes from one second to three, the chance of someone leaving rises sharply, and it keeps climbing from there. They do not send you an email about it — they tap back and choose the next result.
Speed also feeds directly into ranking. Google’s Core Web Vitals measure how quickly the main content appears, how quickly the page responds to a tap, and whether things jump around while loading. They are a genuine ranking signal, and more importantly they measure the things that make a page annoying.
The unfair part is that your visitors do not compare you against a standard. They compare you against the last site they used, which was probably built by a company with a large budget.
How to measure it honestly
Two free tools, and one rule: always read the mobile number. Most small business traffic is mobile, on a mid-range phone, on mobile data. Your desktop score on office wifi is flattering and irrelevant.
- Google PageSpeed Insights — paste your URL in. Read the mobile tab. If real users are visiting, it will also show field data, which is what actually counts.
- Your own phone, on 4G, with wifi turned off. Time it. This tells you what a customer experiences, which no score quite captures.
Test your homepage and your busiest service page, because they often differ considerably.
What the numbers mean
- 90–100: good. Rare for a small business site and worth being pleased about.
- 50–89: needs work. Typical for a WordPress site with a handful of plugins. Usually fixable.
- Below 50: costing you enquiries today. Usually a heavy theme or page builder, uncompressed images, or both.
Do not chase 100. The distance between 85 and 100 is mostly of interest to developers; the distance between 35 and 85 is money.
The fixes, in order of return
1. Your images
This is the single biggest cause of slow small business websites, and the easiest to fix. A photograph straight from a phone or a stock library can be 4MB. On a page it should be 100–300KB.
- Resize before uploading: no image needs to be wider than about 2000 pixels, and most need far less.
- Save as WebP where you can, or well-compressed JPEG.
- Make sure images below the fold load lazily.
- Always set width and height, so the page does not jump as they load.
Halving your image weight often halves your load time. Nothing else on this list is that efficient.
2. Fewer plugins and scripts
Every plugin adds code to every page, whether that page uses it or not. A site with thirty plugins is loading a lot of things nobody asked for. Audit them: deactivate anything you cannot name a purpose for, and check what is left is actually maintained.
The same goes for third-party scripts — chat widgets, analytics, heat maps, review carousels, tracking pixels. Each is a request to somebody else’s server, and your page waits for it. A chat widget that adds two seconds is not paying for itself unless it is producing real conversations.
3. Your hosting
Cheap shared hosting puts hundreds of sites on one machine. When the machine is busy, your site is slow, and nothing you do to the pages fixes it. If your server response time is over about 600ms, hosting is your bottleneck. Moving is usually straightforward and it is what our hosting and care plan is for.
4. Fonts
Custom fonts are frequently loaded from another domain, in four weights, when the site uses two. Load only the weights you use, self-host them, and use font-display: swap so text is visible immediately rather than after the font arrives.
5. Page builders
The hardest one to hear, because it usually means a rebuild. Drag-and-drop builders produce deeply nested markup and load their entire framework on every page. You can optimise around one, but there is a floor you cannot get below. If a site is stuck in the 30s despite everything above being done, this is usually why.
We hand-write the HTML and CSS and use no page builder and no plugin stack, which is why the sites we build typically load in under a second. It is not cleverness — it is the absence of forty things that did not need to be there.
Questions
What is a good page load time?
Under two seconds on a mobile connection is a reasonable target for a small business site, and under one second is achievable if the site is built simply. What matters more than the absolute number is that your main content and your phone number appear quickly — a page that shows the important part in 1.2 seconds and finishes loading decoration at 3 seconds feels fast to a human.
Does website speed really affect Google rankings?
Yes, through Core Web Vitals, though it is one signal among many and relevance matters more. A fast page will not outrank a genuinely more relevant slow one. But between two comparable pages it is a tie-breaker, and the conversion effect is larger than the ranking effect anyway — you lose visitors before Google ever gets involved.
Will a caching plugin fix my slow site?
It will help, and it is worth having, but it treats the symptom. Caching serves a pre-built copy of the page faster; it does not reduce the four megabytes of images or the twenty scripts the browser still has to download. Fix the images and the plugin count first, then add caching on top of a site that is already lighter.
Keep reading
More free guides
Find out what your website would cost
Tell us what your business does and what you need the site to do. You will get a straight answer: what it needs, what it costs a month, and how quickly it can be live. No sales call, no obligation.
No pressure, no jargon, no obligation. We usually reply the same working day.