Load time is the most invisible defect a website can have. The owner opens their own site on an office PC with fast internet and a warm browser cache, and everything feels snappy. The prospective customer opens it on a phone in the subway, waits, waits a moment longer, and taps the next search result. Nobody sees that abandonment; it never shows up as a complaint. It still costs enquiries, every day.

What slowness actually costs

Three mechanisms feed each other. First, abandonment: someone who clicks a search result or an ad and stares at a white screen has little reason to wait, because the competition is one tap away. Google put numbers on this together with SOASTA (2017): as mobile load time grows from one second to three, the probability of a bounce rises by 32 percent; at five seconds it is already 90 percent. Second, rankings: Google measures how fast and stable pages load for real users via the Core Web Vitals and factors that into its evaluation. A slow site therefore gets fewer visitors, and loses a larger share of the ones it gets.

Third, advertising costs: if you run Google Ads, you pay per click — including the clicks that bounce before the page renders. A slow landing page burns ad budget in complete silence.

Increase in bounce probability (mobile)

1 → 3 seconds+32%

1 → 5 seconds+90%

1 → 6 seconds+106%

1 → 10 seconds+123%

Source: Google/SOASTA, 2017

Where the seconds actually go

In the projects we have taken over, it is almost always the same culprits, in roughly this order:

Images: the multi-megabyte phone photo dropped into the header at full resolution is the classic
Third-party scripts: chat widgets, maps, tracking, social media embeds — each one looks harmless, together they dominate the load time
Bloated themes and plugins: site-builder and WordPress themes often ship the code for a hundred features of which the site uses five
Cheap hosting: if the server itself takes a second before it even responds, no optimization downstream can make up for it

Measure honestly instead of guessing

Gut feeling on your own machine is not a measurement. Use Google’s PageSpeed Insights: enter the URL and look at the mobile result, not just desktop. Mind the distinction in the report: at the top, if available, sits field data from real Chrome users over recent weeks; below it, a lab test. The field data is the truth; the lab test is the diagnostic aid.

And run the simplest test there is: open your website on a phone over the mobile network, no Wi-Fi, in a private browser window. That is what your new customers experience.

What can be fixed at reasonable cost

The good news: the biggest brakes are often the cheapest repairs. Converting images to modern formats like WebP and resizing them to the dimensions actually displayed cuts the page weight in half on many sites. Next, go through the third-party scripts and remove everything nobody needs anymore — the forgotten tracking pixel from a campaign two years ago is a common find.

A hosting move costs effort once and pays off permanently. Only after these basics are done do the finer measures become worthwhile: lazy loading, font optimization, cleaning up CSS and JavaScript. That even small steps pay is what Deloitte’s study “Milliseconds Make Millions” (2020) showed across more than 30 million user sessions: 0.1 seconds less mobile load time lifted retail conversion rates by 8.4 percent and average order value by 9.2 percent.

The uncomfortable truth: sometimes the foundation is the problem

Not every slow website can be made fast. If the cause is an overloaded theme with twenty plugins, optimization becomes a renovation with the tenants still living inside: possible, but laborious, and the result stays a compromise. Past a certain point, rebuilding on a lean technical foundation is cheaper than a third round of optimization. That is not pleasant news, but it is the kind you want to hear before commissioning an optimization, not after.

Performance is a construction decision

The most reliable way to get a fast website is to build it fast from the start: lean code instead of a theme with a thousand options, images that are automatically served at the right size, as few third-party scripts as possible. We build our websites statically generated with Next.js precisely because that approach treats load time as the starting condition, not as an afterthought. Whatever provider you talk to, ask before the project how they guarantee load time — and how you can verify it after launch.