The State of Web Vitals

Total JavaScript payload on Wix sites

How many scripts the page runs and their over-the-wire weight.

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · Wix sites only
Wix Scoped to 5,623 sites out of 203,892 analyzed (cms) Compare with all sites →
INP Interaction LCP Loading

58.6% of Wix sites use 550 KB to 1 MB of JavaScript total JavaScript payload, and 97% of those sites have a good INP, against 96% of all Wix sites.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

Core Web Vitals pass rate

Sites with 550 KB to 1 MB of JavaScript total JavaScript payload have a good INP most often: 97%, against 96% of all Wix sites. Sites with over 1 MB of JavaScript JS payload have it least often, at 96%.

SitesGood, needs improvement, poor INPMedian
All Wix sites3,07796%79ms
550 KB to 1 MB 58.6%1,83897%74ms
Over 1 MB 38.7%1,16096%86ms
250 to 550 KB 2.6%7892%70ms
Under 250 KBno field data
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Total JavaScript payload usage

550 KB to 1 MB of JavaScript is the most used: 58.6% of Wix sites.

550 KB to 1 MB 58.6% Over 1 MB 38.7%
550 KB to 1 MB 58.6% Over 1 MB 38.7% 250 to 550 KB 2.6% Under 250 KB <0.1%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Total JavaScript payload per framework

React sets the total JavaScript payload to 550 KB to 1 MB of JavaScript on 59% of its sites, and 96% of React sites have a good INP, against 96% of all sites.

FrameworkTotal JavaScript payload on its sitesGood INP
All Wix sites 5,621 sites550 KB to 1 MB 59%Over 1 MB 39%96%
React 5,620 sites550 KB to 1 MB 59%Over 1 MB 39%96%
550 KB to 1 MB Over 1 MB 250 to 550 KB Under 250 KB
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Total JavaScript payload or the framework

Does the framework explain the total JavaScript payload difference?

On React, 97% of sites with 550 KB to 1 MB of JavaScript total JavaScript payload have a good INP, against 96% of React sites with over 1 MB of JavaScript. Within React, sites with 550 KB to 1 MB of JavaScript and over 1 MB of JavaScript have a good INP about equally often.

Why total script weight taxes main-thread responsiveness

Every kilobyte of JavaScript downloaded over the network must be decompressed, parsed, compiled, and evaluated on the CPU. Across 147 sites (2.6%) shipping 250 to 550 KB of scripts, 92% pass field INP at an 70ms median, whereas the 38.7% (2,176) shipping over 1 MB drop to 96% good INP (86ms median).

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Understanding total JavaScript payload

Keep total JavaScript transfer below 550 KB by route-splitting framework bundles, auditing tag-manager containers, and loading interactive widgets on demand. Across all audited sites, 2.6% transfer 250 to 550 KB (92% good INP, 70ms median) versus 38.7% above 1 MB (96% good INP, 86ms median).

Go fix it 14 methods to defer JavaScript → Reduce unused JavaScript → JavaScript priority levels →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 3,077 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals DOM size → Page weight & requests → Image source mix → Stylesheet loading mix → By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, October 2026) · How we measured