A Slow Website on Phones Loses Customers Before They See the Price

A prospective customer taps a link to your website from Instagram or WhatsApp. The screen stays white. One second, two seconds, three seconds. Before the price and product photos appear, they're already back in the previous app.

A slow website rarely feels slow to its owner, because the owner opens it on a laptop with fast office internet. Prospective customers open it on a phone, often on an ordinary signal.

How to check it yourself

Open PageSpeed Insights and enter your website's address. There are two kinds of results to tell apart:

• Field data, from real Chrome users over the last 28 days. According to Google's documentation, this only appears if your site has enough visitors. New or low-traffic sites often don't have it yet.
• Lab data, from a single simulated page load on one device and connection. Useful for finding causes, but not the actual visitor experience.

The three main measures, called Core Web Vitals, have "good" thresholds assessed at the 75th percentile of visits:

Google also recommends that site owners achieve good Core Web Vitals, and writes on Search Central that this aligns with what its ranking systems seek to reward. But the main reason is still visitors: those who leave before the page appears will never become customers.

The most common causes

1. Images that are too large. A 5 MB photo straight from the camera shown on a phone screen a few hundred pixels wide.
2. Too many plugins and scripts. Chat widgets, ad pixels, sliders, popups, and analytics, all loaded before the main content.
3. Slow hosting, especially the cheapest plans shared with many other sites.
4. CSS and fonts that hold up rendering, so the browser waits for other files before showing anything.
5. Animations at the top of the page that make the main content appear only after the effect finishes.

An example from this website

The website you're reading was also tuned for phones. There were three changes: the CSS was put directly into the page so the browser doesn't wait for a separate file, the analytics script loads only after the page has finished, and the text and photo at the top appear immediately without a fade-in effect. Tested on a throttled phone profile, the time until the largest content appeared dropped from 2.8 seconds to 1.1 seconds.

Time until the largest content appears (LCP), tested on a throttled phone profile(seconds)

• Before2.8 s
• After1.1 s

None of it was complicated. What it takes is knowing which part holds up rendering, then getting it out of the critical path.

A sensible order of fixes

Here's what I'd suggest, from cheapest and most impactful:

1. Shrink images and convert them to WebP or AVIF, sized for how they appear on screen.
2. Cut plugins and scripts, and delay the ones that aren't needed for the first view, such as chat widgets and analytics.
3. Turn on caching and a CDN if your hosting supports it.
4. Consider moving hosts if the server is still slow after all of the above.
5. Measure again after each change, so you know what actually made a difference.

If the site was built with a very heavy theme or page builder, it's sometimes cheaper to rebuild it cleanly than to keep patching. The trade-offs are in Portfolio Websites Are Cheap Now, But Here's When It's Actually the Right Time to Build One, and an example of building from scratch is the PT Damai Sejahtera Metalindo website case study.

Wrapping up

A website that's slow on phones quietly throws away prospective customers you worked hard to attract through ads, content, or AI answers. Check it yourself in PageSpeed Insights, start with images and scripts, then measure again. Speed isn't an extra feature, it's what gives your offer a chance to be seen.

If your website feels slow on phones and you don't know where to start, tell me your website's address first.