CMS performance

How the most-used CMS platforms perform on real-user Core Web Vitals data.

Field data PhoneDesktopAll Scope All sites October 2026 edition · All devices field outcomes
Metric LCP INP CLS FCP TTFB
1

At a glance the headline numbers for CMS performance

How the most-used CMS platforms perform on real-user Core Web Vitals data.

99.5%
Best: Squarespace
good INP
98.1%
Most used: WordPress
good INP
88.1%
Worst: TYPO3
good INP

Squarespace passes INP most often of any CMS. 99.5% of its sites pass. TYPO3 passes least at 88.1%. WordPress (the most-used CMS) sits at 98.1%. The gap is 11 percentage points.

The State of Web Vitals · October 2026 · 210,902 crawled sites · all devices field datacorewebvitals.io/state-of-cwv
2

The ranking sorted by INP at p75, fastest first

# CMS INP p75 Passing Sites
1 Wix 88ms 97.2%
5,827
2 Squarespace 93ms 99.5%
2,260
3 Joomla 96ms 95.3%
2,555
4 TYPO3 98ms 88.1%
104
5 Drupal 102ms 96.9%
3,361
6 WordPress 104ms 98.1%
65,509
7 Adobe Commerce 118ms 98.3%
1,096
8 Shopify 124ms 95.9%
8,575
The State of Web Vitals · October 2026 · 210,902 crawled sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing INP per CMS which group passes the INP most often

CMSSitesPassing INPp75
Ghost 0% 46 100% 87ms
Webflow 0% 20 100% 82ms
Squarespace 1.1% 2,260 100% 93ms
Adobe Commerce 0.5% 1,096 98% 118ms
WordPress 31.1% 65,509 98% 104ms
Wix 2.8% 5,827 97% 88ms
Drupal 1.6% 3,361 97% 102ms
Shopify 4.1% 8,575 96% 124ms
Joomla 1.2% 2,555 95% 96ms
TYPO3 0% 104 88% 98ms
Other / custom 0% 16 83% 139ms
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good INP (200ms at p75) · one value per site

100% of Squarespace sites pass INP. TYPO3 trails 12 points behind. computed

The State of Web Vitals · October 2026 · 210,902 crawled sites · all devices field datacorewebvitals.io/state-of-cwv
4

All five vitals at once the whole category without toggling - cell is the pass rate, small number the p75

LCP
INP
CLS
FCP
TTFB
WordPress 31.1%
702.7s
98104ms
890.03
592.3s
311.8s
Shopify 4.1%
961.7s
96124ms
940.02
951.1s
96513ms
Wix 2.8%
941.6s
9788ms
980.00
931.1s
82653ms
Drupal 1.6%
921.7s
97102ms
880.04
861.5s
67936ms
Joomla 1.2%
892.0s
9596ms
920.01
811.7s
551.1s
Squarespace 1.1%
892.1s
10093ms
900.04
861.5s
96541ms
Adobe Commerce 0.5%
782.4s
98118ms
740.11
692.0s
301.6s
TYPO3 0%
951.5s
8898ms
930.02
901.2s
72827ms
Ghost 0%
941.5s
10087ms
890.06
941.1s
82610ms
Webflow 0%
1001.6s
10082ms
950.03
951.2s
78591ms
Other / custom 0%
752.3s
83139ms
690.15
751.6s
47927ms
60%95%+ passing Cell: pass rate, small number = p75 · faded rows: under 100 sites

One row per CMS, one column per vital - the cell is the share of sites passing, the small number the p75. No toggling needed to see where the category actually differs.

Squarespace leads on INP: 100% of its sites pass. TYPO3 trails at 88%. computed

The State of Web Vitals · October 2026 · 210,902 crawled sites · all devices field datacorewebvitals.io/state-of-cwv
5

Why this matters for the Core Web Vitals, and where to start fixing it

The CMS decides a lot about your Core Web Vitals before you write a line of your own code. It controls the HTML that ships, the scripts and styles that load by default, and how images are handled. Two sites on the same platform can score very differently depending on the theme and plugins, but the platform sets the starting point and the ceiling for how much you can tune.

Start with what the platform loads that you do not need. Strip the default scripts and styles that come with themes and plugins, defer the JavaScript that is not needed for the first paint, and make sure images go out in modern formats at the right size. On script-heavy platforms the biggest wins are usually in cutting and deferring what loads on every page.

How does your CMS affect Core Web Vitals?

Among the most-used CMS platforms, Wix reaches a good INP on 97.2% of sites; Shopify on 95.9%.

Related signals CDN (7) → Frameworks (11) → 210,902 crawled sites with Chrome field data, representing millions of real page loads · How we measured