How Fast Should a Small Business Website Load?
Written by Wagner, founder of Tech Studio. 25 years in software engineering and AI architecture. About Wagner
A small business website should load in under 3 seconds on a mobile phone. Past that point, visitors start to leave. Google reports that 53% of mobile visits are abandoned when a page takes longer than 3 seconds to load, so a slow site loses people before they have read a word.
This guide covers what a good load time looks like, how to test your own site for free, what usually slows a website down, and which fixes you can make yourself and which need a web developer.
What counts as a good load time
Under 3 seconds on mobile is the practical target. Google measures speed more precisely with Core Web Vitals, three measures of how a page feels to a real visitor: how quickly the main content appears, how quickly the page responds when someone taps it, and whether things jump around while it loads.
| Measure | What it tells you | Good result |
|---|---|---|
| LCP (Largest Contentful Paint) | How long the biggest item on screen, usually a hero image or headline, takes to appear | Under 2.5 seconds |
| INP (Interaction to Next Paint) | How quickly the page reacts when someone taps a button or opens a menu | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | How much the page jumps around as it loads, such as a button moving just as you tap it | Under 0.1 |
Why speed matters to a small business
- Visitors leave. Most UK visitors arrive on a phone, often on a mobile connection, and a page that hangs gets abandoned. That is an enquiry or a sale you paid to attract and never received.
- Search ranking. Google takes page experience into account, and slower sites can rank lower than faster competitors offering the same thing.
- Trust. A slow or jumpy site looks neglected. For a local business competing with others in the same town, that first impression counts.
- Wasted spend. If you pay for ads or invest in search visibility, every visitor lost to a slow page is money already spent.
How to test your website speed for free
Two free tools cover most of what a business owner needs. Test your homepage and your most important page, such as a services or contact page, and check the mobile result first.
- Google PageSpeed Insights. Free, from Google. Paste in your address and it reports the Core Web Vitals above for mobile and desktop, and lists what is holding the page back.
- GTmetrix. Free to use for basic tests. It shows a waterfall of everything the page loads, which makes it easy to spot a single oversized image or a slow third-party script.
Run each test more than once and at different times of day, because results vary. Look at the pattern rather than a single score. A page that is consistently slow on mobile has a real problem. One slow result on a busy afternoon may not.
What slows a website down
Most slow small business sites trace back to a short list of causes.
| Cause | Why it slows the site | Who usually fixes it |
|---|---|---|
| Large images | Photos straight from a camera or phone can be many times larger than a web page needs, and the visitor has to download all of it | You can often resize and compress them yourself. A developer can set it up so it happens automatically |
| Cheap or crowded hosting | On low-cost shared hosting your site competes with many others for the same server, so it answers slowly | Moving host is a one-off job. A developer can do it without taking the site offline |
| Too many plugins | Each plugin adds code to load, and some run on every page whether the page needs them or not | You can remove ones you do not use. Deciding which are safe to remove is easier with a developer |
| Bloated code and themes | Multipurpose themes and page builders ship far more code than any one site uses | A developer. This is the hardest to fix without rebuilding parts of the site |
| Third-party scripts | Chat widgets, trackers, embedded videos and social feeds each load from another company's server | You can decide which ones earn their place. A developer can delay them until the page is ready |
| No caching | Without caching, the server rebuilds the same page for every visitor instead of serving a saved copy | A developer, or a caching feature on your host |
Hosting and where your visitors are
If your customers are in the UK, host your site in the UK or nearby. Distance adds delay, and a server far from your visitors answers more slowly than one close by. Ask your host where your site is served from, and whether a content delivery network (CDN) is included. A CDN keeps copies of your pages on servers in many places, so each visitor is served from one close to them.
What you can do yourself and what needs a developer
A lot of the quick wins are within reach of the site owner:
- Resize and compress images before you upload them.
- Delete plugins, widgets and embeds you no longer use.
- Remove videos that start playing on the homepage.
- Check what your host includes for caching and a CDN.
Some fixes are not safe to attempt without experience, because a wrong change can break the site:
- Moving to faster hosting without losing email or search rankings.
- Cutting down heavy themes and page builders.
- Fixing layout shift and slow response on tap (CLS and INP), which sit in the code.
- Setting up caching, image handling and a CDN properly.
If you have fixed the easy things and the mobile score is still poor, the cause is usually in how the site is built. That is the point to bring in a web developer.
Where we fit
We are a UK company that builds websites and web applications, with 25 years of engineering experience behind it. Speed is part of how we build a site from the start, not something we bolt on at the end. If your site is already live and slow, we can look at what is holding it back and tell you plainly whether it needs a few fixes or a rebuild. If a small change from you is all it needs, we will say so.
Action steps
- Test your homepage and your most important page on Google PageSpeed Insights. Note the mobile result.
- Check your LCP, INP and CLS against the targets: under 2.5 seconds, under 200 milliseconds and under 0.1.
- Resize and compress your largest images, then test again.
- Remove plugins, widgets and embeds you do not use.
- Ask your host where your site is served from and whether caching and a CDN are included.
- If the mobile result is still poor, ask a web developer to look at the site. Ask what is causing the slowness before you ask what it will cost.
A fast website is not a bonus feature. It is what decides whether a visitor stays long enough to become a customer.
