Amir runs an online furniture store in Manchester. His products are good. His prices are competitive. His photography is excellent. His Google Ads campaign sends 400 to 500 visitors to his site every week.
His mobile conversion rate is 0.4 percent.
His desktop conversion rate is 2.8 percent.
He had noticed the gap for months but assumed it was just how mobile shopping worked. People browse on phones but buy on laptops. That is just consumer behaviour.
He was wrong. It was not consumer behaviour. It was load time.
His site took 6.8 seconds to load on a mobile connection. His desktop version loaded in 1.9 seconds. He had unknowingly built a business that worked on one device and failed on another, at a time when 67 percent of his paid traffic was arriving on phones.
What 6.8 Seconds Actually Costs You
The relationship between page load time and conversion rate is one of the most extensively studied and consistently proven findings in ecommerce research. The numbers are not directionally interesting. They are precise and they are severe.
A site loading in 1 second converts at a rate roughly 3x higher than a site loading in 5 seconds. Every additional second above 2 seconds on mobile reduces your conversion probability by approximately 20 percent. At 6.8 seconds, a meaningful proportion of your visitors have already left before the page has finished rendering.
Not because they do not want your product. Not because your price is wrong. Because they clicked, they waited, their thumb moved to the back button, and they bought from the next result.
This is happening silently. It does not show up in your analytics as a problem with your product or your price. It shows up as a bounce, attributed to nothing specific, absorbed into a general sense that mobile just does not convert as well.
For Amir, running the maths on what his load time gap was costing him: 300 mobile visitors per week at a 0.4 percent conversion rate versus a potential 2.0 percent conversion rate at optimal load time. The difference is 1.2 booked orders per week versus 6. At an average order value of £480, that is a difference of £2,304 per week in revenue from the same traffic. £9,200 per month. From a technical problem he did not know he had.
Why Most Business Owners Have No Idea Their Site Is Slow
The reason slow site speed goes undetected for so long is that the business owner almost never experiences their own site the way their customer does.
The business owner tests their site on their work laptop, connected to fast office wifi, with the page already cached in their browser from the last visit. Everything loads instantly. They click through, it feels fine, they move on.
Their customer is on a mid-range Android phone on a 4G connection in a train station. They click an ad, they wait, the page starts rendering, they wait more, something shifts on the page as an image loads and they accidentally click the wrong thing, they close it. That experience bears no resemblance to what the business owner sees when they test it themselves.
The only accurate way to measure your site’s real-world load speed is through external tools that simulate actual user conditions. Google PageSpeed Insights, GTmetrix, and WebPageTest all provide mobile performance data that reflects what your visitors experience rather than what you experience in your own browser.
Run your homepage through Google PageSpeed Insights right now on mobile. If your score is below 50, you have a serious revenue problem. Between 50 and 75, you have a moderate problem. Above 90, you are in a competitive position. Most small business and ecommerce sites score between 20 and 50 on mobile and have never checked.
The Four Things That Make Most Sites Slow and How to Fix Each One
Problem One: Images That Have Never Been Compressed
The single most common cause of slow mobile load times is uncompressed images. A photographer delivers beautiful product shots at 8MB each. They get uploaded directly to the website. The mobile visitor’s phone has to download 40MB of imagery before the page is usable.
Image compression tools like Squoosh, TinyPNG, or the automatic compression built into Shopify and modern WordPress plugins can reduce image file sizes by 60 to 80 percent with no visible quality loss. A 6MB product photo becomes a 900KB file that loads in a fraction of the time.
This single change reduces load time on image-heavy pages by 2 to 4 seconds in most cases. It requires no developer, no code changes, and no technical knowledge. It is the highest-leverage performance improvement available to most small ecommerce stores and it is almost universally unimplemented.
Problem Two: Too Many Third-Party Scripts Loading on Every Page
Every plugin, chat widget, analytics tool, heatmap script, social media pixel, and review badge you have added to your site loads a piece of external code on every page visit. Each one adds load time. Individually they are small. Collectively they add up to seconds.
A typical small business website has between 15 and 30 third-party scripts loading on every page. Many of them are for tools that are rarely used or were installed and forgotten. Each one is making every visitor’s experience slightly slower.
Audit the scripts running on your site using a tool like GTmetrix or ask your developer to run a performance trace. Identify every third-party script and evaluate whether it is actively generating value. Remove the ones that are not. Defer the loading of the ones that are not needed immediately when the page loads. This change alone typically reduces load time by 1 to 2 seconds on sites with many installed plugins.
Problem Three: No Lazy Loading on Images Below the Fold
Lazy loading means images below the visible portion of the page do not load until the user scrolls to them. Without it, every image on your entire page loads simultaneously when someone visits, including images they may never scroll to.
Lazy loading is now built into modern browsers and can be enabled with a single HTML attribute or a single WordPress plugin. It has zero effect on the visual experience and significant effect on the initial load time, particularly on pages with many product images or a long scroll depth.
Problem Four: Hosting That Is Too Slow for Your Traffic Level
Cheap shared hosting works fine for a site getting 50 visitors a day. It does not work for a site getting 500 visitors a day during a sale or ad campaign. When multiple visitors arrive simultaneously, a slow server takes longer to respond to each request. That server response time is added to your load time before the browser has even started rendering anything.
Check your server response time in Google PageSpeed Insights under Time to First Byte. If it is above 600 milliseconds, your hosting is a meaningful contributor to your load problem. A mid-tier managed hosting plan or a move to a faster server typically reduces TTFB by 300 to 500 milliseconds and noticeably improves the start of the loading experience.
What Amir Fixed and What Changed
Amir’s developer compressed all product images, removed six unused third-party scripts, enabled lazy loading, and moved to a faster hosting tier. Total implementation time: one working day.
Before: 6.8 second mobile load time. Mobile conversion rate: 0.4 percent. After: 1.9 second mobile load time. Mobile conversion rate: 1.9 percent.
Same products. Same prices. Same traffic. Same ads. Different load time.
The revenue difference in the first full month after the changes was £8,600. The development cost was £400.
Book your free website performance audit here.
Digiwolves works with ecommerce brands and small businesses across the US and UK. Google Premier Partner certified.
