A visitor on a phone, standing in a driveway with a burst pipe, does not wait for your homepage to finish loading. They go back and tap the next result. Speed is not a technical vanity metric for a small business; it is the gap between a ringing phone and a missed one.
The good news is that on most small business sites, a handful of causes account for nearly all of the delay, and each has a straightforward fix.
What "fast" actually means
People talk about speed as if it were one number. It is really a few moments in the page's life:
- First content appears. How long until the visitor sees anything at all.
- Main content appears. When the biggest element, usually the large photo or headline block, is visible. A common target is within about 2.5 seconds on a mid-range phone and an ordinary mobile connection.
- The page stops jumping. Layout shifts happen when images or ads load late and push text down, so people tap the wrong thing.
- It responds to taps. Buttons and menus work immediately, not after a pause.
You do not need to master the jargon. You need to find which of these moments is slow on your site and why.
How to test properly
Your own experience is misleading. You are on fast office wifi, with your site cached in the browser. Test like a customer instead.
- Use a standard speed test on your homepage and your most important service page. Run it on the mobile setting, not just desktop.
- Run it three times and note the middle result. Single runs vary.
- Try it on your phone with wifi off, on ordinary mobile data. Time how long until you can read the headline and tap the call button.
- Open the test's list of suggestions and sort them by how much time they would save. Ignore the tiny ones.
Our free website grader includes a speed section that translates the findings into plain English, so you can pass a short list to whoever looks after your site.
Fix 1: Compress and resize your images
This is the number one cause of slow small business sites, by a distance. A photo straight from a modern phone can be 4 to 8 MB. On a page that shows it at 400 pixels wide, most of that is wasted.
- [ ] Resize before uploading. A photo displayed at 800 pixels wide does not need to be 4000 pixels wide. Twice the displayed size is plenty for sharp screens.
- [ ] Compress. Quality settings around 70 to 80 percent are usually indistinguishable to the eye and a fraction of the file size.
- [ ] Use modern formats. WebP and AVIF are smaller than JPEG at similar quality and are supported by current browsers. Offer a JPEG fallback only if you need to support very old devices.
- [ ] Load below-the-fold images lazily. Images far down the page should load only when the visitor scrolls near them. Do not lazy-load the top image, since that delays what people see first.
- [ ] Set width and height on every image so the browser reserves space and the page does not jump.
A realistic aim for a homepage: total images under 500 KB to 1 MB.
Fix 2: Cut what you load from other places
Every chat widget, tracking tag, review carousel, social feed and booking plug-in is an additional download and often an additional script that has to run before the page settles. Small sites frequently carry ten or more without anyone remembering why.
Do an audit:
| Item | Keep, replace or remove? | Question to ask |
|---|---|---|
| Live chat widget | Often remove | Did anyone use it last month? |
| Social media feed | Usually remove | Could a link do the job? |
| Several analytics tags | Consolidate | Do we look at all these reports? |
| Map embed on every page | Move to the contact page only | Is it needed on the homepage? |
| Video embeds | Use a thumbnail that loads the video on tap | Does it need to autoplay? |
| Review widgets | Replace with static quotes | Can three quotes be plain text? |
Each item removed is a request that no longer competes with your headline and photo.
Fix 3: Keep fonts lean
Custom fonts make a site feel considered, but they can quietly add hundreds of kilobytes.
- Use two font families at most, and only the weights you actually use. Regular and bold are enough for most sites. A family loaded in nine weights is a common culprit.
- Host the font files yourself where possible, in the modern compressed format, instead of fetching them from another server.
- Set text to show immediately in a fallback font while the custom one loads, so visitors can read straight away.
- A well-chosen system font stack costs nothing and loads instantly. Ask whether the custom font is worth its weight.
Fix 4: Tame scripts and styles
Code is lighter than images, but sites built from layers of themes and plug-ins can ship hundreds of kilobytes of code, much of which a given page never uses.
- Remove plug-ins, themes and add-ons you no longer use. Deactivated is not the same as deleted.
- Ask your developer to minify the code (strip spaces and comments) and combine files where it helps.
- Defer non-essential scripts so they run after the page is visible. Marketing tags rarely need to run first.
- If your page is mostly text and photos, ask whether it needs a heavy framework at all. Simple sites can be plain HTML and a small stylesheet, and they load almost instantly.
Fix 5: Check hosting and caching
You can optimise everything above and still be held back by a slow server or a distant one.
- Server response time. If the very first byte takes more than about half a second, the host is a bottleneck. Cheap shared hosting overloaded with other sites is a typical cause.
- Caching. Visitors who return should not re-download your logo and styles. Static files should carry long cache lifetimes.
- A delivery network. Serving files from a location near the visitor shortens every request. Many hosts include this; some do not.
- Compression. Text files such as HTML, CSS and scripts should be sent compressed. This is a setting, not a project.
- Secure connection. Make sure the site uses HTTPS everywhere and redirects the old address to the right one in a single step, not a chain.
Fix 6: Design for mobile first
Speed and design are linked. A page that needs a huge hero image, a slider and a pop-up will never be fast. A page that opens with a headline, a short line of text, one photo and a call button will be.
- Prefer one strong image to a slider; sliders load several images for one visible slide.
- Skip pop-ups on the first screen. They are slow, annoying and a source of layout jumps.
- Keep the first screen simple so the main element can appear quickly. Our small business website checklist shows what belongs there.
A 90-minute speed tune-up plan
If you maintain the site yourself, this order gives the most improvement per minute.
- Baseline (10 min). Test the homepage on mobile three times and write down the median.
- Images (30 min). Resize and compress the five largest images on the page.
- Scripts (20 min). Remove at least two widgets or tags you do not need.
- Fonts (10 min). Cut unused weights.
- Caching and compression (10 min). Check with your host, or ask them.
- Retest (10 min). Compare to the baseline and keep a record.
Most small sites move from "frustrating" to "fine" with these steps alone.
Why this connects to being found
Speed also feeds into how search engines treat your pages, especially for searches made on a phone. It is one signal among many and will not outrank relevance, but a slow page loses the visitors that the rest of your effort earned. It sits alongside your listing and reviews described in local SEO basics.
What not to obsess over
- A perfect score of 100 on a test. Aim for a fast real-world experience, not a trophy.
- Differences of a tenth of a second.
- Desktop results when most of your visitors use phones.
Next step
Get a baseline in two minutes: grade your website and see which speed issues it flags first. If you would rather start from a site built to load quickly, Belmo Studio will make you a free preview, and you pay only if you like it.