CWV for Mobile vs Desktop: Which Wins in 2026?

Mobile devices have slower CPUs, less memory, and variable network connections. Desktop machines have faster processors, more RAM, and stable wired or WiFi networks. This hardware gap directly affects all three CWV metrics.

HTTP Archive data from 2025 shows the gap clearly. The median mobile LCP is 2.9 seconds. The median desktop LCP is 1.9 seconds. Mobile INP is 210 milliseconds compared to 150 milliseconds on desktop. CLS shows the smallest gap with 0.06 on mobile and 0.04 on desktop.

Pass rates for all three metrics show a 10-15 percentage point gap between mobile and desktop. Approximately 72% of mobile origins pass LCP versus 84% for desktop. Mobile INP pass rate is 68% versus 78% for desktop. CLS pass rates are 85% mobile and 91% desktop.

Network conditions are the primary factor. Mobile users connect over cellular networks with higher latency and variable bandwidth. The 75th percentile RTT on mobile is approximately 150 milliseconds. Desktop RTT is typically under 30 milliseconds.

CPU throttling makes a significant difference in INP. Mobile devices often have 4-8 cores running at reduced clock speeds. Desktop machines have 8-16 cores at higher speeds. JavaScript execution that takes 50 milliseconds on desktop can take 150 milliseconds on a mid-range mobile device.

Memory constraints affect CLS and LCP. Mobile devices have 4-8GB of RAM. Desktop machines have 16-64GB. Browsers on mobile are more aggressive with tab discarding and cache eviction. This means resources may reload on revisit, causing slower LCP.

Google uses mobile-first indexing since 2021. The crawler primarily uses the mobile version of your pages for indexing and ranking. Desktop CWV scores are still collected but carry less weight in search rankings.

If your page passes CWV on desktop but fails on mobile, you get no page experience ranking boost. Mobile performance is the gatekeeper. Google's John Mueller confirmed this in 2023. Fix mobile CWV first.

The CrUX report in PageSpeed Insights shows separate scores for mobile and desktop. Always check the mobile tab first. That is the data Google uses for ranking evaluation.

Prioritize mobile performance in your development workflow. Test on real mobile hardware, not just browser DevTools emulation. Use CPU throttling in DevTools to simulate mid-range devices. Test on actual 3G and 4G network conditions.

Minimize JavaScript for mobile. Smaller bundles reduce parsing time and improve INP. Use code splitting to load only what the mobile viewport needs. Consider serving a lighter mobile experience if your page is JavaScript-heavy.

Use responsive images with appropriate sizes for mobile viewports. Serve smaller images to mobile devices. The srcset attribute with width descriptors enables this. Combine with image CDN resizing for additional savings.

Desktop CWV is easier to pass but still matters. Desktop users expect fast performance. Many business users work on desktop exclusively. Enterprise and B2B sites see majority desktop traffic. Optimize for desktop after achieving mobile pass rates.

Desktop LCP optimization is usually straightforward. Server response time and image optimization are the main areas. Desktop INP benefits from the same long task avoidance strategies. CLS fixes apply equally to both.

Run PageSpeed Insights for both mobile and desktop on your top 20 pages. Compare the scores. Identify metrics that pass on desktop but fail on mobile. Fix mobile issues first. Set separate performance budgets for mobile and desktop in your CI pipeline.

Note the gap between your mobile and desktop CWV scores. A large gap indicates mobile-specific issues that need targeted fixes. Closing the gap improves the user experience for your largest traffic segment. Audit quarterly.

• web.dev/mobile-performance (https://web.dev/mobile-performance)
• HTTP Archive CWV by Device (https://httparchive.org/reports/chrome-user-experience#device)
• Google Mobile First Indexing (https://developers.google.com/search/docs/crawling-indexing/mobile-first-indexing)
• CrUX Device Report (https://developer.chrome.com/docs/crux/overview#device)