Why is your Shopify store not working on mobile?

By Published Updated 7 min read

Last updated 9 November 2026 — added a step to rule out a Shopify or Shop Pay incident when checkout fails on every phone at once, with links to the live checks.

Written with AI assistance.

Short answer (1 November 2026, Waqas Ahmad): because a phone is a different environment from your laptop: touch events instead of clicks, a viewport a third the width, widgets that exist only on mobile (sticky bars, drawers, swipe galleries), and iOS Safari's own rules for viewport height and fixed positioning. The four usual causes, ranked: click-only JavaScript handlers, an overlay whose close button lands off-screen, a broken mobile-only widget, and a Safari layout quirk hiding the buy button. Test on a real phone over mobile data — a resized desktop window shares the desktop's mouse events and JavaScript engine and misses exactly these.

Your share is in Shopify admin → Analytics → Sessions by device. Any currency — the maths is the same.
One broken mobile hour—average → peak-hour range
One broken mobile day—a silent weekend is two or three of these
Enter both numbers to see what a dead mobile add-to-cart costs while your desktop checks all pass.

method: monthly ÷ 730 hrs × mobile share = avg mobile hour · peak hour = 2–3× avg · day = monthly ÷ 30.42 × share — the same maths as my downtime cost calculator. Nothing is uploaded.

Every class of store breakage has a detection lag, and mobile's is the longest. Desktop bugs get caught fast because that's where merchants live. Mobile bugs are witnessed only by customers — who don't file bug reports, they just leave.

The store its owner checks is the desktop one; the store most customers use is the phone one — so the majority experience of a store is the one that gets tested least.

The Bilby scan screen mid-visit on the demo store
The scan screen mid-visit on my labelled demo store, Fernwick & Co.: a screenshot per step as it lands, then the seven things it checks read the recording. Run it on your store: free, about two minutes, no signup, and it never logs in, edits or installs anything on your store. Run the free scan →

The mobile-only failure classes, ranked

1. Touch-event JavaScript bugs

Buttons wired to mouse-specific events (or drag and hover interactions) that never fire on touch. Signature: tapping does nothing on the phone while clicking works on desktop. Often introduced by an app update or a theme customisation that tested fine — on desktop.

2. Viewport and overlay traps

The popup that's dismissible on a big screen can render its close control off-screen at phone width — a cookie bar, email popup or sale banner becomes a wall in front of the buy button. Test your own popups on a phone with the keyboard open; that's when the viewport is smallest.

3. Mobile-only app widgets

Sticky add-to-cart bars, mobile menus, swipe galleries and cart drawers exist only on mobile — so when they break, desktop testing literally cannot see it. A cart drawer that won't open is a checkout outage for every phone user.

4. iOS Safari quirks

Safari on iOS handles viewport height (the URL-bar collapse), fixed positioning and some input behaviours differently from Chrome. A layout perfect on Android can hide its checkout button behind Safari's toolbar. If you test on one phone only, make it an iPhone — and ideally test both.

The mobile test ritual

After every change, on a real phone, in a private tab, over mobile data — six taps, about two minutes:

  1. Homepage loads fast and nothing overlaps or covers content.
  2. Any popup or cookie bar can actually be dismissed with a thumb.
  3. Product page: the gallery swipes, the variant picker taps, the price is right.
  4. Add to cart responds to a tap and the item lands.
  5. The cart drawer or page opens and updates.
  6. Checkout reaches the payment step with the keyboard open.

If step 6 fails on every phone at once — yours, a friend's, a customer's — and you changed nothing, it may not be your theme at all. Checkout and Shop Pay are served by Shopify, and an incident there looks exactly like a mobile bug from your side of the screen. Before you touch a line of code, look at my live Shopify check, which adds a product to the cart on a real store every five minutes from Sydney, Virginia and Frankfurt, and my live Shop Pay check, which loads the host Shop Pay runs on. Both show their history on the page and need no account. If they are green, the fault is in your store and the ritual above will find it.

A resized desktop browser window is not a mobile test — it shares the desktop's JavaScript engine and mouse events, missing exactly the touch-handler and Safari-specific failures that break real phones.

What a mobile-only failure costs

