We're not claiming to have measured this ourselves. These are findings from published research by organizations with the scale to measure it. We cite them because they quantify what legacy framework performance costs in revenue.
Published Findings
Our Framework Performance Data
From our 1,265-site scan, we measured average response times by detected framework. These are TTFB measurements from our scanning infrastructure, not Core Web Vitals from real user data.
The Implication
If Deloitte's finding holds — that 100ms of improvement translates to ~1% revenue lift — then the TTFB gap between WordPress (800-2000ms) and Astro (10-50ms) represents a structural revenue disadvantage for sites on legacy frameworks. We don't claim a specific dollar figure because the impact varies by site, traffic, and conversion funnel. But the published research is clear that the relationship between speed and revenue is measurable and significant.
Data Sources
Deloitte 'Milliseconds Make Millions' (2020). Google/SOASTA mobile benchmark (2017). Akamai State of Online Retail Performance. Google Search Central Page Experience documentation. WebPulse scan (initial baseline) (May 2026). All TTFB figures are from our scanning infrastructure response times, not CrUX real user metrics.
