Insights · Website Speed, Plainly
Mobile Speed Is the Only Speed That Matters
By Russ Gardner Updated
Mobile speed matters most because Google ranks the mobile version of your site and most local customers meet you on a phone. Test it the way they see it: PageSpeed Insights on the Mobile tab, then your own phone over cellular. Aim for the main content on screen within 2.5 seconds.
A site that is only fast on desktop is a slow site.
What Google actually measures
Two facts from Google itself settle the desktop-versus-mobile question.
First, ranking. Google’s mobile-first indexing documentation says: “Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.” If something exists only on your desktop layout, as far as Google is concerned it doesn’t exist.
Second, the speed bar. Google’s Core Web Vitals define a good page as one where:
- LCP (largest contentful paint) happens within 2.5 seconds: the main content is on screen.
- INP (interaction to next paint) is 200 milliseconds or less: a tap gets a visible response.
- CLS (cumulative layout shift) is 0.1 or less: nothing jumps while you read.
Google measures these at the 75th percentile of real page loads, “segmented across mobile and desktop devices.” Your phone visitors get their own score. A fast desktop number can’t carry a slow phone one.
The desktop-on-wifi illusion, in numbers
Almost every owner checks their site the same way: on a laptop, on fast office internet, looking at a copy they have opened a hundred times. It is the most flattering test there is.
Here is how big the gap gets, on this very site. On October 6, 2026, PageSpeed Insights scored the generussdesign.com homepage 99 on desktop and 90 on mobile. The main content painted at 0.6 seconds on desktop and 3.0 seconds on the emulated phone. Same page, same code, five times slower on the phone. That homepage carries a lot of motion work, so it is a hard case, but the pattern holds for almost any site: the phone is where speed problems show up first.
How to test it the way customers see it
- PageSpeed Insights, Mobile tab. Paste your URL into PageSpeed Insights and read the Mobile results first. The lab test loads your page as an emulated Moto G Power, a mid-range Android phone, on a throttled connection. If your site gets enough Chrome traffic, the top section also shows field data from real visitors; most small sites see “no data” there, which is normal.
- Your own phone, cold. Open a private tab so nothing is cached, turn off wifi, and load your homepage on cellular. Count from the tap until you could read the page and tap to call.
- Someone else’s phone. Hand it to a friend with an older phone and watch where they hesitate. If they pinch, zoom, or hunt for the button, that is a speed problem too.
- Your main money page, not just the homepage. The service page or booking page that ads and search send people to deserves the same test.
What mobile-first changes about the work
Once the phone is the real venue, the priorities reorder themselves:
- Images. A photo has to look good on a small screen without shipping a desktop-sized file over cellular. Right-sized, modern formats, and lazy loading for anything below the first screen.
- Scripts. Every chat widget, tracker and slider competes for a slower processor. What feels free on a laptop can stall a mid-range phone for a second or more.
- Layout and taps. The button has to be reachable and the text readable the moment the page settles, with no zooming.
A phone is not just a smaller screen; it is a slower computer on a less reliable connection. When a page is fast under those conditions, it is fast everywhere, which is why building for the phone first is the efficient order, not a limitation.
Check your own device split
Open your analytics and look at mobile versus desktop. For most local service businesses the phone share is large, but don’t take anyone’s word for it, including mine: your own numbers decide where to spend. Then put a dollar figure on what slow costs you with the Slow-Site Cost Calculator.
How fast a site should load lays out the full target, and why is my website slow covers what to change when the phone test comes back slow. The website speed pillar puts mobile speed in context with everything else that turns a visit into a customer.
Measure yours, free
Reading about it is one thing. The Slow-Site Cost Calculator runs this on your actual numbers in about two minutes, free.
Run the Slow-Site Cost Calculator →Quick answers
Why is mobile speed more important than desktop speed? +
Google says it uses the mobile version of a site's content for indexing and ranking, and local customers usually find you on a phone, often on cellular. A page that is fast on your office wifi and slow on a mid-range phone is, for both of them, a slow page.
How fast should my site load on a phone? +
Google's Core Web Vitals call a page good when its largest content shows within 2.5 seconds, it responds to taps within 200 milliseconds, and its layout shift stays at 0.1 or less, measured at the 75th percentile of real visits, separately for mobile and desktop.
How do I test my mobile speed? +
Run your page through PageSpeed Insights and read the Mobile tab, which loads it as an emulated mid-range Android phone. Then open the site on your own phone over cellular in a private tab and time it from the tap to the moment you could read it and tap to call. Do both; each catches what the other misses.
Does designing for mobile speed hurt the desktop experience? +
No. A page built light for a phone on cellular loads even faster on a desktop with a wired connection. Optimizing for the hardest case lifts every case. The reverse is not true: a page tuned only for desktop often falls apart on a mid-range phone.