Put your monthly revenue and your mobile share into the calculator beside the answer. The maths is the honest kind: your average hour is monthly revenue divided by 730, the mobile slice of it is that times your share, and a broken peak hour costs two to three times the average because sales cluster in evenings and weekends. A dead mobile add-to-cart approaches full-outage cost while every desktop check you run passes.

The ritual only works if it happens. Mobile checks get skipped exactly when changes are most frequent — launch weeks, sale prep, theme updates. Bilby visits your store every night at a phone viewport as well as a desktop one, in a real browser, and flags anything a customer would hit, with the phone screenshot attached; run the free visit now. It's the safety net under the ritual, not a replacement for shipping carefully.

Frequently asked questions

Why does my store work on desktop but not on mobile?

Mobile is a different environment: touch events, a tiny viewport, mobile-only widgets, and iOS Safari's quirks. The frequent concrete causes are click-only JavaScript handlers, overlays with unreachable close controls, broken drawers or sticky bars, and Safari viewport issues.

How do I test properly on mobile?

Real phone, private tab, mobile data — visit the six-step ritual above by tapping. Test iPhone Safari and Android Chrome if possible; they fail differently. A resized desktop window is not a mobile test.

How much can a mobile-only bug cost?

Your mobile share of revenue, for every hour it runs. Enter your monthly revenue and the mobile share from Sessions by device into the calculator on this page; the method is printed under it.

Why do these bugs last so long?

The person most likely to check the store checks it on desktop, where everything works. Only the conversion graph — or an automated nightly visit at a phone viewport — tells on the mobile experience.

How do I test my Shopify store speed on mobile for free?

Run the free website speed test and read its mobile result first — mobile scores run lower than desktop, and mobile is where most shoppers are. If mobile is slow or broken while desktop looks fine, look at the causes above before assuming the theme is at fault.

Why does my Shopify store look broken on iPhone but work on Android?

Almost always iOS Safari. It sizes 100vh to the full screen behind its toolbars, so a fixed-bottom buy button or a sticky bar can sit under the toolbar where no tap reaches it; it also handles fixed positioning inside scrolling containers differently from Chrome. Open the store in Safari on a real iPhone, scroll the product page to the bottom and try to tap the button; if it is hidden, the fix is a theme CSS change (dynamic viewport units or a safe-area inset), not an app.

Why is my Shopify checkout not working on mobile?

Checkout itself is served by Shopify and is the same on every device, so a checkout that fails only on phones is usually the step before it: an add-to-cart or cart drawer that fails on touch, a discount or upsell app whose mobile layout covers the checkout button, or an express-payment sheet (Shop Pay, Apple Pay) that the customer dismisses and the page does not recover from. Test by adding to cart on a real phone over mobile data, opening the cart, and reaching the information step; the cause is wherever that stops. If every device fails, read the blank checkout post instead.

How slow are Shopify stores on mobile, really?

Google calls a largest-contentful-paint of 2.5 s good and 4 s poor. Bilby measures it on the mobile homepages of public Shopify stores, in a real browser at a phone viewport; the live median and slowest quarter, with their sample size and the day they were computed, are on Bilby’s data report. A store that is slow on mobile is not broken, but shoppers behave as if it were, which is why the free speed test on this site shows the mobile result first.

Bilby checks this for you every night. Free for seven nights →

Keep reading: Add-to-cart not working? · The nightly store check · Images not loading? · Downtime cost calculator

The email Bilby sends before breakfast when something is broken
What it looks like when it happens to a real store: the email, at 06:58.

Is your store
okay on mobile?

Bilby visits your store at a phone viewport every night and reports anything broken — with the phone's screenshot. One free scan, no signup.

Thin or missing product content is the other half of this problem, and it is the half search engines and AI assistants see. Navaal: AI SEO, AEO & GEO audits a Shopify catalogue for it free, and writes what is missing for review.

A Bilby report: the step that failed, ringed, with what it costs
Bilby's report: the step that failed, and what it costs while it stays broken.
A live status card: one service, three cities and the last 24 hours
Everything I publish is measured the same way: by trying the real thing.

What this looks like in the app

The Navaal SEO app writing a product's title and description
Inside the app: a product's title and description, written in your brand's voice. Example product.

Start tonight.

Type your store. Bilby walks it now and shows you what it found. Free, no card.

Scan your store

About two minutes. Bilby stops at payment.

Walk my store