Website Speed for Small Businesses: Test It, Find the Slow Parts and Fix Them
Learn how to test website speed, read Core Web Vitals in plain words and fix the images, scripts and hosting issues that make visitors leave.
- Test on mobile first and look at real-visitor (field) data before lab scores.
- Oversized photos are the most common reason a small site feels slow.
- Every chat widget, tracker and font family adds work for the visitor's phone.
- Caching and a content delivery network shorten the distance between your site and customers.
- Re-test after every big change; speed quietly gets worse as content is added.
Website speed is how quickly your pages appear and respond when someone opens them, especially on a phone over mobile data. A shop, salon or clinic site that takes too long to show its first screen loses people before they see a price, a photo or a phone number. This guide explains how to measure page speed, what the numbers mean, and which fixes make the biggest difference for a small business.
Speed is one part of a bigger picture. If you are planning or rebuilding your site, start with our full guide to what a small business website needs, then come back here to make it quick.
Why website speed matters for a small business
Most of your visitors arrive with a simple goal: check opening hours, see a menu, find a price, or send a message. When the page stays blank, many simply tap back and try the next result. You rarely see those lost visitors, because they never call or write. Poor website speed is a leak you cannot see in your enquiries.
Speed also shapes how trustworthy you look. A site that jumps around while loading, or ignores taps for a second, feels broken even if the content is good. Google describes page experience, including loading and responsiveness, as something its ranking systems consider alongside the relevance of your content.
There is a cost angle too. Visitors on prepaid data plans pay for every megabyte your page sends. A lighter page is kinder to them and cheaper for you to host.
How Google measures website speed: Core Web Vitals
Google groups its user-focused speed measurements under the name Core Web Vitals. Each one tracks a different moment of the visit. The table shows what they mean in everyday terms and the thresholds Google publishes on web.dev.
| Metric | What the visitor feels | Good | Poor | Usual cause on small sites |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main image or headline shows | 2.5 s or less | Over 4 s | Huge hero photo, slow server, sliders |
| Interaction to Next Paint (INP) | How long a tap or click takes to show a reaction | 200 ms or less | Over 500 ms | Too many scripts, heavy page builders |
| Cumulative Layout Shift (CLS) | Whether text and buttons jump while loading | 0.1 or less | Over 0.25 | Images without set sizes, late banners |
Between "good" and "poor" sits a middle band labelled "needs improvement". Google assesses each metric at the 75th percentile of real visits, which means most of your visitors, not just the lucky ones on fast connections, should get a good experience.
Website speed data: lab results versus field results
Speed tools show two kinds of results. Lab data comes from a single simulated test run in controlled conditions. It is great for spotting problems and checking fixes. Field data comes from real visitors using Chrome over the past 28 days, collected in the Chrome User Experience Report.
Small sites with few visitors often have no field data for website speed yet. That is normal. Rely on lab results until enough traffic builds up, and treat field data as the final judge once it appears.
How to run a website speed test properly
A single website speed test can mislead you, because network conditions vary. Follow a steady routine so your results are comparable from month to month.
- Pick three pagesTest the homepage, your busiest service or product page, and the contact page, since visitors arrive at all three.
- Run PageSpeed InsightsPaste each address into the free tool, choose the mobile tab, and note the field data and lab results.
- Repeat twice moreRun each test three times and write down the middle result to smooth out random swings.
- Read the opportunities listLook for items that mention images, render-blocking resources and unused JavaScript.
- Try a real phoneOpen the same pages on an inexpensive Android phone over mobile data and time how long the main content takes.
- Record the date and changesKeep a small log so you can link any drop in speed to the change that caused it.
You can run the test any time at PageSpeed Insights. If your site is verified in Search Console, its Core Web Vitals report groups slow pages together; our beginner's guide to Google Search Console shows where to find it.
What happens when someone opens your page
It helps to picture the journey a page takes. First the browser asks your server for the page. The server replies with the HTML, the basic structure. Then the browser fetches the stylesheets, fonts, images and scripts that the HTML mentions, and only then can it draw the full screen and respond to taps.
Every website speed fix in the rest of this guide shortens one of those bars. Smaller images shorten the yellow one. Fewer scripts shorten the last one. Better hosting shortens the first.
Images: the biggest website speed problem on small sites
Photos taken on modern phones are far larger than any screen needs. A single unedited picture can outweigh the rest of the page combined. Fixing images is usually the cheapest and fastest way to improve website speed.
Resize photos before upload for better website speed
Decide the largest width the image will ever display at. A full-width banner rarely needs more than about 1,600 to 2,000 pixels; a product thumbnail may need only 600. Resize to that width on your computer or phone before uploading, rather than relying on the page to shrink it.
Choose a modern format
WebP and AVIF are image formats designed for the web. They usually produce noticeably smaller files than older JPEG or PNG images at similar quality. Keep PNG for logos and graphics with sharp edges or transparency, and use WebP or AVIF for photos where your platform supports it.
Good source photos still matter. Clean, well-lit pictures compress better than noisy, dark ones; our guide to product photography with a phone covers lighting and backgrounds that help.
Lazy-load the images below the first screen
Adding loading="lazy" to an image tells the browser to wait until the visitor scrolls near it. This is ideal for galleries and long product lists. Never lazy-load the main image at the top, because that delays the very content the visitor is waiting to see.
Give every image a width and height
When an image has no declared size, the browser does not know how much space to reserve, so text jumps down when the picture arrives. Setting width and height attributes, or a fixed aspect ratio in your design, prevents that jump and improves your layout shift score.
Fonts, scripts and third-party add-ons
Each extra file the browser must fetch adds delay, and scripts also need processing time on the phone. Small business sites tend to collect add-ons over the years: a chat bubble, two analytics tools, a review widget, an Instagram feed, a cookie banner and a popup form.
Audit what loads on every page
List every third-party service on your site and ask one question about each: does it bring in customers or useful information? Remove anything you no longer check; each removal is a free website speed gain. Where a widget is needed on one page only, such as a booking calendar, load it on that page instead of site-wide.
Keep fonts lean
Two font families, each in two or three weights, are plenty. Every extra weight is another download. Using font-display: swap lets text appear in a fallback font while the brand font loads, so visitors are not left staring at invisible text.
Hosting, caching and a content delivery network
Your server is where every visit begins. Cheap shared hosting can take a long time to send the first byte of a page, especially at busy times. If test tools report a slow server response even on a simple page, hosting is worth reviewing.
Caching in plain words
Caching means keeping a ready-made copy of a page or file so it does not have to be rebuilt for every visitor. Server caching stores finished pages; browser caching lets returning visitors reuse files they already downloaded. Most managed platforms handle both for you.
What a content delivery network does
A content delivery network, or CDN, stores copies of your images and files on servers in many countries. A customer in Dubai then downloads them from a nearby location instead of from a server on another continent. For businesses with customers in more than one region, a CDN is one of the most effective upgrades available.
Website speed on WordPress and website builders
On WordPress, website speed depends heavily on the theme and plugins you choose. Heavy multipurpose themes and visual page builders often load large amounts of code on every page. A lighter theme, fewer plugins and one well-configured caching plugin usually help more than any single trick.
Hosted website builders manage servers and caching for you, so your main levers are image sizes, embedded widgets and the number of sections stacked on each page. Shorter pages with a clear purpose load faster and are easier to read. Choosing the right pages to build in the first place also helps; see our list of essential website pages for a small business.
Shops need extra care, because catalogue pages carry many images. Our guide to setting up an online store for a small business covers lean product pages in more depth.
Keeping your site fast after launch
Website speed slips gradually. A new homepage video here, an extra plugin there, a batch of uncompressed photos for a sale, and within a year the site is twice as slow. A short monthly routine prevents this.
- Run your three-page test and compare it with last month.
- Check the size of any new images before they go live.
- Remove expired offers, old banners and unused add-ons.
- Update your theme and plugins, which also closes security holes; see our guide to website security for small business.
- Open the site on a phone and confirm it still feels quick to scroll and tap.
Speed and mobile design go hand in hand, since most visitors arrive on phones. Pair this routine with the layout checks in our guide to building a mobile friendly website. With a lean page, sized images and a reliable host, good website speed becomes something you maintain in minutes rather than a problem you fight every year. If you would rather not handle the tuning yourself, ADigitalMotive compresses images and keeps pages lean automatically when you update your site.
Frequently asked questions
Why does my site score well on desktop but badly on mobile in PageSpeed Insights?
The mobile test simulates a mid-range phone on a slower network, so the same page has less processing power and bandwidth to work with. Large images and heavy scripts hurt far more under those conditions. Treat the mobile score as the one that matters, because it is closer to what most local customers experience when they open your link from a message or search result.
Is a PageSpeed score of 100 necessary for good rankings?
No. The score is a lab estimate that helps you find problems; it is not a ranking number in itself. Google describes page experience as one of many signals, and helpful, relevant content matters more. Aim for passing Core Web Vitals in field data and a page that feels quick on a normal phone. Chasing the last few points rarely brings visible benefits.
How often should a small business re-check its page speed?
Check once a month and after any large change, such as a new theme, a new plugin, a homepage video or a batch of new product photos. Speed tends to slip slowly as content is added, so a regular habit catches problems early. Keep a simple note of each result so you can see whether the trend is going up or down.
Will a faster hosting plan fix a slow website on its own?
Only if the server is the bottleneck. If your pages carry several megabytes of photos or a dozen third-party scripts, better hosting improves the first response but the phone still has to download and process everything. Fix image sizes and remove unneeded add-ons first, then upgrade hosting if the server response time is still slow in test results.
Does lazy loading images help speed or hurt it?
It helps when used on images further down the page, because the browser skips them until the visitor scrolls near them. It hurts when applied to the main image at the top, because that image is then delayed and the largest content appears later. Load the top image normally and lazy-load the rest, such as gallery photos and footer logos.
Written and reviewed by the ADigitalMotive team for owners of small businesses. General guidance only, not legal, tax or financial advice for your situation.
Keep reading
A practical guide to the pages, speed, mobile layout, trust signals, accessibility and upkeep every small business website needs to bring in customers.
11 min read · 18 September 2026Pick a business domain name customers remember, choose the right extension, understand DNS records and SSL, and avoid losing your address at renewal.
8 min read · 13 June 2026A practical guide to making a mobile friendly website: layouts that reflow, readable text, thumb-sized buttons, quick forms and the tests that catch problems.
8 min read · 15 August 2026