Mobile speed versus desktop speed: why the phone score is the one to fix
Your mobile score is lower because speed tests simulate a mid range phone on a slow mobile connection, and real phones have less processing power than office computers. Fix mobile first: Google uses the mobile version of your pages for indexing and ranking, and it scores phones and computers separately.
Why the mobile number is always worse
When PageSpeed Insights runs its lab test on the Mobile tab, Lighthouse slows things down on purpose. By default it simulates a network with 150 milliseconds of latency and about 1.6 megabits per second of download speed, and it slows the processor four times. Its documentation describes that network as roughly the bottom quarter of 4G connections and the top quarter of 3G.
That is not a trick. It is a fair picture of a patient on an older phone in a hospital parking garage, or anywhere the signal is weak. Your office desktop on a fast connection hides all of it.
Processor speed matters as much as the network. Phones take longer to run the same code, which is why chat widgets and animation heavy templates that feel fine on a laptop can make a phone sluggish.
Google looks at the mobile version first
Google uses mobile first indexing. In its own words, it uses the mobile version of a site's content, crawled with its smartphone crawler, for indexing and ranking. Your desktop layout is not the version that counts.
Two practical consequences follow. First, the mobile page has to contain the same content as the desktop page. If your mobile layout drops the insurance list, the provider bios or the condition details to save space, Google may not see them. Second, a mobile page that is slow or broken is the version Google evaluates.
Core Web Vitals are also reported separately for phones and computers, both in PageSpeed Insights and in Search Console. A site can pass on desktop and fail on mobile, so a good desktop result tells you little about your patients on phones.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
What makes practice sites slow on phones
The same problems show up on practice sites again and again, and they hurt phones far more than computers:
- Hero videos and sliders that load several large files before the patient sees anything useful
- Photos sized for a desktop monitor and shrunk by the browser on a small screen, so the phone downloads pixels it never shows
- Chat, review and booking widgets that all start running the moment the page opens
- Pop ups and banners that load late and push content down, or cover the screen
- Several web fonts, each one a separate download
None of these require a redesign to fix. Our guides to images and third party scripts walk through each one.
Pop ups hurt more on small screens
A promotional pop up on a desktop covers part of the page. On a phone it covers all of it, and the patient has to find a tiny close button before they can see your phone number. Google's guidance on interstitials says not to obscure the entire page, and a pop up that appears after a delay can also add to layout shift.
If you need an announcement, such as a new location, a flu shot clinic or holiday hours, use a slim banner that is part of the page from the start rather than an overlay that slides in later. Legally required notices are treated differently, but keep them small and let the patient reach your content. More in pop ups that cover the page on mobile.
Do not fix mobile by hiding content
A tempting shortcut is to strip the mobile version: drop sections, hide the provider grid, remove the FAQ. It may improve the score, but because Google indexes the mobile version, content you remove from mobile may stop counting in search. Patients lose it too, and they are the ones looking for your insurance list at 9 pm.
Make the mobile page lighter instead of shorter. Serve smaller image files to small screens, delay widgets until they are needed, and cut decorative effects. The words, headings and links can stay. Text is cheap to load. Images, video and scripts are what make phones slow.
A mobile first review in fifteen minutes
- Open PageSpeed Insights, keep the Mobile tab selected, and test your homepage and your busiest service page.
- Note LCP, INP and CLS from real users if they are shown, and the lab results below them.
- Switch to the Desktop tab and compare. A big gap usually points to images or scripts.
- Open the same pages on your own phone over cellular data and tap through to booking.
- Put the mobile and desktop versions side by side and confirm the same content appears on both.
- Send your vendor the mobile numbers, the size of the gap, and anything missing on mobile.
Fixing the mobile problems usually improves desktop along the way. The full testing routine is in how to test your website's speed.
Checklist
- You review mobile results before desktop
- Mobile pages contain the same text, headings and links as desktop pages
- Hero images are served at phone size on phones
- No pop up covers the whole screen on a phone
- Widgets do not all start loading the moment the page opens
- You have tapped through to booking on your own phone over cellular data
Frequently asked
Why does my site feel fast on my phone but score poorly?
Your phone may be newer than many of your patients' phones, your connection may be strong, and parts of the site may already be cached from earlier visits. The mobile lab test removes all three advantages on purpose. If you have real user data, trust it, because it reflects your actual patients.
Do I need a separate mobile website?
No. A responsive site, one set of pages that adapts to the screen, keeps content identical across devices, which matters because Google indexes the mobile version. Separate mobile sites at a different address are an older approach that doubles the work of keeping both versions in step.
Is a desktop score worth tracking at all?
Yes, especially if many patients, caregivers or referring offices view your site on computers. Desktop is measured separately and can fail on its own, for example from very large images. Just do not let a good desktop number reassure you about mobile.
What is the single biggest mobile fix for most practice sites?
There is no universal answer, so check what your own test reports as the Largest Contentful Paint element. If it is a large hero photo or a slider, replacing it with one properly sized image is often the quickest meaningful improvement.
Sources
- Lighthouse throttling documentation, GoogleChrome Lighthouse (GitHub)
- Mobile-first indexing best practices, Google Search Central
- Web Vitals, web.dev (Google)
- About PageSpeed Insights, Google for Developers
- Interstitials and dialogs, Google Search Central
- Why lab and field data can be different (and what to do about it), web.dev (Google)
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.