Unused JavaScript bytes on Wix sites
Of the JavaScript shipped, how much actually ran during load (used vs unused bytes, Chrome coverage).
72.0% of Wix sites use over 1.5 MB of unused JS unused JavaScript bytes, and 97% of those sites have a good INP, against 97% 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 over 1.5 MB of unused JS unused JavaScript bytes have a good INP most often: 97%, against 97% of all Wix sites. Sites with 850 KB to 1.5 MB of unused JS unused JS have it least often, at 97%.
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.
Unused JavaScript bytes per framework
React sets the unused JavaScript bytes to over 1.5 MB of unused JS on 72% of its sites, and 97% of React sites have a good INP, against 97% of all sites.
React sets the unused JavaScript bytes to over 1.5 MB of unused JS on 72% of its sites, 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, 97% of sites with over 1.5 MB of unused JS unused JavaScript bytes have a good INP, against 97% of React sites with 850 KB to 1.5 MB of unused JS. Within React, sites with over 1.5 MB of unused JS and 850 KB to 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 (5,333 with all devices Chrome field data, October 2026). How we measured.