WordPress third-party request share and the Core Web Vitals
51.2% of audited sites (32,405) keep third-party requests under 10% of total network traffic (100% good INP, 46ms median), while 12.1% have 25% to 50% third-party requests (99% good INP, 52ms median).
51.2% of WordPress sites use under 10% third-party requests third-party request share, and 100% of those sites have a good INP, against 100% of all WordPress sites.
12.1% of WordPress sites use 25% to 50% third-party requests third-party request share, and 78% of those sites have a good LCP, against 76% of all WordPress sites.
Core Web Vitals pass rate
Sites with under 10% third-party requests third-party request share have a good INP most often: 100%, against 100% of all WordPress sites. Sites with 25% to 50% third-party requests third-party share have it least often, at 99%.
Sites with 25% to 50% third-party requests third-party request share have a good LCP most often: 78%, against 76% of all WordPress sites. Sites with under 10% third-party requests third-party share have it least often, at 75%.
Third-party request share usage
Under 10% third-party requests is the most used: 51.2% of WordPress sites.
Third-party request share per framework
Vue sets the third-party request share to under 10% third-party requests on 64% of its sites, and 99% of Vue sites have a good INP, against 100% of all sites.
Vue sets the third-party request share to under 10% third-party requests on 64% of its sites, and 75% of Vue sites have a good LCP, against 76% of all sites.
Third-party request share or the framework
Does the framework explain the third-party request share difference?
On jQuery, 100% of sites with under 10% third-party requests third-party request share have a good INP, against 100% of jQuery sites with 10% to 25% third-party requests. Within jQuery, sites with under 10% third-party requests and 10% to 25% third-party requests have a good INP about equally often. On Vue, 100% of sites with under 10% third-party requests third-party request share have a good INP, against 99% of Vue sites with 10% to 25% third-party requests. Within Vue, sites with under 10% third-party requests and 10% to 25% third-party requests have a good INP about equally often.
On jQuery, 77% of sites with 25% to 50% third-party requests third-party request share have a good LCP, against 74% of jQuery sites with under 10% third-party requests. Within jQuery, sites with 25% to 50% third-party requests have a good LCP more often. On Vue, 76% of sites with 25% to 50% third-party requests third-party request share have a good LCP, against 74% of Vue sites with under 10% third-party requests. Within Vue, 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 32,405 sites (51.2%) keeping third-party traffic under 10% and 21,262 sites (33.6%) between 10% and 25%, good INP reaches 100% and 100% (46ms and 49ms median). When third parties account for 25% to 50% of requests (12.1%), good INP drops to 99% (52ms median), while the 3.1% over 50% sit at 99% good INP (50ms median).
Understanding third-party request share
Self-host fonts and static assets on your origin and defer marketing pixels until after first interaction so third-party requests stay below 25%. On WordPress, 51.2% of sites keep third-party requests under 10% (100% good INP) while 3.1% exceed 50% (99% good INP).
By Arjen Karel · 63,295 crawled WordPress sites (17,005 with desktop Chrome field data, October 2026). How we measured.