Third-party provider categories on React sites
Frameworks (98.1%), CDNs (89.7%), analytics (43.8%), tag managers (39.5%), font services (23.6%), video embeds (28.0%), and ad networks (9.6%) across 9,568 sites.
63.8% of React sites use RUM third-party technology categories, and 87% of those sites pass all three Core Web Vitals, against 76% of all React sites.
63.8% of React sites use RUM third-party technology categories, and 93% of those sites have a good LCP, against 85% of all React sites.
6.5% of React sites use performance plugin third-party technology categories, and 99% of those sites have a good INP, against 95% of all React sites.
63.8% of React sites use RUM third-party technology categories, and 96% of those sites have a good CLS, against 92% of all React sites.
Core Web Vitals pass rate
Sites with RUM third-party technology categories pass all three Core Web Vitals most often: 87%, against 76% of all React sites. The biggest gap is LCP, 93% against 85%.
Sites with RUM third-party technology categories have a good LCP most often: 93%, against 85% of all React sites. Sites with ecommerce runtime third-party categories have it least often, at 57%.
Sites with performance plugin third-party technology categories have a good INP most often: 99%, against 95% of all React sites. Sites with image CDN third-party categories have it least often, at 83%.
Sites with RUM third-party technology categories have a good CLS most often: 96%, against 92% of all React sites. Sites with personalization third-party categories have it least often, at 74%.
Third-party technology categories usage
Framework is the most used: 98.1% of React sites. RUM is 63.8% of React sites.
How third-party categories affect the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between RUM and ecommerce runtime sits in time to first byte (TTFB): 426 ms median for RUM against 1411 ms for ecommerce runtime. Overall median field LCP is 1.2s for RUM (TTFB 426 ms, load delay 456 ms, load duration 137 ms, render delay 154 ms) versus 2.3s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between RUM and ecommerce runtime sits in time to first byte (TTFB): 426 ms median for RUM against 1411 ms for ecommerce runtime. Overall median field LCP is 1.2s for RUM (TTFB 426 ms, load delay 456 ms, load duration 137 ms, render delay 154 ms) versus 2.3s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between RUM and ecommerce runtime sits in time to first byte (TTFB): 426 ms median for RUM against 1411 ms for ecommerce runtime. Overall median field LCP is 1.2s for RUM (TTFB 426 ms, load delay 456 ms, load duration 137 ms, render delay 154 ms) versus 2.3s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between RUM and ecommerce runtime sits in time to first byte (TTFB): 426 ms median for RUM against 1411 ms for ecommerce runtime. Overall median field LCP is 1.2s for RUM (TTFB 426 ms, load delay 456 ms, load duration 137 ms, render delay 154 ms) versus 2.3s for ecommerce runtime.
Third-party technology categories per platform
Wix sets the third-party technology categories to RUM on 100% of its sites, and 90% of Wix sites pass all three Core Web Vitals, against 76% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 54% of WordPress sites pass all three.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 94% of Wix sites have a good LCP, against 85% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 61% of WordPress sites have a good LCP.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 97% of Wix sites have a good INP, against 95% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 98% of WordPress sites have a good INP.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 98% of Wix sites have a good CLS, against 92% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 85% of WordPress sites have a good CLS.
Third-party technology categories or the platform
Does the platform explain the third-party technology categories difference?
Almost every site with RUM third-party technology categories is a Wix site, and almost every Wix site has RUM third-party technology categories, so the data can't tell RUM third-party technology categories and Wix apart. On WordPress, 43% of sites with RUM third-party technology categories pass all three Core Web Vitals, against 53% of WordPress sites with framework. Within WordPress, sites with RUM and framework pass all three about equally often.
Almost every site with RUM third-party technology categories is a Wix site, and almost every Wix site has RUM third-party technology categories, so the data can't tell RUM third-party technology categories and Wix apart. On WordPress, 49% of sites with RUM third-party technology categories have a good LCP, against 60% of WordPress sites with framework. Within WordPress, sites with RUM and framework have a good LCP about equally often.
On Wix, 97% of sites with framework third-party technology categories have a good INP, against 97% of Wix sites with CDN. Within Wix, sites with framework and CDN have a good INP about equally often. On WordPress, 99% of sites with performance plugin third-party technology categories have a good INP, against 98% of WordPress sites with framework. Within WordPress, sites with performance plugin and framework have a good INP about equally often.
Almost every site with RUM third-party technology categories is a Wix site, and almost every Wix site has RUM third-party technology categories, so the data can't tell RUM third-party technology categories and Wix apart. On WordPress, 78% of sites with RUM third-party technology categories have a good CLS, against 85% of WordPress sites with framework. Within WordPress, sites with RUM and framework have a good CLS about equally often.
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, 9,568 sites with third-party technology categories, October 2026). How we measured.