Unused JavaScript bytes on Wix sites
Of the JavaScript shipped, how much actually ran during load (used vs unused bytes, Chrome coverage).
27.9% of Wix sites use 850 KB to 1.5 MB of unused JS unused JavaScript bytes, and 96% of those sites have a good INP, against 96% of all Wix sites.
27.9% of Wix sites use 850 KB to 1.5 MB of unused JS unused JavaScript bytes, and 97% of those sites have a good LCP, against 94% of all Wix sites.
Core Web Vitals pass rate
Sites with 850 KB to 1.5 MB of unused JS unused JavaScript bytes have a good INP most often: 96%, against 96% of all Wix sites. Sites with over 1.5 MB of unused JS unused JS have it least often, at 96%.
Sites with 850 KB to 1.5 MB of unused JS unused JavaScript bytes have a good LCP most often: 97%, against 94% of all Wix sites. Sites with over 1.5 MB of unused JS unused JS have it least often, at 93%.
Unused JavaScript bytes usage
Over 1.5 MB of unused JS is the most used: 72.0% of Wix sites. 850 KB to 1.5 MB of unused JS is 27.9% of Wix sites.
Unused JavaScript bytes per framework
On React, 72% of sites use over 1.5 MB of unused JS unused JavaScript bytes, and 96% of React sites have a good INP, against 96% of all sites.
On React, 72% of sites use over 1.5 MB of unused JS unused JavaScript bytes, and 94% of React sites have a good LCP, against 94% of all sites.
Unused JavaScript bytes or the framework
Does the framework explain the unused JavaScript bytes difference?
On React, 96% of sites with 850 KB to 1.5 MB of unused JS unused JavaScript bytes have a good INP, against 96% of React sites with over 1.5 MB of unused JS. Within React, sites with 850 KB to 1.5 MB of unused JS and over 1.5 MB of unused JS have a good INP about equally often.
On React, 97% of sites with 850 KB to 1.5 MB of unused JS unused JavaScript bytes have a good LCP, against 93% of React sites with over 1.5 MB of unused JS. Within React, sites with 850 KB to 1.5 MB of unused JS have a good LCP more often.
By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, October 2026). How we measured.