A web developer looks at your site on their phone, frowns at the loading bar and tells you the slowness is costing you customers. They quote a figure from an article: so many percent of visitors gone for every second of delay. You run a small business, not a laboratory, and you would like to know whether any of that applies to you before you spend money on it.
So, does website speed affect conversions, and if it does, how much of your problem is it? The honest answer is yes, it can, but nobody can tell you in advance how many sales a slow page is costing you. What you can do is understand how slowness turns into lost customers, find the pages where it hurts most, and measure the effect on your own site instead of trusting a number from someone else’s.
Why nobody can give you a percentage
You will find plenty of articles claiming that every extra second costs a fixed share of sales. That is probably where your developer’s figure came from. Treat it with suspicion. Even where a large company once measured something on its own site, that result belongs to that site, its customers, its products and the year it was measured. It does not transfer to a dental clinic in Pune or a furniture shop in Leeds.
What does transfer is the mechanism. A visitor who arrives wanting something has a limited amount of patience, and every moment spent looking at a blank or half-built page uses some of it up. Some people wait. Some go back and tap the next result. How many leave depends on how much they want what you sell, whether they can get it elsewhere, what device and connection they are on, and how bad the delay really is. That is why the useful question is not “how much do slow sites lose” but “where on my site are people giving up, and is speed the reason?”
How a slow site actually loses customers
It helps to picture the specific moments where a delay turns into a lost enquiry, because each one has a different fix.
Before the page appears at all
The most expensive loss is the visitor who never sees your page. They clicked a search result or an ad, watched a white screen for a few seconds and went back. In your analytics they may not even register, because the tracking script had not loaded when they left. You only see the effect indirectly, as clicks in Google Ads or Search Console that do not match the visits you recorded.
When the page looks ready but is not
The next loss is quieter. The page appears, the visitor taps a menu or a “Book now” button, and nothing happens because the browser is still busy running scripts. They tap again. Sometimes the second tap lands on something else because the layout jumped. People rarely describe this as slowness. They describe the site as broken or untrustworthy, and they leave with a worse opinion of the business than if the page had simply loaded late.
Inside a form or checkout
By the time someone is filling in a form or paying, they have decided they want something. Delays here feel different: a spinner after “Submit”, a checkout step that takes a long time to show shipping options, a payment page that hangs. Some people wait it out. Others start to worry that they have been charged twice, or that the shop is not reliable, and abandon. Checkout delays on WooCommerce have their own causes, covered in why a WooCommerce checkout page loads slowly.
On the next visit
Finally, there is the customer who did buy but remembers the site as a chore. Next time they need something similar, a competitor’s quicker site gets the order. You cannot measure this one directly, but it is real, and it is one reason speed work tends to pay back slowly rather than overnight.
Where speed matters most for sales and enquiries
Not every page deserves the same attention. If you are short of time or budget, these are the places where you are most likely to find a slow website losing customers.
- Mobile visits. Phones have slower processors than laptops, and mobile connections drop and recover. A page that feels fine on office broadband can be painful on a mid-range phone on a train. For many small businesses most visitors are on phones, so this is usually where the gap between “fine for me” and “slow for customers” lives.
- Pages that receive paid traffic. Every visitor who leaves before the page loads is a click you paid for. Ad visitors also tend to be less committed than someone who searched your business name. The specific problems here are in making Google Ads landing pages load quickly.
- Checkout, cart and booking steps. These pages are usually not cached, because they show personal information, so they are often the slowest pages on a store, exactly where you can least afford it.
- The first page a new visitor lands on. That might be your homepage, but often it is a blog post or a product page that ranks in search. Look at which pages people actually enter through, not which page you think of as the front door.
- Visitors on weak connections. If your customers include people on patchy mobile data, a heavy page is not just slow for them, it may never finish. Designing for them is its own subject: building a site that works on slow connections.
Speed tends to matter less where the visitor is already committed: an existing client logging in to download an invoice, or a supplier checking your address. Those people will wait. It still makes sense to fix them eventually, just not first.
Does website speed affect conversions here, or is it something else?
A slow site is an easy thing to blame because it is visible. Before spending money on it, rule out the other common reasons enquiries fall:
- The contact form stopped sending email, so enquiries are being made and lost.
- Tracking broke after a site change, so conversions are happening but not being counted.
- An ad campaign changed its targeting or budget.
- Rankings for a key page dropped. Speed is one signal among many in how Google ranks pages, a point covered in whether Core Web Vitals affect SEO.
- Seasonal demand, a new competitor, or a price change.
Send yourself a test enquiry through every form and check it arrives. That one action rules out the most painful explanation, and it takes very little time.
How to measure the effect on your own site
You do not need a data team to get a reasonable answer. You need a few comparisons, made honestly.
1. Find the pages that matter
In your analytics, list the landing pages that bring the most visitors, and separately the pages where conversions happen: the contact page, the cart, the booking form, the thank-you page. If conversions are not set up as events yet, do that first, otherwise you have nothing to compare. Our post on setting up conversion tracking in GA4 walks through it.
2. Compare devices
Split those pages by device category. If desktop visitors convert at a reasonable rate and mobile visitors on the same page barely convert at all, speed is one of the likely reasons, alongside layout problems on small screens. Open the page on an ordinary phone, not the newest one in the office, on mobile data, and watch what a customer sees.
3. Check what real visitors experience
Run your key pages through PageSpeed Insights. The top section, when your site has enough traffic, shows field data from real Chrome users rather than a simulated test. If a page fails on real users, and especially on mobile, you have evidence that customers are waiting, not just a testing tool. The rest of our website speed guide explains how those reports fit together.
4. Make one change and compare periods
The cleanest test available to a small business is a before-and-after. Record conversion rate, bounce or engagement rate, and the speed measurements for your key pages over a few weeks. Make the speed improvement. Then compare a similar period afterwards, keeping in mind anything else that changed: ad spend, season, prices. It will never be a perfect experiment, but if mobile conversions on a page rise after that page became faster, and nothing else changed much, that is a useful result for your business.
5. Watch for clicks that never become visits
Compare the clicks reported by Google Ads or Search Console with the sessions your analytics records for the same pages and dates. Some gap is normal, because tracking is blocked or declined by some visitors. A gap that grows on mobile, or that is much larger on one slow page than on others, often means people are leaving before the page loads.
What to fix first if sales are the goal
If the measurements above point at speed, work in this order rather than trying to improve every page at once.
- The money pages on mobile. The landing pages that receive ads, the product or service pages that rank, and the checkout or booking flow.
- Whatever blocks the first view. Usually an oversized hero image, a slider, a heavy page builder layout or slow server response.
- Whatever makes taps feel ignored. Often chat widgets, tracking tags and plugin scripts that load on every page.
- Form and checkout delays. These need careful testing, because a speed change that breaks a payment step costs more than it saves.
Before touching anything, write down where you started. A short, structured review, like the one set out in what a speed audit should include, gives you a baseline and a ranked list, so you can tell later whether the work paid off.
Frequently asked questions
How slow is too slow for a small business website?
There is no single cut-off that applies to every business. A useful reference is Google’s Core Web Vitals: a largest contentful paint of 2.5 seconds or less, measured across at least three quarters of real page loads, counts as good. If your key pages are well outside that on mobile, customers are probably noticing the wait.
Will a faster website automatically bring more enquiries?
No. Speed removes a reason for people to leave, but it does not create demand. If the offer, price or page content is not persuading people, a faster page will show them the same thing sooner. Treat speed as one fix among several and measure what changes afterwards.
Can a slow site lose customers even if my analytics shows normal traffic?
Yes. Visitors who leave before the page and its tracking script load are often not recorded at all, so traffic can look normal while some people never see the page. Comparing ad or search clicks with recorded sessions for the same pages is one way to spot this.
Should I speed up the whole site or just a few pages?
Start with the pages that bring in customers: ad landing pages, top entry pages from search, and the checkout or enquiry path. Many fixes, such as caching, image handling and removing unused scripts, help every page anyway, but checking results on the pages that earn money keeps the work focused.
How long after speeding up a site will I see a change in sales?
Speed tests show improvement immediately, but the effect on sales needs enough visits to judge. A busy store may see a pattern within a few weeks; a site with a handful of enquiries a month may need longer. Compare similar periods and note anything else that changed.
Forms checked, tracking working, and the evidence still pointing at speed? Then it is worth a proper look. Our website speed optimisation service measures the pages that bring in customers before anything changes and again afterwards, so you can set the two sets of numbers against your own conversion figures.
All guides in this section
- Landing Page Speed for Google Ads: What to Fix First
- Website Speed Audit Checklist: What a Real Audit Covers
- Should I Hire Someone to Speed Up My Website?
- How to Keep a Website Fast After It Has Been Optimised
- Is AMP Still Worth It? A Plain Answer for Small Sites
- Website Performance Budget: Limits That Keep Pages Fast
- Building a Website for Slow Internet Connections
- Shopify Store Slow? What You Control and What You Do Not
- Wix Website Slow? Fixes for Wix and Squarespace Sites
- Website Speed Optimization Cost: What Drives the Price
Next in this series: Landing Page Speed for Google Ads: What to Fix First
