You clicked your own website on your phone this morning, waited, watched a grey box sit there, and thought: that cannot be helping. You are right. If you are asking why your website is so slow, the answer is almost always one of about five things, and most of them are fixable without rebuilding anything.
Speed matters commercially, not just technically. Google uses page experience as a ranking signal, and every extra second of load time costs you visitors who were never going to wait. On a phone, on patchy 4G, in a van, people leave.
This is a plain-English guide to what actually slows a small business website down, how to find out which problem you have in about five minutes, and what to fix first. No jargon you need to look up.
The three numbers Google actually measures
Google grades page experience using Core Web Vitals, three metrics with unhelpful names and simple meanings:
- LCP (Largest Contentful Paint) is how long before the main thing on the page, usually your hero image or headline, actually appears. Google wants this under 2.5 seconds.
- INP (Interaction to Next Paint) is how quickly the page responds when someone taps something. Under 200 milliseconds is good.
- CLS (Cumulative Layout Shift) is how much the page jumps about while loading. You have felt this: you go to tap a button, an image loads above it, everything shifts, and you tap the wrong thing. Google wants this under 0.1.
Two things worth knowing. Google judges these on real visitor data, not a lab test, and it uses the 75th percentile, meaning three quarters of your visitors need a good experience for the page to pass. And it measures mobile separately, which is where most small business sites fall down.
For context, only around 36 per cent of WordPress sites pass Core Web Vitals on mobile. If yours does not, you are in ordinary company, and the gap is winnable.
Find out what is actually wrong in five minutes
Before changing anything, measure. Two free tools tell you almost everything.
Run your homepage and your busiest service page through PageSpeed Insights (search for it, paste your URL). Ignore the big score out of 100 for a moment and look at the top section, which shows real-world data from actual visitors. That is what Google grades you on. The score underneath is a lab simulation and it is useful only for diagnosing causes.
Then open Google Search Console and look at the Core Web Vitals report. It groups your pages and tells you which templates are failing, which is more useful than testing pages one at a time.
Test on mobile. Always. Your desktop experience on office broadband is not the experience Google is measuring or the one your customers get.
The five things that are usually to blame
Unoptimised images
This is the most common cause by a distance, and the easiest to fix. Someone uploads a 4MB photo straight off a phone or a stock site, the page displays it at 800 pixels wide, and every visitor downloads the full thing anyway.
Fix it by resizing images to the size they are actually displayed at, saving them as WebP rather than JPEG or PNG, and compressing them. A hero image should be well under 200KB. On WordPress, an image optimisation plugin will do this in bulk for your existing library.
Also make sure images have width and height set. Missing dimensions are the main cause of that jumping-about problem, because the browser does not reserve space until the image arrives.
Too many plugins
The average WordPress site runs 20 to 30 plugins, and each one can add its own CSS and JavaScript to every page, whether that page uses it or not. A contact form plugin loading its scripts on your blog posts is pure dead weight.
Go through your plugin list honestly. Deactivate anything you are not actively using, then delete it rather than leaving it dormant. If two plugins do overlapping jobs, keep one. This is the single most effective thing most site owners can do in an afternoon.
Cheap shared hosting
If your server takes 800 milliseconds to respond before it has even started sending the page, no amount of image optimisation rescues you. Budget shared hosting puts hundreds of sites on one machine and you get whatever is left over.
You can see this in PageSpeed Insights as a slow “server response time” or “time to first byte”. If that number is high, the fix is hosting, not tinkering. Decent managed hosting costs more per month than the cheapest options and usually pays for itself in the first month if it moves you into the top three for anything.
No caching
Without caching, your server rebuilds the entire page from scratch for every single visitor. With caching, it builds it once and serves a saved copy. This is the highest-return fifteen minutes of work available to most WordPress sites.
A good caching plugin handles this along with minifying your CSS and JavaScript. Many decent hosts include server-level caching, which is better still. Check whether yours does before installing anything.
Heavy themes and page builders
Page builders make sites easy to edit, which is genuinely valuable, but they carry weight. Depending on how a site is built, a builder can add a few hundred kilobytes of JavaScript to every page, which affects both how fast it paints and how quickly it responds to taps.
This is a configuration problem more than a condemnation. A carefully built site using a page builder can absolutely pass Core Web Vitals: it comes down to loading only the assets a page needs, keeping the number of nested sections sensible, and not stacking a builder on top of a bloated theme. A site that was thrown together with every widget switched on is a different story.
What to fix first, in order
If you do nothing else, do these four, in this order:
- Compress and resize your images, and set width and height on them. Biggest gain, least risk.
- Turn on caching if it is not already running, either at the host or with a plugin.
- Audit and delete unused plugins. Test the site after each removal.
- Check your server response time. If it is slow, move host. Nothing else will fix it.
Then re-measure. Give it a few weeks before judging the real-world data in Search Console, because it is based on a rolling window of actual visitor sessions and does not update instantly.
When speed is not really the problem
One honest caveat. Speed is a tiebreaker, not a magic ranking lever. Google has been fairly clear that page experience matters most when other things are equal. A fast page with thin content still loses to a slow page that genuinely answers the question better.
So if your site loads in three seconds but you are nowhere in the rankings, speed is not your bottleneck. Relevance, content and local signals are doing more damage. And if your site is fast and ranking but not producing enquiries, the problem is further down the funnel, which is what our post on why a website gets visitors but no enquiries digs into.
Where speed does earn its keep is on mobile, where slow pages lose people before they ever read a word, and in competitive local markets where you and three rivals all look broadly similar to Google. That is where a fast, well-built website quietly wins.
FAQs
What is a good page load time for a small business website?
Aim for your main content to appear within 2.5 seconds on a mobile connection, which is Google’s threshold for a good Largest Contentful Paint score. Anything over four seconds is costing you visitors noticeably. Test on mobile rather than desktop, because that is what Google grades and what most of your customers are using.
Do Core Web Vitals actually affect Google rankings?
Yes, but as a tiebreaker rather than a primary factor. Page experience helps decide between pages of similar relevance and quality. A fast page with poor content will not outrank a genuinely better answer. Where it matters most is competitive local markets, where several businesses look similar to Google and experience signals separate them.
Why is my website fast on desktop but slow on mobile?
Mobile devices have less processing power and often slower connections, so the same page has to work harder. Large images that download fine on broadband become a real cost on 4G, and JavaScript that a laptop chews through easily can block a phone’s main thread. Google also measures mobile separately, so a good desktop score tells you very little.
Will a caching plugin fix my slow website?
It will help, often substantially, but it is not a cure-all. Caching stops your server rebuilding the page for every visitor, which cuts response time. It does nothing about oversized images, plugin bloat or slow hosting. Treat it as one of four fixes rather than the whole job, and always test the site after enabling one.
How many plugins is too many for WordPress?
There is no fixed number, because a well-coded plugin can cost almost nothing and a badly-coded one can cost a second. What matters is what each plugin loads on each page. A useful rule: if you cannot say what a plugin does and when you last used it, remove it. Most sites can lose a third of their plugins with no visible change.
Want to know what is really slowing you down?
Speed problems are usually a handful of specific, findable causes rather than a mystery. If you would rather someone just tell you which ones apply to your site, book a free discovery call. We will run your pages properly, show you exactly what is dragging them down, and tell you honestly whether it is worth fixing or whether your budget is better spent elsewhere.