You open your own website on your phone while waiting for a customer to call back, and it takes long enough that you start to wonder whether they bothered. The logo appears, then a blank space, then a large photograph slowly fills in, then the text jumps down the screen as something else loads above it. On the office computer it seemed fine. On a phone, in a car park, it feels like it might be costing you work.
It might be. A slow site does lose some visitors, particularly on phones, and particularly people who are comparing several businesses at once. But speed is also one of the easiest things to be sold a fix for. Hosting upgrades, speed plugins, "performance packages", full rebuilds: all of them promise a faster site, and some of them deliver nothing you would notice.
This guide sets out how to find out whether your site is actually slow, what is most likely causing it, which fixes tend to make a real difference, and which are worth leaving alone. It is written so you can do the first checks yourself, in an afternoon, before paying anyone.
Table of Contents
First, Is It Actually Slow?
It sounds obvious, but it is worth checking before anything else. Owners judge their own sites in unusual conditions. Sometimes that makes a site look slower than it is: a weak signal in a rural yard, an old phone, twenty tabs open. Sometimes it makes a site look faster: the office broadband is quick, and the browser has already stored most of the site from the last hundred visits, so it barely has to download anything.
Your customers see neither of those. They usually arrive for the first time, on a phone, on whatever connection they happen to have. That is the visit worth measuring.
How it feels and how it measures
A quick, rough test you can do now:
- Turn off Wi-Fi on your phone and use mobile data.
- Open a private or incognito tab, so the browser has nothing stored from earlier visits.
- Type in your address and watch. Note roughly when you can first read the main heading, when you could tap the phone number, and whether anything jumps around as it loads.
- Try a service page as well, not just the homepage. Customers often land on those first from Google.
- Do the same for two competitors. This tells you whether your site is slow or whether everyone's is on that connection.
If your site is readable and usable about as quickly as the others, speed is probably not your main problem, even if a score somewhere says otherwise. If you are still looking at a blank screen while competitors' pages are ready, it is worth digging further.
Running PageSpeed Insights
Google's PageSpeed Insights is free and gives you a more consistent picture. Enter your page address and it tests the page on a simulated phone, then reports a score and a list of suggestions. It also shows, where Google has enough visits to report on, how the page has performed for real visitors using Chrome over recent weeks.
Those two parts are worth keeping separate in your head:
- The real-visitor data, labelled as what your actual users experienced, is the more meaningful of the two. Small sites often do not have enough visits for Google to show it, which is normal.
- The lab test, with the familiar score out of 100, is a single simulated visit on a deliberately slow phone and connection. It is useful for finding causes and comparing before and after. It moves around between runs, so run it two or three times and look at the general level rather than one number.
Test the mobile result, not the desktop one. The desktop score is almost always better and almost always less relevant.
What the Scores Mean
PageSpeed Insights uses a handful of measurements. You do not need to understand them in depth, but knowing what each one describes helps you tell which problem you have.
| Measurement | In plain terms | What usually makes it bad |
| Largest Contentful Paint | How long until the biggest thing on screen, usually the main image or heading, appears | Huge images, slow server response, scripts that block the page |
| Cumulative Layout Shift | How much the page jumps around while loading | Images without set sizes, banners and adverts that push content down, late-loading fonts |
| Interaction to Next Paint | How quickly the page responds when you tap something | Heavy scripts, chat widgets, bloated themes |
| First Contentful Paint | How long until anything at all appears | Slow hosting, render-blocking files |
| Time to First Byte | How long the server takes to start replying | Hosting, or a site that builds every page from scratch on each visit |
A few points worth bearing in mind about the score itself.
The number is not the goal. A page scoring in the seventies that shows its heading and phone number quickly is better for a customer than a page that scores in the nineties because everything useful was stripped out. Chasing a perfect score on a small business site is rarely good value.
The suggestions are not a to-do list. PageSpeed lists everything it could find, with estimated savings. Some of those savings are tiny. Some suggestions are impossible to follow on certain platforms. Read them for patterns, particularly anything mentioning images or a particular script, rather than trying to clear every line.
Third-party items are counted against you. A booking widget, a review feed or a tracking tag from another company can drag the score down, and you may decide it is worth keeping anyway. That is a reasonable decision as long as it is a decision.
A fair question to ask of any score: on a phone, how long before a stranger can read what you do and tap to contact you? That is the part that wins or loses the enquiry.
The Usual Suspects
On small business sites, the causes of slowness are not very varied. Most slow sites have one or two of the following, and the first is by some distance the most common.
Images
Photographs straight off a modern phone or camera are very large files. They are made to be printed or viewed full screen on a big monitor. When they are uploaded to a website unchanged, every visitor's phone has to download the whole thing, then shrink it to fit a screen a few inches wide.
One oversized photograph at the top of the homepage can account for most of the load time on its own. A gallery page of twenty unprocessed photographs can be dramatically slower than the rest of the site.
Signs this is your problem:
- PageSpeed mentions properly sizing images, serving images in modern formats, or efficiently encoding images, with large estimated savings.
- The main image is the last thing to appear when you load the page on mobile data.
- Pages with more pictures are noticeably slower than pages with few.
This is also the cheapest problem to fix, which is why it comes first. Photos for a trade website covers choosing and preparing pictures more generally.
Scripts and add-ons
Every extra feature on a site tends to bring its own code: a chat bubble, a cookie banner, a review carousel, an Instagram feed, social sharing buttons, several tracking tags, a pop-up, a map. Each one may be modest. Together they can mean a phone downloading and running far more code than the page itself needs.
On WordPress sites in particular, plugins accumulate. Something was installed years ago for a feature that has since been removed, but the plugin still loads its files on every page. Some plugins load on every page even though they are only used on one.
Signs this is your problem: PageSpeed mentions reducing unused JavaScript, minimising main-thread work, or reducing the impact of third-party code, and names specific services; the page looks ready but does not respond to taps for a moment; or the slowness appeared after something was added.
The theme or builder
Some sites are slow because of how they were built. Multipurpose themes that can do anything tend to load the code for everything, whether you use it or not. Drag-and-drop page builders often produce heavy, deeply nested pages. A site may have been put together with one builder inside another.
This is harder to diagnose yourself, but a few clues help. If even a nearly empty page, such as a short privacy page, is slow, the weight is coming from the template rather than the content. If PageSpeed points at lots of CSS and JavaScript files you do not recognise, often with the theme or builder's name in them, the build is a large part of it.
This is the cause where honest advice matters most, because it is the one that can only partly be fixed without changing the build. More on that below.
Hosting
Hosting is the most commonly blamed cause and, for most small sites, not the main one. It does matter sometimes. Very cheap shared hosting can be slow to respond, especially at busy times, and a server a long way from your customers adds a little delay to every request.
The measurement to look at is the server response time, often shown as Time to First Byte or as a suggestion to reduce initial server response time. If the server takes a long time to reply before anything else can happen, hosting, or the way the site generates its pages on the server, is worth looking at. If the server replies quickly and the page is still slow, better hosting will not fix it, because the time is being spent downloading and running what the page asks for.
That distinction alone saves a lot of owners from paying for an upgrade that changes nothing they can see.
Fonts, videos and sliders
A few smaller culprits turn up often enough to mention:
- Several web fonts, each in several weights, all loaded before the text can show.
- A background video on the homepage, which on a phone is a lot to download for something decorative.
- Image sliders, which usually load every slide up front even though most visitors only see the first.
- Embedded maps and videos from other services, loaded the moment the page opens rather than when someone reaches them.
None of these is wrong in itself. Each is worth asking about: does it help a customer decide to get in touch, and is it worth what it costs in load time?
Working Out Which It Is
Putting those together, a short sequence will usually point at the main cause.
| What you see | Likely cause | Where to start |
| Large savings listed for images | Oversized photographs | Resize and compress images, starting with the top of the homepage |
| Slow server response, everything else modest | Hosting or server-side setup | Caching, then the hosting plan |
| Named third-party services taking time | Widgets and tracking tags | Remove what you do not use, delay what you keep |
| Even a near-empty page is slow | The theme or builder | Trim plugins and features; consider whether the build is the problem |
| Page jumps around while loading | Images without sizes, banners, fonts | Set image dimensions, make banners smaller |
| One page much slower than the rest | Something on that page | Gallery, video, map or embed on that page |
Two simple comparisons help confirm it. Test your heaviest page against your lightest one: if both are slow, look at the template and hosting; if only the heavy one is, look at what is on it. Then test a page before and after removing one suspect, if you are able to. A clear difference tells you more than any list of suggestions.
Fixes Worth Doing Yourself
Many owners can make the first round of improvements without paying anyone, depending on the platform and how much access they have.
Resize images before uploading. A photograph for a web page rarely needs to be wider than the largest space it fills on screen. Most phones and computers can export a smaller copy, and free tools will compress a picture further without visible loss. Replace the largest images first, especially anything at the top of a page.
Use a modern format where your platform allows it. WebP and AVIF files are usually much smaller than the equivalent JPEG. Many platforms now convert images automatically; check whether yours does before doing it by hand.
Remove what you do not use. Go through plugins, widgets and embedded feeds. If you cannot say what something is for, find out, and if nobody needs it, remove it. Deactivated is better than active; deleted is better than deactivated. Take a backup first.
Cut the homepage slider or video down. One strong photograph of real work, sized properly, usually serves customers better than five rotating slides, and it is lighter.
Check tracking tags. Sites often carry tags from services nobody looks at any more: an old analytics account, an advertising pixel from a campaign that ended. Each still loads.
Turn on caching if your platform offers it. Caching stores ready-made copies of pages so the server does not rebuild them for every visitor. Many hosts and platforms include it as a setting.
Change one thing at a time, note the date, and run PageSpeed two or three times afterwards. It is the only way to know which change helped.
Fixes Worth Paying For
Some work is worth handing to someone who knows what they are doing, because it touches how the site is built and is easy to get wrong.
- Setting image sizes and lazy loading properly across the template, so images below the fold load only when needed and the page does not jump.
- Deferring scripts so that chat, reviews and tracking load after the content a customer needs, rather than before it.
- Reducing the template's weight, removing unused code the theme loads on every page.
- Fixing a slow server response where caching and configuration, rather than a new plan, are the cause.
- Replacing a plugin that is known to be heavy with a lighter way of doing the same job.
When asking for this kind of work, ask for something you can check: which pages will be tested, what the before results are, and how the after results will be shown. A good answer names the cause and the specific changes. A vague one promises a better score.
What any of this costs depends on the platform, the state of the site and how much there is to untangle, so it is worth getting a description of the work in writing before agreeing to it.
Where Money Tends to Be Wasted
| Spend | Why it appeals | Why it often disappoints |
| Upgrading hosting first | Easy to buy, sounds technical | If the server already responds quickly, images and scripts are still the bottleneck |
| Stacking speed plugins | Promise a fix in one click | Several overlapping plugins can conflict, break layouts, or add their own weight |
| Paying to hit a perfect score | A clear, satisfying target | The last points rarely change what a customer experiences, and can mean stripping useful features |
| A rebuild on the same heavy builder | Feels like a fresh start | The same template weight comes straight back |
| Ongoing "speed optimisation" with no reporting | Reassuring | Without before and after figures, there is no way to tell if anything happened |
None of these is always wrong. Hosting does sometimes need upgrading, and one well-chosen caching plugin can help a WordPress site considerably. The point is to fix the cause you have actually found, not the one that is easiest to sell.
A useful test for any speed offer: can they tell you what is slowing the site down now, in plain words, before you pay? If they cannot, they are guessing.
Does Speed Really Cost Enquiries?
Sometimes, and it is worth being honest about how much. A page that takes a long time to show anything on a phone will lose some visitors before they read a word. Pages that jump around cause mis-taps and irritation. A form that is slow to respond makes people wonder whether it sent.
Google does take page experience into account, but it is one signal among many. A slow page that answers a search well can still outrank a fast page that does not. Speed is rarely the reason a site cannot be found at all; why nobody finds your website on Google covers the more common causes.
The practical position is this. If your site is clearly slower than competitors on a phone, fixing that is worth doing and will help a little with everything else. If it is roughly as fast as theirs, more speed work will bring less than improving what the pages say. Owners who see plenty of visits and few enquiries are usually better served by looking at the pages themselves; why a trade website gets clicks but no calls goes into that.
To judge for yourself, look at Search Console and your enquiry log before and after a speed fix, over a few weeks, allowing for the season. If nothing else changed and enquiries from that page rose, the fix probably helped. If nothing moved, the page had a different problem.
When It Is Time to Rebuild
Sometimes the slowness is a symptom rather than the disease. If the site is built on a heavy theme or builder, with years of accumulated plugins, and every fix seems to break something else, there comes a point where patching costs more than it saves. The same applies if the site is slow and also out of date, awkward on a phone and not bringing enquiries anyway.
Questions that help decide:
- Is a near-empty page on the site still slow? If so, the build itself is heavy.
- Have previous speed fixes held, or does the site slow down again after each update?
- Is speed the only problem, or one of several?
- Can you change the site yourself, or does every change need a developer?
If a rebuild is the answer, make sure the new site is not built the same way as the old one, and that every existing address is redirected to its closest new page so nothing Google already knows is thrown away. Redesign or fix your website and signs you need a new website help with the decision, and what a 301 redirect is explains the redirects.
For what it is worth on this subject, Operosus builds sites by hand rather than on a page builder, and the live site does not call on Operosus to load a page.
A Slow Site Worked Through
Here is an imagined landscaper whose site feels slow. The business and the details are illustrative, not drawn from a client, but the pattern is common.
The phone test. On mobile data, in a private tab, the homepage shows a blank area for a noticeable time before a large photograph of a patio slowly appears. Two competitors' homepages are readable well before it. A short contact page on the same site loads quickly.
PageSpeed. The mobile score is low across three runs. The largest suggestion by far is image related: the patio photograph is a full-size camera file. Further down, a review carousel and an Instagram feed are named among the third-party items. Server response time is fine.
The reading. Fast contact page plus fine server response means hosting is not the issue, and the template is not unusually heavy. The homepage is slow because of what is on it.
The fixes. The owner exports a smaller copy of the patio photograph and replaces it. The gallery page gets the same treatment over an evening. The Instagram feed, which nobody remembers adding, is removed from the homepage and replaced with a link. The review carousel stays, because the owner values it, but whoever looks after the site is asked whether it can load after the main content.
What did not happen. An email offering a hosting upgrade is set aside, because the server was never the problem. So is a suggestion to rebuild.
Afterwards. The homepage is readable on mobile data about as quickly as competitors'. The owner notes the date and watches Search Console and enquiries over the following weeks rather than the next morning.
The largest gain came from one photograph. That is typical.
Keeping It Fast
Sites rarely become slow overnight. They slow down gradually as photographs, plugins and widgets are added and nothing is taken away. A few habits keep that in check:
- Resize every image before it goes on the site, or check that your platform does it for you.
- Ask what each new feature costs in load time before adding it, and remove the old one if it replaces something.
- Run PageSpeed on your main pages every so often, and keep a note of the results so you can spot a change.
- Test on a phone, on mobile data, rather than relying on how the site feels on office broadband.
- Review plugins and tracking tags once or twice a year and remove what nobody uses.
What should happen to your website every month sets out a wider routine, and mobile responsive web design covers the other phone problems worth checking at the same time.
If you would rather have a second view before doing anything, the Operosus free website review includes Google's own PageSpeed scores for your home page on a phone, alongside the search basics.
The short version: test on a phone against competitors, run PageSpeed a few times, look at images first, check whether the server is genuinely slow before blaming hosting, remove what you do not use, and pay for build work only once someone can tell you plainly what the cause is.
Most slow small business sites are slow for one or two ordinary reasons, and most of those can be found in an afternoon. Knowing which one you have is what stops you paying for the wrong fix, and it usually turns a vague worry into a short, specific list.