The State of Web Vitals

Script loading attributes on Wix sites

2.0% of audited sites (115) still execute render-blocking synchronous scripts and drop to 84% good LCP (1.5s median), compared to 94% good LCP on sites using async (99.9%) and 92% on ES modules (1.9%).

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

100.0% of Wix sites use inline scripts script loading strategy, and 94% of those sites have a good LCP, against 94% of all Wix sites.

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

Core Web Vitals pass rate

Sites with inline scripts script loading strategy have a good LCP most often: 94%, against 94% of all Wix sites. Sites with render-blocking scripts script loading have it least often, at 84%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites5,33394%1.2s
Inline <script> blocks 100.0%5,33394%1.2s
Legacy fallback (<script nomodule>) 99.9%5,33294%1.2s
Async (<script async>) 99.9%5,33294%1.2s
Dynamic / script-injected 99.9%5,33094%1.2s
Deferred (<script defer>) 99.9%5,32994%1.2s
ES module (<script type="module">) 1.9%10292%1.4s
Render-blocking (<script src>) 2.0%11184%1.5s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Script loading strategy usage

Inline scripts is the most used: 100.0% of Wix sites.

Sites using each option (sites can use more than one) 5,621 sites
Inline <script> blocks 100.0% Legacy fallback (<script nomodule>) 99.9% Async (<script async>) 99.9% Dynamic / script-injected 99.9% Deferred (<script defer>) 99.9%
Inline <script> blocks 100.0% Legacy fallback (<script nomodule>) 99.9% Async (<script async>) 99.9% Dynamic / script-injected 99.9% Deferred (<script defer>) 99.9% Render-blocking (<script src>) 2.0% ES module (<script type="module">) 1.9%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by script loading attribute

Across the four LCP sub-parts in Chrome's field data, the largest gap between inline scripts and render-blocking scripts sits in resource load delay: 455 ms median for inline scripts against 636 ms for render-blocking scripts. Overall median field LCP is 1.2s for inline scripts (TTFB 419 ms, load delay 455 ms, load duration 137 ms, render delay 151 ms) versus 1.5s for render-blocking scripts.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 3,945419 ms455 ms455 mslab 455 ms1.2s
Inline <script> blocks 3,945419 ms455 ms455 mslab 455 ms1.2s
Async (<script async>) 3,945419 ms455 ms455 mslab 455 ms1.2s
Legacy fallback (<script nomodule>) 3,945419 ms455 ms455 mslab 455 ms1.2s
Dynamic / script-injected 3,942419 ms455 ms455 mslab 455 ms1.2s
Deferred (<script defer>) 3,942419 ms455 ms455 mslab 455 ms1.2s
ES module (<script type="module">) 81458 ms508 ms180 ms508 mslab 508 ms1.4s
Render-blocking (<script src>) 86537 ms636 ms168 ms636 mslab 636 ms1.5s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Script loading strategy per framework

React sets the script loading strategy to inline scripts on 100% of its sites, and 94% of React sites have a good LCP, against 94% of all sites.

FrameworkScript loading strategy on its sitesGood LCP
All Wix sites 5,621 sitesInline <script> blocks 100%Legacy fallback (<script nomodule>) 100%Async (<script async>) 100%Dynamic / script-injected 100%Deferred (<script defer>) 100%94%
React 5,620 sitesLegacy fallback (<script nomodule>) 100%Async (<script async>) 100%Inline <script> blocks 100%Deferred (<script defer>) 100%Dynamic / script-injected 100%94%
Inline <script> blocks Legacy fallback (<script nomodule>) Async (<script async>) Dynamic / script-injected Deferred (<script defer>) Render-blocking (<script src>) ES module (<script type="module">)
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Script loading attributes or the framework

Does the framework explain the script loading strategy difference?

Almost every site with inline scripts script loading strategy is a React site, and almost every React site has inline scripts script loading strategy, so the data can't tell inline scripts script loading strategy and React apart.

How synchronous blocking <script> tags halt the HTML parser before LCP

When the HTML parser hits a synchronous <script src> tag without async, defer, or type="module", it must pause DOM construction, wait for the network download, and execute the script before painting. Across 115 sites (2.0%) with render-blocking scripts, good LCP drops to 84% (1.5s median). Sites loading scripts with async (99.9%), defer (99.9%), or type="module" (1.9%) reach 94%, 94%, and 92% good LCP.

The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding script loading attributes

Add defer or type="module" to all first-party application scripts and async to independent third-party tags so zero synchronous <script src> tags block the HTML parser in <head>. Across all audited sites, 2.0% ship render-blocking scripts (84% good LCP, 1.5s median).

Go fix it async vs defer → 14 methods to defer JavaScript → Head vs footer JavaScript →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 5,333 with all devices field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Cookies per site → Uses @import → DOM size → Images per page → By Arjen Karel · 5,621 crawled Wix sites (5,333 with all devices Chrome field data, October 2026) · How we measured