Use case

Fix the mobile experience where the traffic actually is

Most Shopify stores get most of their visits on a phone, and evaluate their storefront on a laptop. That gap is where a lot of revenue quietly goes.

  • Mobile-only segmentation
  • Rage-click detection
  • Real device replay
Mobile brings the visits. It does not bring the same share of orders.

75%

Share of US traffic

78% globally

64%

Share of US orders

66% globally

An eleven-point gap between where shoppers arrive and where they buy. That gap is not a law of nature — people are perfectly willing to spend money on a phone. It is the accumulated cost of a storefront that was designed, reviewed and signed off on a laptop.

Source: Salesforce Shopping Index — 1.5bn unique global shoppers across 67 countries, Q1 2024

Mobile is not a smaller desktop

The failures are specific to the device, which is why desktop testing never surfaces them. A tap target that is comfortable with a mouse is a coin flip with a thumb. A gallery that reveals itself on hover reveals nothing. A sticky bar that costs 60px on a laptop eats a quarter of a phone screen. And every one of these is invisible in an aggregate report, because the aggregate is dominated by the device that works.

  • Taps that miss — targets too small or too close together
  • Hover-dependent interactions that simply do not exist on touch
  • Forms that summon the wrong keyboard, or lose their content on rotate
  • Sticky headers, chat widgets and cookie bars stacking over the buy button
Ecommerce conversion rate against page load time
1 second
3.05%
2 seconds
1.68%
3 seconds
1.12%
4 seconds
0.67%

Page load timeEcommerce conversion rate

Source: Portent — 20 sites, 27,000+ landing pages, 100M+ page views, 5.6M sessions, 2022

The first second is worth more than all the others

Look at the shape of that curve rather than the numbers. Going from one second to two costs nearly half the conversion rate; going from three to four costs far less, because by then most of the impatient shoppers have already gone. Speed work has sharply diminishing returns — which is good news, because it means the valuable work is concentrated at the fast end and you do not need a perfect score to collect most of the benefit.

+8.4%retail conversions, from 0.1s faster
Google and Deloitte instrumented 37 brands across 30 million sessions and measured what a tenth of a second is worth. Retail conversions rose 8.4% and average order value rose 9.2%. A tenth of a second is one oversized hero image — this is the rare optimisation where the unit of work is genuinely that small.

Source: Google / Deloitte — “Milliseconds Make Millions” — 37 brands, 30M+ sessions; retail figures from 20.5M sessions across 15 retail brands

A mobile pass that is worth doing

In this order, because the first step usually makes the rest obvious.

  1. 1

    Buy from your own store on your own phone, on mobile data

    Not the simulator, not office wifi. The single highest-yield thirty minutes available to any merchant, and most have never done it.

  2. 2

    Segment every report to mobile before reading it

    A blended number is a mobile number with a flattering desktop average mixed in. Look at them separately or do not look.

  3. 3

    Find the taps that go nowhere

    Rage and dead taps on mobile templates point straight at targets that are too small, too close, or not actually interactive.

  4. 4

    Spend the speed budget on the first second

    Hero image weight, render-blocking scripts, third-party widgets above the fold. Per the curve above, this is where the money is.

Which specific assets are costing you that first second, on your own templates, is what Storefront Speed reports. Read on →

Questions

Shopify Mobile Optimization, answered

Is this only about page speed?
Speed matters, and heavy assets hurt more on mobile connections than anywhere else. But most of what we see is interaction friction — targets too small, controls that do not respond, content positioned for a screen the shopper does not have.
My theme says it is responsive. Is that not enough?
Responsive means the layout reflows. It says nothing about whether the resulting order of content still makes sense, or whether a control is comfortable to hit with a thumb. Those are behavioural questions, and they need behavioural data.
Can I see what a specific shopper experienced?
Yes — session replay reconstructs the visit as it happened on that device, including the taps that did not do anything. That is usually more persuasive than any chart when you are deciding what to fix first.
Where should I start?
Rage clicks, then scroll depth, then the cart step. In that order. The first is the cheapest to fix, and the last is the most expensive to leave broken.

Stop guessing. Fix it and see the money.

Install DynoWeb on your Shopify store and see your first findings within a day of normal traffic.

Questions first? Talk to us or read the merchant stories.