We measured 7 DTC product pages on mobile: what we found

We loaded seven real direct-to-consumer product pages on a phone-sized screen and measured what a shopper actually sees before scrolling, and the add-to-cart button was below that first screen on most of them. This is original data, measured on the twenty-third of July 2026 at a 375 by 812 viewport, the size of a common phone, and the full method sits at the foot of this piece. The short story, even big, well-funded brands put the buy button where a mobile shopper has to hunt for it, and they load a lot of third-party script to do it.

The reason we ran this ourselves, most advice about the mobile fold is assertion without measurement, and our own sticky add-to-cart work kept running into the same gap on real stores. So we measured, on stores anyone can open, and wrote down the numbers.

What we measured, store by store

The set was seven stores, each running on Shopify or on Shopify under a custom front end, and we pulled one representative product page from each. For every page the notes were the same, where the buy control landed against the 812-pixel line, where the price and the review stars landed, and the count of scripts the page dragged in from other companies’ servers.

Take the six standard product pages together. On four of them the add-to-cart button had already scrolled off the first screen before the shopper touched a thing. The other two kept it where a thumb could reach it. Allbirds was the extreme, its buy control measured more than three thousand pixels down, several full screens of scrolling from the top. Jones Road went the other way and put price, reviews, and the buy button all inside the first screen, the layout doing exactly what a mobile page should.

The buy button is too far down

The pattern is the headline. A shopper on a phone decides fast, and a product page that hides its one action below several swipes of scrolling is spending attention it did not need to spend. This is the exact gap our sticky-cart data speaks to, the buy button that scrolls away costs conversions on the device where most traffic now lives, and the fix is a persistent bar that keeps the action in reach. Four of six pages here would benefit from it today, and these are not small operations, they are brands with real budgets and real teams.

Reviews told a gentler story, four of six pages surfaced star proof above the fold, so the trust signal tends to get prioritized while the action does not. Social proof up top and the buy button buried is a common shape, and it is backwards, the proof earns the click that the missing button then fails to catch.

The script counts are heavy

The second finding is weight. The lightest page still pulled 68 third-party scripts. The heaviest pulled 258. Most sat somewhere near 144, reaching out to anywhere from 11 to 33 different outside servers to do it. Death Wish Coffee alone loaded 173 scripts from 33 hosts, Jones Road ran 203, and ColourPop topped the set. Behind each request is an app or a tracking tag earning its keep, or not, and the store pays the loading cost on every page either way, used or ignored, the app tax our earlier bloat audit measured, seen again from the script side.

Heavy pages load slower, and slow pages lose the same mobile shopper the buried buy button was already testing. The two findings compound, a page that arrives late and then hides its action is asking a lot of a phone user with a thumb hovering over the back button. The speed guide and Google’s own LCP guidance both point the same way, fewer render-blocking requests, lighter pages, faster first screens.

What this means for your store

None of these brands is doing everything wrong, and the point is not to dunk on them, it is that if teams this size leave the buy button below the fold and carry two hundred scripts, the odds are your store does something similar. Two checks tonight. Open your own product page on your phone and see whether you can tap buy without scrolling, and if you cannot, a sticky bar is a short native build. Then count the apps loading on that page, because the conversion apps worth keeping are the few doing real work, and the rest are weight you can shed. Measured beats assumed, which is the whole reason we ran the numbers instead of guessing at them.

Method and limits

The honest caveats. We measured seven stores on one date, a small sample, directional not definitive. Detection was heuristic, we located the add-to-cart, price, and review elements by pattern, and price detection missed at least one store’s format, so we leaned the findings on the add-to-cart and script counts, which read cleanly. One page, ColourPop’s, was a bundle rather than a single product, so we used its script count but not its layout. Above the fold means an element’s top edge fell within the 812-pixel viewport height. Script and host counts came from the rendered page. Numbers reflect what loaded for us at that moment, not a claim about any brand’s typical build.

FAQ

What did the audit measure?

Seven real DTC product pages loaded at a 375 by 812 phone viewport, checking whether add-to-cart, price, and reviews sat above the fold, plus each page’s third-party script and host counts. Measured 23 July 2026, methodology disclosed above.

What was the main finding?

The add-to-cart button was below the first mobile screen on four of six standard product pages, one as far as 3117 pixels down. Big brands surface reviews early but often bury the buy button, the gap a sticky cart bar closes.

How heavy were the pages?

Third-party scripts ran from 68 to 258 per page, median around 144, across 11 to 33 external hosts. Most load on every page regardless of use, the app-tax weight that slows the same mobile shopper the buried button already tested.

Is seven stores enough to conclude?

It is directional, not definitive, and we say so. It is enough to show the pattern exists at brands with real budgets, and enough reason to check your own store on a phone tonight rather than assume it is fine.

Can I check my own store this way?

Yes. Open your product page on your phone and try to tap buy without scrolling. Then look at how many apps load on it. Those two checks catch most of what we measured, and both point to fixes you can make.

Want your product page measured and fixed, the buy button and the weight both? Send me the store and I will tell you what sits below your mobile fold. Free look, no obligation, usually a reply within the hour.