INP Core Web Vitals leaderboard for July 2025: Squarespace and BigCommerce lead - WordPress improves

INP results by CMS and shopping platforms

The July dataset shows strong INP performance across hosted builders and steady gains for several open-source CMSs. Figures reflect the share of origins on each platform with "good" INP (≤200 ms at the 75th percentile) in field data. Methodology details follow. [S1][S2][S3]

Executive snapshot

• Squarespace leads CMSs at 96.07% "good" INP; Duda follows at 93.81%. [S1]
• Adding shopping platforms, BigCommerce enters at 95.29% (2nd overall); Shopify is 89.58% (4th overall). [S1]
• WordPress and Wix are mid-pack at 86.77% and 87.52%; Drupal 86.14%; Joomla 84.47%. [S1]
• June to July improvement leaders (percentage-point change in "good" INP share): Joomla +1.12; WordPress +0.88; Wix +0.70; Drupal +0.64; Duda +0.46; Squarespace +0.22. [S1]
• Range across the six CMSs is tight: 84.47%-96.07% (~11.6 points), indicating broadly solid responsiveness at scale. [S1]

Implication for marketers: Platform defaults matter - Squarespace and BigCommerce reduce baseline INP risk, while WordPress and WooCommerce can match peers with disciplined scripting and theme or plugin choices.

Method and source notes

This analysis uses the HTTP Archive Core Web Vitals Technology Report for July 2025; metrics are derived from Google's Chrome UX Report (CrUX) field data. Figures represent the share of origins on each technology with "good" INP, computed at the origin level using the 75th-percentile user experience over a 28-day window. [S1][S2][S3]

• What: Share of origins per platform with "good" INP (≤200 ms). Thresholds: good ≤200 ms; needs improvement >200–500 ms; poor >500 ms. [S3]
• Who/When: CrUX aggregates anonymized, opted-in Chrome users' experiences; July 2025 dataset (trailing 28 days). [S2]
• How: HTTP Archive maps origins to technologies (CMSs, site builders, shopping platforms) and reports Core Web Vitals pass rates by tech. [S1][S4]
• Limitations: Platform samples vary in size and site mix; only Chrome users are included; results aggregate all templates and themes; origin-level aggregation can mask page-level variance. [S2][S4]

Findings: platform rankings and month-over-month change

Overall CMS ranking by "good" INP share, July 2025

• Squarespace: 96.07% [S1]
• Duda: 93.81% [S1]
• Wix: 87.52% [S1]
• WordPress: 86.77% [S1]
• Drupal: 86.14% [S1]
• Joomla: 84.47% [S1]

Shopping platforms vs CMSs (combined view), July 2025

• Squarespace: 96.07% [S1]
• BigCommerce: 95.29% [S1]
• Duda: 93.81% [S1]
• Shopify: 89.58% [S1]
• WooCommerce: 87.99% [S1]
• Wix: 87.52% [S1]
• WordPress: 86.77% [S1]
• Drupal: 86.14% [S1]
• Joomla: 84.47% [S1]

Shopping platform subset, July 2025

• BigCommerce: 95.29% [S1]
• Shopify: 89.58% [S1]
• WooCommerce: 87.99% [S1]

Month-over-month change (June→July 2025), "good" INP share

• Joomla: +1.12 points [S1]
• WordPress: +0.88 [S1]
• Wix: +0.70 [S1]
• Drupal: +0.64 [S1]
• Duda: +0.46 [S1]
• Squarespace: +0.22 [S1]

Additional context

• The top gap within CMSs is Squarespace vs WordPress (~9.3 points); Squarespace vs Duda is ~2.26 points. [S1]
• Among shopping platforms, BigCommerce leads Shopify by ~5.71 points and WooCommerce by ~7.30 points. [S1]
• WooCommerce and Wix are within ~0.47 points - effectively a tie in this dataset. [S1]

Interpretation and implications for marketers

• Likely: Hosted site builders (Squarespace, Duda) and BigCommerce show stronger default responsiveness, reducing the need for deep performance engineering to reach a "good" INP at scale. This aligns with controlled templates, managed asset pipelines, and limits on arbitrary scripting. [S1][S4]
• Likely: WordPress and WooCommerce can achieve comparable responsiveness but are sensitive to theme, plugin, and script load. Teams should budget JavaScript, defer non-critical work, and measure interaction latency on key flows (navigation, add-to-cart, filters). [S3]
• Likely: The improvements from June to July - especially for Joomla and WordPress - suggest platform-level updates or broader adoption of optimizations (for example, reduced long tasks, better event handling). Expect incremental gains rather than sudden shifts. [S1]
• Tentative: For new builds where team control over custom code is limited, Squarespace or BigCommerce reduce risk of exceeding the 200 ms threshold. Conversely, custom WordPress stacks need guardrails and continuous RUM to maintain INP as features accrete. [S1][S3]
• Tentative: On interactive pages (filters, carts, search), prioritize reducing main-thread blocking, splitting bundles, and avoiding heavy synchronous work triggered by input events, since INP reflects the longest meaningful interaction during the visit. [S3]

Contradictions and gaps

• Sample imbalance: The number and type of sites per platform differ and are not reported alongside the percentages in the public dashboard, which can bias comparisons. [S1][S4]
• Browser scope: CrUX only includes Chrome users; results may differ for other browsers or device distributions. [S2]
• Aggregation effects: Origin-level aggregation hides page-level hotspots; sites with a few slow interactive pages may still rate "good" at the origin. [S2]
• Unknowns: The dashboard does not attribute causes of month-over-month changes (for example, platform releases vs site-owner optimizations). [S1]

Sources

• [S1] HTTP Archive - Core Web Vitals Technology Report (Looker Studio; July 2025). https://lookerstudio.google.com/s/ioPF6YYC94Q
• [S2] Chrome UX Report (CrUX) methodology. https://developer.chrome.com/docs/web-platform/chrome-ux-report/ and https://web.dev/chrome-ux-report/
• [S3] Interaction to Next Paint (INP) definition, thresholds, and guidance. https://web.dev/inp/
• [S4] HTTP Archive methodology and technology classification notes. https://httparchive.org/about and https://github.com/HTTPArchive/legacy.httparchive.org/tree/master/docs

Notes on metric definitions

• INP "good" threshold: ≤200 ms; "needs improvement": >200–500 ms; "poor": >500 ms. [S3]
• Values are computed at the 75th percentile of user experiences per origin over a rolling 28-day window; CrUX data covers opted-in Chrome users only. [S2]