Slow on mobile
Your site is fast on the machine you own and slow on the ones your customers hold.
The desktop-fast, mobile-slow gap isn't a paradox — it's arithmetic: mid-range phones have a fraction of your desktop's power, cellular adds latency wifi doesn't, and the same page weight lands very differently. Since your visitors are mostly the phone side, fix for them first.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
Three multipliers separate the experiences. Hardware: the median visitor's phone executes JavaScript several times slower than a desktop — the builder scripts your laptop shrugs off monopolize a phone's main thread for seconds. Network: cellular latency taxes every request, so request-heavy pages suffer disproportionately. And rendering: massive desktop images shipped to phones burn both bandwidth and decode time.
This is also precisely how Google sees you — mobile-first indexing means the phone experience is the ranked experience, and the Core Web Vitals field data doing the judging comes largely from those mid-range phones on cellular. The office-desktop speediness is real, and it's the minority report.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
JavaScript weight meeting phone CPUs
Builders, sliders, and tracker stacks that desktops absorb — executing for whole seconds on the devices most visitors hold. The INP killer.
Desktop-sized media on cellular
Images sized for large screens shipped to small ones — bandwidth and decode time burned on pixels nobody sees.
Request-count latency tax
Dozens of scripts, fonts, and third-party calls — each paying cellular's round-trip toll. Fine on wifi, punishing on LTE.
Mobile-hostile third parties
Chat widgets, embeds, and ad scripts whose phone builds are afterthoughts — heavy where the audience is biggest.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Test your site on a real phone, on cellular
Wifi off, your actual site, a stopwatch honestly observed. This is what customers experience, and the desktop comparison makes the gap undeniable.
- 2
Run PageSpeed and read the MOBILE tab
The tool defaults to showing mobile first for a reason. Compare the two scores — the gap size tells you how phone-specific your problem is.
- 3
Note when the slowness bites
Slow first paint = media and server. Loads-then-janky taps = JavaScript and the main thread. The feel of the slowness sorts the fix list.
Stop and call when…
- The mobile-desktop gap is wide — that's a JavaScript economy problem needing surgical deferral
- Field vitals fail on mobile while lab passes — real-user forensics territory
- Your traffic is majority phone (check analytics — it probably is) and every slow second is majority-of-visitors slow
From there it’s our job: same-day look, flat quote, and the $679 flat repair covers most cases of exactly this.
Site Speed Tune-Up — buy it now, skip the hunt.
Images, scripts, and caching tuned — measurably faster inside 48 hours of starting.
Covers one site: image optimization, script cleanup, caching configuration, and a before/after PageSpeed report. Platform-level rebuilds quoted separately if the site needs more.
Questions we hear a lot.
Why is the gap so much bigger than my phone suggests?
Because your phone is probably newer than your median visitor's — developers and owners carry flagship devices; customers carry three-year-old mid-rangers. Google's field data aggregates the real distribution, which is why testing on (or throttling to) modest hardware is part of an honest diagnosis.
Is this the same as the $679 speed tune-up?
Same price, phone-first emphasis: the work prioritizes what mobile feels — JavaScript deferral, media sizing for real screens, request-count reduction — and verifies on real devices and cellular, not just the lab. If your gap is desktop-fine/mobile-failing, this is the right door in.
Will fixing mobile speed help rankings?
It's the version of speed Google actually measures — mobile-first indexing plus phone-heavy field data means mobile speed IS your speed, as far as ranking signals go. The conversion effect is even more direct: most of your visitors feel every improvement immediately.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Fix it for the hands that actually hold it.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.