On your office laptop the site opens in a blink. On your phone, standing in a shop or sitting in a cab, it hangs on a white screen, then lurches into place, and the menu ignores your first two taps. Your developer says it is fast because they tested it on their desktop. Your customers, most of whom arrive on phones, would probably disagree.
It is common to see a website slow on mobile but fast on desktop, and the difference is rarely imaginary. Phones and laptops really do load the same page differently, and some sites quietly send phones more work than they send desktops. Once you know where the difference comes from, you can test for it instead of arguing about it.
A phone is not a small laptop
The obvious explanation is the connection, and it matters. But the bigger difference is often the processor.
Processing power. A modern page is not just downloaded; it is run. The browser has to read the HTML, work out the styles, and execute every script the theme and plugins include. A mid-range phone does this work far more slowly than a laptop. A script that takes a fraction of a second on your desktop can keep a cheaper phone busy for much longer, and while it is busy it cannot respond to taps or scrolling.
The network. Mobile data varies from moment to moment. Even when the download speed looks fine, each request can take longer to start, because mobile networks usually add more delay per round trip than office broadband or fibre. A page that needs a hundred separate files suffers more on mobile than a page that needs twenty, even if the total size is the same.
Heat and battery. Phones slow themselves down when they are warm or in power-saving mode. This is one reason the same phone can give you different results an hour apart.
None of this is a fault in your site. It is the environment your site has to work in, and the site needs to be built for it.
Things some sites send only to phones
Sometimes the site itself treats phones differently, and not in a helpful way. These are the ones we look for first.
Content hidden, not removed
Page builders make it easy to build a desktop version of a section and a separate mobile version, then hide one on each device. Hiding usually means the browser still downloads both versions and simply does not display one of them. The phone ends up fetching the images and scripts for a desktop layout it never shows.
Oversized images
A phone screen is narrow, so it should get narrower images. If the theme or builder does not provide smaller versions, or the images were set as backgrounds through custom code, the phone downloads the same large file the desktop gets. The post on serving smaller images to smaller screens explains how this is meant to work and what breaks it.
Mobile-only extras
Popups that only appear on small screens, “download our app” banners, sticky call or WhatsApp buttons, a separate mobile menu plugin, a mobile slider that replaces the desktop hero. Each adds files and code, and some load from outside servers.
Ads and tracking that behave differently
Ad networks and some marketing tools serve different content to mobile visitors. If the site carries ads, a phone may be loading quite a different set of scripts from the one you see on desktop.
Why your desktop test gives the wrong picture
When you check the site on your laptop, several things are working in your favour at once. You are on a fast, steady connection. Your processor is powerful. You have probably visited the site many times, so your browser already has its files saved. And if you are logged in to WordPress, you may be seeing a different version altogether.
Chrome’s device toolbar, the button that lets you view the page at phone width, helps with layout but, on its own, changes very little about speed. It shrinks the screen, not the processor. Unless you also switch on network and CPU throttling in DevTools, treat it as a layout check rather than a speed test.
Speed tools are better, because they simulate a slower device and connection. PageSpeed Insights, for example, runs its mobile test on a simulated mid-range phone with a throttled connection, which is why its mobile number is almost always worse than its desktop one. That gap is expected. It does not mean the test is broken.
How to test on a real mid-range phone
A simulation is useful, but nothing replaces holding an ordinary phone and watching your own page load. Here is a routine that gives you results you can compare over time.
- Use an ordinary phone. Not the newest flagship. A mid-range Android phone a couple of years old is closer to what many customers carry. If you only own a high-end phone, borrow one.
- Turn off Wi-Fi. Test on mobile data, ideally somewhere with average signal rather than right next to a window.
- Open a private or incognito tab. This means the browser has nothing saved from earlier visits, so you see what a new visitor sees. Make sure you are not logged in to the site.
- Load the page and time three moments. When something first appears, when the main content (the headline and main image) is visible, and when the menu responds to a tap. A stopwatch is fine. So is screen recording, which lets you replay it.
- Repeat three times and note the middle result for each moment.
- Test your important pages, not just the home page: a product or service page, the contact page, the checkout if you have one.
If you want to see exactly what the phone downloaded, you can connect an Android phone to Chrome on a computer by USB and use remote debugging to open developer tools for the phone’s browser. For a closer look at the Network panel itself, including throttling and sorting requests by size, see the post on checking page load in Chrome DevTools.
Reading what you find
Your timings tell you which kind of mobile slowness you have.
- Long blank screen, then the page appears quickly. The wait is at the server or the connection, not the phone. Compare with the desktop test: if desktop also waits, it is a server problem that the phone simply makes more visible.
- Content appears, but the main image is late. Usually image size or loading order. Check whether the phone is getting a desktop-sized image.
- Everything is visible, but taps are ignored. Scripts are keeping the phone busy. This is the classic case of a site that is fine on a laptop and poor on a phone, because the difference in processing power is greatest here.
- The page jumps as it loads. Banners, popups or late images are pushing content around, which is more noticeable on a narrow screen.
If the honest answer is “all of the above”, start with the general triage in why a website is slow and how to tell which part is at fault, then come back to the phone-specific causes.
Website slow on mobile but fast on desktop: what to fix first
The detailed fixes live elsewhere in our complete guide to website speed, but the order of work for a phone problem is fairly consistent.
- Stop sending phones what they never display: duplicate hidden sections, desktop sliders, large background images.
- Make sure every image has smaller versions and the phone is actually receiving them.
- Remove or delay mobile popups, banners and widgets that are not earning their place.
- Cut down the scripts that run on every page, especially from plugins whose features you only use on one page.
- Keep the top of the page simple: a clear headline, one image, and a visible call to action.
Mobile-friendly design is related but not the same thing. A layout can fit a phone screen perfectly and still be slow. Our post on making a website mobile-friendly covers the layout side.
And if your customers often browse on weak or patchy connections, designing for that is its own discipline, covered in building a site that works on slow networks.
Mistakes to avoid
- Judging speed in Chrome’s phone-width view on a desktop with no throttling.
- Testing only on your own top-end phone over office Wi-Fi.
- Hiding heavy sections on mobile and assuming they no longer load.
- Adding a mobile-only popup to “capture leads” without checking what it costs in load time.
- Treating the mobile PageSpeed number as the whole story, rather than also watching the page on a real phone.
Frequently asked questions
Why is my PageSpeed score so much lower on mobile than on desktop?
The mobile test simulates a mid-range phone on a slower, throttled connection, while the desktop test assumes a fast computer and connection. The same page therefore scores lower on mobile. A large gap is normal; what matters is whether the mobile result improves after you make changes.
Do phones get a different cached copy of the page from desktops?
Usually they share one cached copy, which is right for a responsive site. Some caching plugins offer a separate mobile cache, which is only needed when the theme sends phones different HTML. If that setting does not match what your theme does, phones can get the wrong layout or miss the cache, so check the theme before changing it.
Would a separate mobile version of the site be faster?
Rarely worth it today. One responsive site that sends phones lighter images and fewer scripts is easier to maintain and avoids duplicate content. A separate mobile site doubles the work of every update and tends to fall out of step with the main one.
Does my phone’s browser or age make a difference to the test?
Yes. Older and cheaper phones have slower processors, so script-heavy pages feel worse on them. Browser extensions, data-saver modes and battery saving also change results. That is why you should note which phone and connection you used, and repeat tests with the same setup.
Sites that load slowly on phones are exactly who our speed optimisation work is meant for. It starts with an audit, works through a prioritised fix list with your approval, and finishes with a re-test and a before-and-after comparison you can check on your own phone.
Next in this series: Website Slow on First Load but Quick After That?
