Why your small business website is slow, and what to fix first
A slow website costs a small business in quiet ways. Visitors on a phone give up before the page appears, a booking form takes long enough that people abandon it, and search engines treat page experience as one of many signals when they rank results. The good news is that most slow small business sites are slow for the same few reasons, and the biggest gains usually come from the cheapest fixes.
This guide explains how to measure speed in a way that reflects real visitors, the usual causes in the order we check them, and the changes that look helpful but are not.
Measure first, the way visitors feel it
Before changing anything, record where you start. Google describes page experience with three measurements, called Core Web Vitals:
- Largest Contentful Paint (LCP): how long until the main content, usually the large image or headline at the top, has appeared. Google's guidance is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. The guidance is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the page jumps around while it loads, such as text moving down when an image or banner appears above it. The guidance is 0.1 or less.
Free tools such as PageSpeed Insights show these numbers for a page. Where enough people visit your site, the tool also shows field data collected from real visitors' browsers, which matters more than a single lab test. Test on a phone setting, not only on a fast office computer, and test the pages that earn money: the home page, a service or product page, and the contact or checkout page.
1. Images are usually the biggest problem
On most small business sites we review, images make up most of the page's weight. A photo straight from a phone or a stock library can be several megabytes, displayed in a box a few hundred pixels wide. Fixes, in order:
- Resize each image to the largest size it is really shown at, and provide smaller versions for phones.
- Use a modern format such as WebP or AVIF, which are often much smaller than JPEG or PNG at the same visible quality.
- Load images below the fold lazily, so the browser fetches them only as the visitor scrolls. Do not lazy-load the main image at the top; that delays the number LCP measures.
- Give every image a width and height in the page code, so the browser reserves its space and the layout does not jump.
2. Too many scripts from too many places
Each chat widget, analytics tool, review badge, social feed and advertising tag adds code that the visitor's phone must download and run. Several of them can make a page feel frozen when someone tries to tap a button, which is what INP measures. List every outside script your site loads and ask whether each one still earns its place. Remove the ones nobody uses, load the rest with the defer or async attribute where their provider allows it, and avoid loading a heavy widget on pages where it is not needed.
3. Fonts that hold the text back
Custom web fonts look good but can leave the page blank or invisible for a moment while they download. Use only the weights you really need, host them on your own site or a fast font service, and set font-display: swap so the text appears at once in a fallback font and switches when the custom font arrives. Preloading the one font used in the main headline can also help.
4. Hosting and caching
If the server itself takes a long time to send the first byte of the page, nothing else can start. This is common on crowded shared hosting and on content systems with many plugins that rebuild every page for every visitor. Page caching, where the server keeps a ready-made copy of each page, often helps the most. A content delivery network keeps copies of your files in data centers close to your visitors. Make sure your server tells browsers how long they may keep static files such as images, styles and scripts, so returning visitors do not download them again.
5. Plugins, themes and page builders
Heavy themes and page builders often load the code for every feature on every page, whether the page uses it or not. Each plugin can add its own scripts and styles too. Deactivate plugins you no longer use, replace ones that do a small job with a lot of code, and check your speed numbers after each change so you know which one helped. Keep everything updated: old plugins are slow and a common way into a site.
Changes that look helpful but are not
- Chasing a perfect score. A score of 100 in a lab test does not matter if real visitors on phones still wait. Watch the field data and the pages that make money.
- Installing a speed plugin on top of everything else. It can help, but it cannot fix five megabyte images or a dozen unused widgets, and it adds its own code.
- Removing content to make a page lighter. Visitors and search engines come for the content. Make it lighter, do not take it away.
- Testing only once. Every new widget, plugin or large image can undo the work. Check again after each change to the site.
The short version
Measure the pages that earn money on a phone setting, and record LCP, INP and CLS. Then fix in the order that usually pays most: resize and convert images and give them sizes, remove or defer outside scripts you do not need, make fonts appear at once, add page caching and sensible browser caching, and trim plugins and heavy themes. Check the numbers after every change, and watch what real visitors experience rather than a single score.