Third-party request share on React sites
15.0% of audited sites (1,433) keep third-party requests under 10% of total network traffic (99% good INP, 49ms median), while 57.3% have 25% to 50% third-party requests (99% good INP, 43ms median).
14.7% of React sites use over 50% third-party requests third-party request share, and 100% of those sites have a good INP, against 99% of all React sites.
57.3% of React sites use 25% to 50% third-party requests third-party request share, and 87% of those sites have a good LCP, against 79% of all React sites.
Core Web Vitals pass rate
Sites with over 50% third-party requests third-party request share have a good INP most often: 100%, against 99% of all React sites. Sites with 10% to 25% third-party requests third-party share have it least often, at 98%.
Sites with 25% to 50% third-party requests third-party request share have a good LCP most often: 87%, against 79% of all React sites. Sites with under 10% third-party requests third-party share have it least often, at 69%.
Third-party request share usage
25% to 50% third-party requests is the most used: 57.3% of React sites. Over 50% third-party requests is 14.7% of React sites.
Third-party request share per platform
On Wix, 85% of sites use 25% to 50% third-party requests third-party request share, and 100% of Wix sites have a good INP, against 99% of all sites. On WordPress, 54% of sites use under 10% third-party requests, and 100% of WordPress sites have a good INP.
On Wix, 85% of sites use 25% to 50% third-party requests third-party request share, and 92% of Wix sites have a good LCP, against 79% of all sites. On WordPress, 54% of sites use under 10% third-party requests, and 66% of WordPress sites have a good LCP.
Third-party request share or the platform
Does the platform explain the third-party request share difference?
On Wix, 100% of sites with over 50% third-party requests third-party request share have a good INP, against 100% of Wix sites with 25% to 50% third-party requests. Within Wix, sites with over 50% third-party requests and 25% to 50% third-party requests have a good INP about equally often. On WordPress, 100% of sites with 25% to 50% third-party requests third-party request share have a good INP, against 100% of WordPress sites with under 10% third-party requests. Within WordPress, sites with 25% to 50% third-party requests and under 10% third-party requests have a good INP about equally often.
On Wix, 93% of sites with 25% to 50% third-party requests third-party request share have a good LCP, against 85% of Wix sites with over 50% third-party requests. Within Wix, sites with 25% to 50% third-party requests and over 50% third-party requests have a good LCP about equally often. On WordPress, 68% of sites with 25% to 50% third-party requests third-party request share have a good LCP, against 66% of WordPress sites with under 10% third-party requests. Within WordPress, sites with 25% to 50% third-party requests and under 10% third-party requests have a good LCP about equally often.
How external request share shapes main-thread contention and INP
Third-party request share measures the fraction of page requests served from external origins. Across 1,433 sites (15.0%) keeping third-party traffic under 10% and 1,249 sites (13.1%) between 10% and 25%, good INP reaches 99% and 98% (49ms and 55ms median). When third parties account for 25% to 50% of requests (57.3%), good INP drops to 99% (43ms median), while the 14.7% over 50% sit at 100% good INP (57ms median).
Understanding third-party request share
Keep third-party requests under 25% of total page traffic by self-hosting fonts and media on your primary CDN and consolidating tag-manager pixels into server-side endpoints. Across all audited sites, 15.0% stay under 10% third-party requests (99% good INP) and 57.3% sit at 25% to 50% (99% good INP).
By Arjen Karel · 9,570 crawled React sites (1,979 with desktop Chrome field data, October 2026). How we measured.