Revenue Lost Per 100ms Of Mobile LCP On DTC Storefronts Benchmarks
A DTC-specific benchmark translating mobile LCP research into euros lost per 100ms — broken out by AOV band and traffic source, with the math for a €5M store.
Revenue Lost Per 100ms of Mobile LCP
The estimated revenue a DTC store forfeits for every additional 100 milliseconds of mobile Largest Contentful Paint.
Revenue lost per 100ms of mobile LCP is a site-speed benchmark that converts a technical metric — Largest Contentful Paint on mobile devices — into a euro figure a finance team recognises. It combines three inputs: your annual mobile revenue, the elasticity of conversion to load time (typically 0.6-1.5% conversion drop per 100ms in the 2-5s LCP band), and how sensitive your specific traffic mix is to friction.
For a €5M store with 60% mobile revenue and a paid-social-heavy mix, each 100ms above the 2.5s "Good" threshold translates to roughly €18k-€35k per year in forgone gross revenue. The number scales non-linearly: the first 100ms past 2.5s hurts less than the fifth.
The underlying research is a decade old and well-replicated. Google's 2017 mobile page-speed study found bounce probability rises 32% as LCP moves from 1s to 3s, and 90% from 1s to 5s. Deloitte's 2020 "Milliseconds Make Millions" analysis pegged conversion elasticity at ~0.8% per 100ms for retail mobile. Shopify's own 2022 platform data landed in the same band.
What the public research does not do is translate those percentages into euros for a specific store profile. That is what this page does — for online-retail brands in the €1M-€15M revenue band, on Shopify, Woo or Magento, running a normal paid-social and Google-Ads acquisition mix.
Estimated annual revenue lost per 100ms of additional mobile LCP, by AOV band. Assumes a €5M store, 60% mobile revenue share, baseline LCP of 3.0s (i.e. already past the 2.5s "Good" threshold).
| AOV band | Conversion elasticity (per 100ms) | € lost per 100ms / year | € lost per 500ms / year |
|---|---|---|---|
| €30-€60 (apparel, beauty basics) | 1.1% | €33,000 | €158,000 |
| €60-€120 (mid-tier fashion, skincare) | 0.9% | €27,000 | €131,000 |
| €120-€250 (premium apparel, small electronics) | 0.7% | €21,000 | €103,000 |
| €250-€500 (furniture, high-end beauty sets) | 0.5% | €15,000 | €74,000 |
| €500+ (considered purchase, bikes, appliances) | 0.3% | €9,000 | €45,000 |
The pattern is counter-intuitive at first glance: lower-AOV stores lose more per 100ms in absolute euros, not less. That is because low-AOV baskets convert on impulse — a beauty shopper choosing between three stores on a Meta ad will abandon a slow page faster than a customer researching a €900 e-bike who has already committed cognitively. Impulse traffic punishes slow LCP hardest.
Conversion drop per 100ms of added mobile LCP, by acquisition channel
How to read these numbers for your store
Two adjustments matter. First, scale linearly with your revenue: a €2M store divides these figures by 2.5, a €10M store multiplies by 2. Second, weight by your traffic mix. If paid social is 50% of your sessions, your effective elasticity is closer to the top of the range; if you are 70% email and returning direct, use the lower bound.
The elasticity is also non-linear across the LCP curve. Moving from 4.0s to 3.9s recovers more revenue than moving from 2.5s to 2.4s, because you are pulling users back across the abandonment cliff that sits around 3s on mid-tier Android devices. This is why the same 100ms win is worth two or three times more on a slow storefront than on an already-fast one.
The tracking-script tax is usually the biggest lever
On a typical Shopify storefront, 40-60% of mobile LCP is attributable to third-party scripts: analytics, heatmaps, A/B testing tools, review widgets, chat, and pixel stacks. Every additional analytics tag adds roughly 60-180ms of LCP on a mid-tier Android over 4G. Consolidating a five-tool CRO stack into one snippet routinely recovers 300-500ms — which at €27k per 100ms on a €5M mid-AOV store is a €80k-€135k annual line item.
Where the biggest wins hide
The revenue impact concentrates in three places. First, the product detail page — where new visitors from paid social land and where LCP hurts more than on checkout, because intent is still being formed. Second, the mobile experience on mid-tier Android devices over 4G, which is the real-world condition most stores never test on. Third, the Shopify theme app stack, where each installed app carries a measurable LCP cost.
A useful rule of thumb: if your paid-social LCP on a mid-tier Android is above 3.5s, you are leaving roughly one month of net profit per year on the table. Fix the PDP first, audit the tag stack second, and only then look at image weight and CDN configuration — most stores get this order backwards.
Frequently asked questions
It is causal, not correlational. Google, Deloitte and Shopify have all run controlled experiments where LCP was artificially degraded or improved and conversion tracked. The 0.5-1.5% conversion elasticity per 100ms replicates across studies, platforms and verticals. The debate is about the exact coefficient for your store, not whether the effect exists.
Paid social traffic has lower baseline intent and higher tolerance for competing options — a shopper is one swipe from the next ad. Organic visitors arrived on purpose, often with a specific query. The result is that paid social punishes slow LCP roughly twice as hard as organic. This is covered in more depth on the paid-social LCP sensitivity page.
2.5s is Google's "Good" threshold and the point at which Core Web Vitals stops penalising you in search. But conversion elasticity keeps rewarding you below that: 2.0s converts measurably better than 2.5s, and 1.5s better still. Diminishing returns kick in around 1.2-1.5s on mobile.
Median real-user LCP on Shopify stores measured on mid-tier Android over 4G sits around 3.2-3.8s. "Fast" storefronts (top decile) come in at 2.0-2.4s. The gap between a p50 and a p90 store on this device profile is worth six figures a year for most €5M brands.
On a mid-tier Android over 4G, a typical third-party script adds 60-180ms of LCP depending on whether it blocks the main thread and whether it loads a heavy dependency. GTM alone often adds 200-400ms once you count everything firing through it. Consolidating the stack is usually the fastest way to recover 300-500ms.
Overwhelmingly on new visitors. Returning customers have brand trust, remembered accounts and existing intent — they will wait 4-5 seconds where a new visitor from a Meta ad would have bounced at 3.2s. The revenue-loss numbers on this page are dominated by new-visitor abandonment.
PDP first, in almost every case. Checkout traffic has already committed and will tolerate more friction; PDP traffic is being acquired and is where the acquisition-to-decision funnel narrows fastest. A 100ms LCP win on the PDP is worth roughly 2-3x the same win on checkout for most DTC stores.
Segment mobile sessions into LCP buckets (under 2.5s, 2.5-3.5s, 3.5-5s, over 5s), then compute conversion rate and revenue per session for each bucket. Multiply the CVR delta between adjacent buckets by your average session count and AOV. Metricuno's speed report does this automatically from your GA4 import.
Yes — the numbers get worse. Peak-traffic tag load slows LCP by an additional 400-900ms on many storefronts, exactly when your traffic and CAC are highest. A 100ms of LCP on Black Friday is worth 3-5x a 100ms on a regular Tuesday because both traffic and conversion sensitivity spike.
For most Shopify stores, removing or async-loading the two heaviest third-party scripts (usually a heatmap tool and an A/B testing tool) recovers 250-400ms with no functional loss. Consolidating those tools into a single lightweight snippet is the second-order fix once you have measured the impact.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.