Is your website slow on mobile?You’re losing customers before it even loads
The most common reasons a website is slow, what Google actually measures, and what I do so my pages load in under a second, even on slow 4G.
In this article· 5 sections
You open your website on your phone, somewhere with an average signal. A white screen, then a logo, then the text jumps around as photos load. Three, four, five seconds. Your customer doesn’t wait that long.
According to Google research (2016), more than half of mobile visits are abandoned when a page takes longer than three seconds to load. And speed doesn’t just affect visitors; it affects your Google ranking too.
What Google actually measures
Google rates the experience on every page with three metrics, the Core Web Vitals:
| Metric | What it means in plain words | Good value |
|---|---|---|
| LCP | How fast the main content appears | 2.5 s or less |
| CLS | How much the page jumps around while loading | 0.1 or less |
| INP | How quickly it responds when you tap something | 200 ms or less |
They are one of Google’s ranking signals: if two pages have similar content, the faster one has an edge.
Where the seconds go
When I review a slow website, I almost always find some of these:
- Huge photos. A 5 MB photo straight from the camera, shown 400 pixels wide, makes the visitor download ten times more data than needed.
- Page builders and plugins. Every plugin brings its own CSS and JavaScript and loads them on every page, even where they aren’t used.
- Fonts and stylesheets that block rendering, because they must download before the browser shows anything at all.
- Third-party scripts: chat widgets, trackers, pop-ups, sliders. Each one is “only a few KB”; together they cost seconds.
- Cheap hosting far from the visitor. A server on another continent adds delay to every single request.
Speed is designed in from the start
You can’t bolt it on at the end. This is what I do instead:
- Where possible, pages are built ahead of time as ready-made HTML, so the browser receives content immediately instead of assembling it.
- Hosting is at the edge, on Cloudflare’s network, which serves the page from the location nearest to the visitor.
- Every image exists in sizes for phones and desktops, in a modern format (WebP), and loads only when it’s about to scroll into view.
- Fonts carry only the characters and weights that are actually needed, hosted on the same server as the site.
- JavaScript is kept to a minimum. Animations are done mostly in CSS, which the browser runs far more efficiently.
How fast this site loads
On a simulated slow 4G connection with a four-times-slower processor, this website shows its main content in 0.93 seconds (LCP), with a CLS of 0.02. Google’s target is 2.5 seconds. The same page scores a perfect 100 on Lighthouse for accessibility, best practices and SEO.
Time until the main content appears
- This website, on slow 4G0.93 s
- Google’s target for a “good” LCP2.5 s
- Where more than half of mobile visits are abandoned3 s
How to check your own site
Open Google’s PageSpeed Insights, enter your page’s address and look at the “Mobile” tab. If LCP is above 2.5 seconds or you see a lot of red, you’re losing visitors and Google rankings.
If you’d rather I looked at it, I’ll review your website for free (speed, mobile layout and Google visibility) and tell you plainly what’s worth fixing.
Found it useful? Share it
Keep reading
- AI wrote your app. Do you know what it forgot to tell you?I checked 105 public AI-built apps and the code mostly looked fine. The real risk is what doesn’t show: six things AI won’t tell you before you launch.
- 7 mistakes that drive customers away from your website (I see number 2 almost everywhere)Your website gets visits, but the phone doesn’t ring? The 7 mistakes I see most often on small business websites, and how to fix each one.