Why Your Website's Speed Is Costing You Customers

Your website has about three seconds. That is roughly how long a typical visitor on a phone waits before deciding whether to stay or hit the back button. If your homepage takes five, six, eight seconds to become usable, a chunk of your potential customers never see your prices, your portfolio, or your contact form. They just leave — and most of them go straight to a competitor.

This is not a technical vanity metric. It is a leak in your sales funnel, and it is measurable.

What slow actually costs

Google's own research found that as mobile load time goes from 1 second to 3 seconds, the probability of a visitor bouncing increases by around 32%. From 1 to 5 seconds, it roughly doubles. Independent studies from retailers point the same direction: every additional second of load time typically cuts conversions by measurable single-digit percentages.

Run the numbers on your own business. Say your site gets 1,000 visits a month and converts 3% of them into enquiries — 30 leads. If a slow site is silently costing you even a fifth of those visitors before the page renders, that is 6 leads a month you never knew existed. Over a year, that is 72 conversations you never had.

Speed also affects how many visitors you get in the first place. Google uses page experience signals — including the Core Web Vitals below — as a ranking factor. A slow site does not just convert worse; it gets found less.

Core Web Vitals, in business terms

Google measures three things on real users' devices. You do not need to memorise the acronyms, but here is what each one means for your customer:

Metric	What Google measures	What your customer experiences	Good
LCP (Largest Contentful Paint)	Time until the main content is visible	"Is this site even loading?"	Under 2.5 s
INP (Interaction to Next Paint)	Delay when they tap or click	"I clicked the button and nothing happened"	Under 200 ms
CLS (Cumulative Layout Shift)	How much the page jumps around	"The page moved and I tapped the wrong thing"	Under 0.1

If any of these is in the red, real people are having a bad experience on your site right now — and Google knows it, because it collects this data from actual Chrome users visiting your pages.

The mid-range phone reality

Here is the part most business owners miss: your site probably feels fine to you. You test it on a recent laptop, on office Wi-Fi, with the site already cached in your browser.

Your customers are mostly on phones — in many markets, 60–70% of traffic — and most of those phones are not this year's flagship. A €200 mid-range Android has a fraction of the processing power of the device you test on. A page that "feels instant" on your machine can take 8+ seconds to become interactive on the median customer's phone over 4G.

This is why lab tests simulate a mid-range phone on a throttled connection. It looks pessimistic. It is actually realistic.

The usual culprits

In our experience auditing small-business sites, slowness almost always comes from the same short list:

• Page-builder bloat. Drag-and-drop builders and heavy multi-purpose themes ship hundreds of kilobytes of CSS and JavaScript for features you never use. The page loads the whole toolbox to show one paragraph.
• Unoptimized images. A 4 MB photo straight from a phone camera, displayed at 400 pixels wide. One hero image can weigh more than the rest of the site combined. Modern formats (WebP, AVIF) plus correct sizing routinely cut image weight by 70–90%.
• Tag soup. Analytics, chat widget, heatmaps, a pixel for every ad platform, a pop-up tool — each one "just a small script". Ten small scripts later, the browser is doing more work for third parties than for your content.
• Plugin stacking. Twenty plugins, each loading its own assets on every page, whether needed or not.
• Cheap hosting. Shared servers that take over a second just to send the first byte, before anything else even starts.

None of these is exotic. All of them are fixable — some in an afternoon, some by rebuilding on a lighter foundation.

Check your own site in 5 minutes

You do not need a developer to get a diagnosis. Do this now:

1. Go to pagespeed.web.dev (Google's free PageSpeed Insights).
2. Enter your homepage URL and run the test.
3. Look at the Mobile tab first — that is where most of your visitors are.
4. Check the top section, "Discover what your real users are experiencing". If your site has enough traffic, this shows field data from actual visitors. Green means fine; orange or red means real people are struggling.
5. Below that, note the Performance score (0–100) from the lab test, and skim the "Opportunities" list — it names the biggest offenders in plain language ("Properly size images", "Reduce unused JavaScript").
6. Repeat for your most important page — the one where customers decide to contact or buy.

Rough interpretation: 90+ is good, 50–89 needs work, under 50 is costing you money. Test a competitor while you are at it. If they score 85 and you score 40, that gap shows up in Google rankings and in who wins the customer.

What good looks like

Good scores are not luck; they are an engineering choice made at build time. When we build sites at Feitura, we measure them with the same public tool anyone can use, and our own sites and client builds score 90+ on PageSpeed's mobile test — because they are built without page-builder bloat in the first place: only the code each page needs, images served in modern formats at the right size, and third-party scripts loaded only where they earn their keep.

That is the honest takeaway: a fast site is mostly the result of not adding the things that make sites slow. Retrofitting speed onto a bloated build is possible but laborious; building light from day one is cheaper.

Your action checklist

• Run PageSpeed Insights on your homepage and your key conversion page (mobile tab)
• Note your Performance score and whether Core Web Vitals pass
• Compress and resize your five heaviest images (the "Opportunities" list identifies them)
• List every third-party script on your site; remove any you cannot justify
• If you use a page builder, ask what your score would be without it
• Re-test after each change — improvements are measurable the same day
• If your score sits under 50 after the quick wins, the foundation is the problem, not the decoration

Speed is one of the few marketing investments where the result is a number you can verify yourself, before and after, for free.

If your site scored below where it should and you want a build that measurably passes Core Web Vitals, request a free estimate — we respond with concrete numbers, not a sales call.