A New Benchmark Report Just Changed the CRO Conversation
DTC Pages just published one of the more honest pieces of conversion rate data you'll find. It's based on anonymised first-party data from 21 Shopify stores doing a combined $688M in annual revenue, not recycled industry averages from a SaaS company with a product to sell.
The headline stat: mean CVR dropped to 2.32% in Q1 2026, down 22% year-over-year. Most merchants seeing that number would start tearing apart their PDPs. The report's argument is that they'd be looking in the wrong place.
Traffic grew 50% year-over-year across these stores. When you scale paid acquisition, influencer spend, and PR, you import colder audiences who have never heard of your brand and aren't ready to buy. The denominator gets bigger. CVR looks worse. That's not a conversion problem, that's growth with a measurement optics issue.
Fair enough. But buried in the same data is something that is a real problem, and it's one that doesn't sort itself out.
The Number That Should Actually Worry You
Mobile accounts for 84.4% of all ecommerce traffic in this dataset. Mobile converts at 2.87%. Desktop converts at 4.51%.
That's a 57% performance gap between the channel carrying nearly all your traffic and the channel that barely anyone uses. If your store skews anywhere close to that mobile split, you're running an acquisition engine that sends the majority of visitors into an experience that converts at roughly half the rate of desktop.
This isn't new information. The mobile-desktop conversion gap has been documented for years. What's notable is that with real first-party data from 21 stores at this revenue scale, the gap hasn't closed. It's still enormous.
There are a few reasons mobile converts worse, and not all of them are fixable through CRO alone. Smaller screens make trust signals harder to display. Payment friction is higher on mobile unless you've got Apple Pay and Google Pay set up properly. And then there's page speed, which on mobile is genuinely in a different category of bad.
Page Speed Is Where Revenue Goes to Die on Mobile
Research from Portent across 100 million page views found that a site loading in one second has an ecommerce conversion rate 2.5x higher than one loading in five seconds. That's not a marginal uplift. That's a different business.
Mobile networks and mobile CPUs make slow pages slower. A Shopify store that scores fine on desktop Lighthouse tests can be genuinely painful on a mid-range Android device on 4G. Most merchants never test that scenario.
Huckabuy's analysis puts the average conversion rate drop at 4.42% for each additional second of load time in the zero-to-five-second window. Stack two or three slow-loading third-party scripts on a product page and you're past that threshold before the above-the-fold content has even rendered.
Vodafone Italy improved their Largest Contentful Paint by 31% and recorded 8% more sales as a direct result. That's a controlled, A/B-tested outcome, not a correlation someone massaged in a spreadsheet. Rakuten 24 optimised all three Core Web Vitals and saw a 53% increase in revenue per visitor alongside a 33% higher conversion rate.
These aren't edge cases. They're what happens when you treat page speed as a revenue lever rather than a technical housekeeping task.
What the Add-to-Cart Data Is Actually Telling You
The DTC Pages report includes one more number worth paying attention to. The average add-to-cart rate across all 21 stores was 7.23% for FY2025. Stores with ATC rates above 10% consistently hit overall conversion rates above 3.8%. Below 5% ATC, the bottleneck is almost certainly the product page or landing page experience, not the checkout.
That's a useful diagnostic. If your ATC rate is low, optimising checkout is wasted effort. But if your ATC rate is healthy and you're still losing people before payment, the checkout itself is the problem, and the report names the usual suspects: surprise shipping costs, mandatory account creation, and slow checkout page speed.
Slow checkout page speed is the one on that list that's actually invisible to most merchants. You can see surprise shipping costs in your analytics. You can see account creation friction in your checkout settings. A JavaScript error silently breaking your payment form at step three of checkout? That one you only find out about when someone tweets at you or your revenue drops and you can't explain why.
The Errors Nobody's Watching
The average Shopify store runs 15 to 25 third-party scripts. Review widgets, loyalty apps, chat tools, analytics tags, affiliate tracking, personalisation engines. Each one is a dependency. Each one can fail independently without setting off any alarm in your Shopify admin.
A broken script on your product page might suppress the add-to-cart button for a subset of mobile visitors. An unhandled promise rejection in your checkout flow might stop the payment submit button from responding on certain browsers. These aren't hypothetical failure modes, they're the kind of thing that shows up as a gradual CVR decline that everyone assumes is a seasonal pattern or a traffic quality issue.
Shopify's own analysis suggests a one-second delay in site speed could cost a store $9,000 per day at a $60 AOV with 5,000 daily visitors. A JavaScript error that breaks checkout for 3% of sessions at that same volume is in the same financial ballpark, and it's far less likely to be spotted.
This is exactly what Bloodhound is built to catch. It monitors JS errors, console errors, failed network requests, and Core Web Vitals in real time across your storefront, and it tracks the full purchase funnel via Shopify Web Pixel, from add-to-cart through to payment submit. When something breaks in checkout, you get a Slack or Teams alert within seconds, with a stack trace and an estimate of the revenue impact based on affected sessions.
The checkout funnel monitoring piece is genuinely unusual. Most error tracking tools are generic infrastructure products that you adapt to Shopify. Bloodhound is built specifically for Shopify stores, which means the checkout visibility actually works rather than requiring months of custom instrumentation.
A Practical Checklist for 2026 CVR Diagnostics
If the DTC Pages benchmarks have made you want to actually do something useful rather than panic about a 2.32% mean CVR, here's where to start:
- Check your add-to-cart rate first. If it's below 5%, your product page experience is the problem. Fix that before touching checkout.
- Run a real mobile speed test, not Lighthouse on desktop. Use WebPageTest on a simulated mobile device with throttled network conditions. The results will be worse than you expect.
- Audit every third-party script running on your storefront. Work out which ones are render-blocking and which ones you can load asynchronously or defer entirely. Most stores have at least two or three scripts that have no business loading before the page is interactive.
- Check your Core Web Vitals in Google Search Console, specifically LCP and INP on mobile. Even a half-second improvement in load time can lift conversions, and INP failures are increasingly common on script-heavy stores.
- Verify your checkout works end-to-end on a mid-range Android device. Not your work iPhone. A Samsung Galaxy A-series or similar. Pay with a real card if you can.
- Set up error monitoring on your storefront. A JavaScript error breaking checkout for 2% of sessions costs more than almost any A/B test can recover.
Don't Optimise for the Wrong Metric
The DTC Pages report makes a solid case that a falling CVR during a period of aggressive traffic growth isn't necessarily a crisis. That reframe is genuinely useful for merchants who'd otherwise waste a quarter rebuilding product pages that aren't the actual bottleneck.
But the corollary is important: if your traffic quality is stable and your CVR is still soft, you don't have an acquisition problem. You have a store problem. Broken scripts, slow pages, and checkout friction are the things most likely to be silently eating your revenue, and they're also the things least likely to show up clearly in standard Shopify analytics.
The 2026 benchmarks are a useful calibration point. The real work is in knowing whether your gap from 3.8% is explained by traffic mix or by something that's actually broken. Those two diagnoses require completely different responses. Getting that call wrong is expensive.
Sources
- web.dev — "Vodafone (Italy) improved LCP by 31% to achieve 8% more sales."
- portent.com — "A site that loads in 1 second has an e-commerce conversion rate 2.5x higher than a site that loads in 5 seconds."
- shopify.com — "A one-second delay in site speed could be costing you $9,000 a day."
- shopify.com — "Even a half-second improvement in site speed can increase your conversion rate."
- huckabuy.com — "Website conversion rates drop by an average of 4.42% for each additional second of load time between 0 and 5 seconds."
- monsterinsights.com — "Rakuten 24: Optimized all three Core Web Vitals and saw a 53% increase in revenue per visitor and 33% higher conversion rate."