71.7% of Mobile Visitors Never Scrolled Past the Top Quarter of the Homepage

On 2026-09-09 we pulled 30 days of mobile behavior from a US furniture store on Shopify. On the homepage, 71.7% of mobile visitors never scrolled past the top quarter of the page, and the average visitor's furthest point was 20.1% down (our data, scroll depth, homepage, mobile, 99 sessions, 2026-08-10 to 2026-09-09). We looked at why, and this is what showed up.

The editor lies about mobile#

Redesigns rarely fail in the theme editor. They fail on a phone, after the merchant has already moved on to the next task, and Shopify Community threads are full of the same shape of story.

One merchant switched their theme to mobile mode in the editor and the preview looked normal. After saving and checking on an actual phone, the mobile version behaved like the desktop layout instead (a merchant on the Shopify Community forum, August 2025). Another had every app switched on in the theme customizer, trust badges, a video carousel, conversion tools, and none of them appeared on the live product page once it rendered on a phone (a merchant on the Shopify Community forum, December 2025). A third described the size selector, quantity field, and add-to-cart button sitting below the page's main text near the bottom of the page on mobile, so many customers missed them and did not check out (a merchant on the Shopify Community forum, February 2025).

The pattern is not limited to small stores or first-time builders. One operator who had run Shopify stores professionally for more than ten years relaunched a brand's site and went "no orders in over a month" (r/shopify, May 2026). Experience does not stop a redesign from breaking mobile. Only checking does.

What all four threads share is the same blind spot: the person who approved the redesign checked it on a desktop monitor, or in an editor preview that does not actually load like a phone does. Mobile is most of a Shopify store's traffic, and it is the one environment almost nobody tests the change in before it goes live.

What the scroll data actually showed#

We wanted to know what a store that "looks fine in the editor" actually measures like from the shopper's side, not just what the complaints describe, so we pulled 30 days of mobile scroll data from a live store in DynoWeb's dashboard for that account.

On the homepage, 71.7% of mobile visitors never scrolled past the top quarter of the page, average furthest point 20.1% down (our data, scroll depth, homepage, mobile, 99 sessions). Whatever sits below that line, the second section, the collection grid, the footer, is invisible to seven out of ten mobile visitors.

That is not because mobile visitors do not scroll. On the same store, in the same window, 85.2% of blog-post readers scrolled past a quarter of the page, 74.1% past half, and 44.4% past three quarters (our data, scroll depth, 10 pages). Collection pages went the other way: 0% of sessions reached the last quarter of the page on any collection template we measured. Same store, same visitors, three different scroll behaviors depending on what the page asked of them.

That is the tell. A shopper who reads a blog post to the bottom will scroll. A shopper who stops 20% down a homepage and never touches a collection page's lower half is not lazy. Either the page is not giving them a reason to keep going, or the layout under the fold on a phone is not the layout whoever built it was picturing.

What the theme and performance audit found#

Scroll depth says where attention stops. It does not say why. For that we ran a theme and performance audit on the same store's product pages.

71% of product-page sessions bounced immediately (our data, theme audit). The audit's explanation: none of the product images had width or height set in the code, so the browser does not know how much space to reserve for them, and the layout jumps as each image finishes loading. A shopper who taps "add to cart" a half-second early can end up tapping whatever shifted into that spot instead, on a page that visually moved out from under their thumb.

Tap response was the other flag. We measured about 620 milliseconds between a tap and the page responding, on one product page (our data, performance audit). The usual rule of thumb is that a response over about 200 milliseconds starts to feel slow to the person waiting on it. Our reading here ran roughly three times past that line, on the device most of its visitors were using.

Neither of these shows up in a quick look at the theme editor. A layout jump only happens once real images load at real network speed, and a slow tap response only shows up once you are holding the phone yourself, tapping the actual button, waiting for the actual response. Both are exactly the kind of thing that looks fine when a redesign is approved and only shows up once shoppers start using it.

What to change first, in a draft you review#

None of this needs a rebuild. In order of how much of the drop-off each one likely explains:

1. Set width and height on every product image, or at minimum a fixed aspect-ratio box, so the layout stops moving while images load. This is a Shopify theme setting or a couple of lines of Liquid, not a redesign.
2. Compress the top of the homepage. If 71.7% of mobile visitors stop at 20% down, whatever occupies that first screen and a half is the entire homepage for most people. A hero, a promo bar, and a slow first image competing for that space asks a lot of it.
3. Time the tap response, not just the page load. A fast load score can still hide a slow product page if the interaction itself lags. Test on a real phone, not a simulator, the way the merchant with the mismatched mobile preview eventually had to.

If a fix touches the theme itself, the safer route is to make the change in a copy of the theme first, check the page still renders before and after, and only publish once it looks right. That is the shape of the workflow DynoWeb's Restyle tool follows: it edits a duplicate of the theme, shows the page before and after, and saves the result to a draft. The merchant reviews the draft and publishes it themselves, in Shopify admin. Nothing goes live on its own.

Check your own store in 10 minutes#

Nothing here needs an app installed first.

1. Open your homepage on your own phone, not a browser window resized to look like one. Scroll naturally and notice where you stop wanting to continue. That is roughly where most visitors stop too.
2. Compare that to a blog post or a long product description on the same store. If you scroll further there without thinking about it, the homepage has a reason problem, not a mobile problem.
3. Try to add a product to your cart with one thumb, on the slowest connection you can find. Count how long it takes before anything visibly responds to your tap.
4. Open your browser's inspector on a product image and check whether the <img> tag has a width and height set. If it does not, that is a layout jump waiting to happen on a slow connection.
5. Switch your theme editor to mobile mode, save, then check the live page on an actual phone before you assume the two match.

A redesign that looks finished in the editor and a redesign that works on a phone are two different projects. Only one of them is the one your visitors experience.

The scroll, tap and layout numbers in this piece came from the same kind of view our dashboard showed for the furniture store above.