You run your store through PageSpeed Insights, see a comfortable 85-90 on desktop, and figure your Shopify site is in decent shape. Then you check mobile. Suddenly you’re looking at a 35, maybe a 45 if you’re lucky, and a wall of red “opportunities” you didn’t know existed. Nothing on the site changed between the two tests, just the device profile.
This is one of the most common patterns we see raised in the Shopify Community forums: a merchant posts their desktop Lighthouse score as proof the store is “fast,” then asks why mobile conversion and mobile rankings still lag. The honest answer is that desktop and mobile are effectively two different tests, run under two different sets of constraints, and a store can genuinely be fast on one and slow on the other.
This post explains why that gap exists, where it usually comes from on Shopify stores specifically, and what to actually do about it, not just what to feel bad about.
The Short Answer
Your mobile score is lower because Lighthouse’s mobile test simulates a mid-range phone on a throttled connection, not the desktop or laptop you’re testing from. Shopify stores that lean on high-resolution imagery, carousel-heavy homepages, and a stack of third-party apps tend to cope fine on a fast desktop CPU and connection, but the same page can choke on a throttled mobile CPU and a simulated 4G connection. The fix isn’t a different score, it’s addressing the actual weight and blocking behaviour of the page, which shows up worse on mobile because mobile has less headroom to hide it.
How Lighthouse Actually Tests Desktop vs Mobile
If you’re using Google PageSpeed Insights or Lighthouse (the tool behind both PageSpeed Insights and the Performance panel in Chrome DevTools), it’s worth understanding that “mobile” isn’t just a smaller viewport. Two things change under the hood:
CPU throttling. The mobile test profile applies a slowdown multiplier (Lighthouse has used a 4x CPU slowdown in recent versions) to simulate a mid-tier Android device rather than the powerful desktop or MacBook you’re probably testing from. Any JavaScript your theme or apps run, carousel initialisation, app embeds, analytics snippets, review widget rendering, takes proportionally longer to execute on this simulated hardware.
Network throttling. The mobile test also simulates a slower, higher-latency connection roughly comparable to a decent 4G connection, not your office wifi or fibre. Every render-blocking request, CSS, fonts, blocking scripts, costs more time before the browser can start painting the page.
Desktop testing, by contrast, uses a much lighter throttling profile because the assumption is a stronger device on a faster connection. So a Shopify store with a 400KB hero image and six third-party app scripts might look “fine” on desktop simply because desktop has enough CPU and bandwidth to absorb the cost quickly. On mobile, the same page has to do the same amount of work with a fraction of the resources.
This is also why Core Web Vitals data in Google Search Console is reported separately for mobile and desktop, Google treats them as genuinely different experiences, and for most Australian stores, mobile is also where the majority of session volume actually comes from.
Where Shopify Stores Typically Lose Mobile Speed
In our experience running Shopify performance audits, the mobile/desktop gap on Shopify stores usually comes down to a handful of repeat offenders. This pattern shows up especially often on image-heavy fashion and beauty stores, where the homepage and collection pages are doing a lot of visual heavy lifting.
1. Images served at desktop size to mobile viewports
Shopify’s responsive image support (via srcset and the image_url filter) means themes can serve appropriately sized images per breakpoint, but only if the theme and the merchant’s uploaded assets are set up to use it properly. A common issue: a merchant uploads a 2400px-wide hero banner meant for a large desktop screen, and if the section or app block isn’t correctly using responsive srcset markup, that same oversized file gets downloaded on a 390px-wide phone screen, just scaled down by CSS. The browser still has to fetch and decode the full file.
2. Render-blocking apps and scripts
Every app you install that injects a script into theme.liquid or into the head of your pages adds a network request and, often, execution time before the page is interactive. Reviews widgets, upsell popups, live chat, loyalty program widgets, and tracking pixels are common culprits. On desktop’s faster CPU, this is barely noticeable. On a throttled mobile CPU, several of these stacking up is exactly what drags First Input Delay and Total Blocking Time into the red.
3. Homepage carousels and sliders
Carousels are a recurring theme in mobile speed complaints, and for good reason: many carousel implementations load every slide’s image up front (rather than lazy-loading off-screen slides) and run JavaScript to initialise the slider before anything is interactive. On mobile, where the carousel is often the very first thing in the viewport (Largest Contentful Paint candidate), a slow-loading, JS-dependent carousel directly hurts your LCP score.
4. Custom web fonts loading render-blocking
If your theme loads custom fonts via @font-face without font-display: swap (or an equivalent strategy), the browser can block text rendering until the font file arrives. This costs more on a throttled mobile connection than on fast desktop wifi.
5. Third-party pixel and tag stacking
Meta pixel, TikTok pixel, Google Ads conversion tracking, affiliate tracking, and A/B testing tools each add their own script. Individually small, collectively they add up, and mobile users, with less CPU and bandwidth, feel that weight more than desktop users do.
A Practical Checklist for Diagnosing the Gap
Before you touch anything, get a clear read on where the problem actually sits. Run through this sequence:
- Run PageSpeed Insights on your homepage, a collection page, and a product page, separately for mobile and desktop. Note the score gap on each template; it’s rarely uniform.
- Check the “field data” (Core Web Vitals) versus “lab data” sections. Field data (from real Chrome users, via the Chrome UX Report) tells you what’s actually happening for real mobile visitors, not just a simulated test run.
- Open the “Diagnostics” section and sort by mobile impact, look specifically at “Reduce unused JavaScript,” “Properly size images,” and “Eliminate render-blocking resources.”
- Audit your installed apps in Shopify admin under Settings > Apps and sales channels, list every app that touches the storefront, and check whether each one is still earning its keep.
- Check image dimensions on your top templates against actual rendered size on a phone screen, is a 2000px image being displayed at 400px wide?
- Test on an actual mid-range Android device if you can, not just a simulator, real-world battery saver modes and background apps make mobile performance worse than lab tests often suggest.
Fixing the Gap, Not Just the Number
A few genuinely effective levers, roughly in order of typical impact:
- Compress and correctly size images, and confirm your theme is serving responsive
srcsetvariants rather than one fixed size for every device. - Lazy-load below-the-fold images and carousel slides so the browser isn’t fetching everything at once on page load.
- Audit and remove apps you don’t need, and for the ones you keep, check whether they offer a “load only on specific pages” setting rather than loading site-wide.
- Defer non-critical scripts (chat widgets, some tracking pixels) so they load after the main content is interactive, not before.
- Simplify or replace JS-heavy carousels with lighter, native theme sections where the design allows it, especially on the homepage, where LCP matters most.
- Set
font-display: swapon custom fonts so text isn’t invisible while fonts load.
One honest caveat: some of this is genuinely a trade-off. A merchandising team might want six product images in a homepage carousel; a performance-first build might argue for two. There’s no single correct answer, it depends on what matters more for that store’s conversion goals, and that’s a conversation worth having explicitly rather than defaulting to whichever is easiest to implement.
When to Bring In a Specialist
If you’ve worked through the checklist above and you’re still seeing a wide gap between desktop and mobile, or you’re not sure which of the dozen “opportunities” in your PageSpeed report will actually move the needle versus which are noise, that’s usually the point where a proper technical audit pays for itself. A lot of the highest-impact fixes here (responsive image delivery, script loading order, theme-level rendering behaviour) touch Liquid templates and app configuration in ways that are easy to get wrong on a live store. Our Shopify performance optimisation service is built specifically around diagnosing this mobile/desktop gap and fixing the underlying causes rather than chasing a Lighthouse number for its own sake.
FAQ
Why is my Shopify mobile PageSpeed score so much lower than desktop even though I haven’t changed anything?
Because desktop and mobile tests use different throttling profiles, mobile simulates a slower CPU and a throttled connection, so the same page, apps, and images cost more time to load and become interactive. The page hasn’t changed; the test conditions have.
Does a low mobile PageSpeed score actually hurt my Google rankings?
Google has used mobile-first indexing for years, meaning it primarily evaluates the mobile version of your site for ranking. Core Web Vitals are a confirmed ranking signal (a relatively minor one compared to content relevance), so persistently poor mobile performance can be a contributing factor, though it’s rarely the single cause of a ranking problem.
Should I try to get my mobile score to 90+ like my desktop score?
Treat the score as a diagnostic, not a target to chase for its own sake. What matters more is real-user Core Web Vitals data in Search Console and whether load times are costing you mobile conversions, a store at 70 mobile with fast real-world load times can outperform one obsessing over hitting 95 in a lab test.
Are Shopify apps the main cause of slow mobile speed?
They’re a very common cause, but not the only one. Oversized images and unoptimised carousels are just as frequent. The right approach is auditing your specific store rather than assuming it’s “probably the apps.”
Can I fix this myself without a developer?
Some of it, yes, compressing images before upload, removing unused apps, and reviewing app settings for “load on all pages” toggles are accessible to most merchants. Liquid-level changes like responsive image markup, script deferral, and carousel rebuilds typically need theme development experience to do safely.
Next Step
If you want a clear picture of exactly what’s dragging your mobile score down rather than a generic list of “opportunities,” a proper Shopify audit will show you what’s actually worth fixing on your specific store. It’s a practical first step before spending time or budget guessing.
