The State of Web Vitals

Subresource network protocols on Wix sites

HTTP/2 (100.0%), HTTP/3 QUIC (99.9%), and legacy HTTP/1.1 (99.9%) across all page subrequests: how connection protocols move Largest Contentful Paint.

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

100.0% of Wix sites use HTTP/2 subresource network protocols, and 92% of those sites have a good LCP, against 92% of all Wix sites.

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

LCP pass rate

Sites with HTTP/2 subresource network protocols have a good LCP most often: 92%, against 92% of all Wix sites. Sites with HTTP/1.1 network protocols have it least often, at 92%.

SitesGood, needs improvement, poor LCPMedian
All Wix sites72892%1.2s
HTTP/2 (h2) 100.0%72892%1.2s
HTTP/3 (QUIC / h3) 99.9%72892%1.2s
HTTP/1.1 99.9%72892%1.2s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Subresource network protocols usage

HTTP/2 is the most used: 100.0% of Wix sites.

Sites using each option (sites can use more than one) 5,621 sites
HTTP/2 (h2) 100.0% HTTP/3 (QUIC / h3) 99.9% HTTP/1.1 99.9%
HTTP/2 (h2) 100.0% HTTP/3 (QUIC / h3) 99.9% HTTP/1.1 99.9%
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

How subresource network protocols affect the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between HTTP/2 and HTTP/1.1 sits in time to first byte (TTFB): 343 ms median for HTTP/2 against 343 ms for HTTP/1.1. Overall median field LCP is 1.2s for HTTP/2 (TTFB 343 ms, load delay 478 ms, load duration 259 ms, render delay 137 ms) versus 1.2s for HTTP/1.1.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All Wix sites 376343 ms478 ms259 ms137 ms478 mslab 462 ms1.2s
HTTP/2 (h2) 376343 ms478 ms259 ms137 ms478 mslab 462 ms1.2s
HTTP/3 (QUIC / h3) 376343 ms478 ms259 ms137 ms478 mslab 462 ms1.2s
HTTP/1.1 376343 ms478 ms259 ms137 ms478 mslab 462 ms1.2s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Subresource network protocols per framework

React sets the subresource network protocols to HTTP/2 on 100% of its sites, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkSubresource network protocols on its sitesGood LCP
All Wix sites 5,621 sitesHTTP/2 (h2) 100%HTTP/3 (QUIC / h3) 100%HTTP/1.1 100%92%
React 5,620 sitesHTTP/2 (h2) 100%HTTP/3 (QUIC / h3) 100%HTTP/1.1 100%92%
HTTP/2 (h2) HTTP/3 (QUIC / h3) HTTP/1.1
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

Subresource network protocols or the framework

Does the framework explain the subresource network protocols difference?

Almost every site with HTTP/2 subresource network protocols is a React site, and almost every React site has HTTP/2 subresource network protocols, so the data can't tell HTTP/2 subresource network protocols and React apart.

Why most pages mix HTTP/2, HTTP/3, and HTTP/1.1 in a single load

While a page's HTML document uses a single connection, its subresources come from first-party CDNs, font hosts, and third-party scripts. Across 189,798 sites, 100.0% load subresources over HTTP/2 (92% good LCP), 99.9% negotiate HTTP/3 on at least one origin (92% good LCP), and 99.9% still make at least one legacy HTTP/1.1 request (92% good LCP).

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

Understanding subresource network protocols

Serve all first-party static assets over HTTP/2 and HTTP/3 via a modern CDN, and audit third-party scripts or unproxied asset hosts that still fall back to HTTP/1.1 (99.9% of sites). HTTP/1.1 origins cannot multiplex concurrent requests over a single connection, adding head-of-line blocking when multiple assets share that domain.

Go fix it Third-party domains → Configure Cloudflare for passing the Core Web Vitals →
The State of Web Vitals · October 2026 · Wix: 5,621 crawled sites · 728 with desktop field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals Connection hints → Main CDN → HTTP protocol → HTML compression → By Arjen Karel · 5,621 crawled Wix sites (728 with desktop Chrome field data, October 2026) · How we measured