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 81% of those sites pass all three Core Web Vitals, against 63% of all React sites.
63.8% of React sites use RUM third-party technology categories, and 89% of those sites have a good LCP, against 79% of all React sites.
8.3% of React sites use map embed third-party technology categories, and 100% of those sites have a good INP, against 99% of all React sites.
63.8% of React sites use RUM third-party technology categories, and 92% of those sites have a good CLS, against 80% of all React sites.
Core Web Vitals pass rate
Sites with RUM third-party technology categories pass all three Core Web Vitals most often: 81%, against 63% of all React sites. The biggest gap is CLS, 92% against 80%.
Sites with RUM third-party technology categories have a good LCP most often: 89%, against 79% of all React sites. Sites with ecommerce runtime third-party categories have it least often, at 59%.
Sites with map embed third-party technology categories have a good INP most often: 100%, against 99% of all React sites. Sites with session recording third-party categories have it least often, at 97%.
Sites with RUM third-party technology categories have a good CLS most often: 92%, against 80% of all React sites. Sites with personalization third-party categories have it least often, at 60%.
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): 434 ms median for RUM against 1348 ms for ecommerce runtime. Overall median field LCP is 1.3s for RUM (TTFB 434 ms, load delay 478 ms, load duration 218 ms, render delay 150 ms) versus 2.2s 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): 434 ms median for RUM against 1348 ms for ecommerce runtime. Overall median field LCP is 1.3s for RUM (TTFB 434 ms, load delay 478 ms, load duration 218 ms, render delay 150 ms) versus 2.2s 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): 434 ms median for RUM against 1348 ms for ecommerce runtime. Overall median field LCP is 1.3s for RUM (TTFB 434 ms, load delay 478 ms, load duration 218 ms, render delay 150 ms) versus 2.2s 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): 434 ms median for RUM against 1348 ms for ecommerce runtime. Overall median field LCP is 1.3s for RUM (TTFB 434 ms, load delay 478 ms, load duration 218 ms, render delay 150 ms) versus 2.2s for ecommerce runtime.
Third-party technology categories per platform
Wix sets the third-party technology categories to RUM on 100% of its sites, and 88% of Wix sites pass all three Core Web Vitals, against 63% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 51% of WordPress sites pass all three.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 92% of Wix sites have a good LCP, against 79% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 66% of WordPress sites have a good LCP.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 100% of Wix sites have a good INP, against 99% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 100% of WordPress sites have a good INP.
Wix sets the third-party technology categories to RUM on 100% of its sites, and 96% of Wix sites have a good CLS, against 80% of all sites. WordPress sets the third-party technology categories to CMS on 100% of its sites, and 75% 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, 50% of sites with framework third-party technology categories pass all three Core Web Vitals, against 49% of WordPress sites with CDN. Within WordPress, sites with framework and CDN 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, 57% of sites with RUM third-party technology categories have a good LCP, against 65% of WordPress sites with framework. Within WordPress, sites with RUM and framework have a good LCP about equally often.
On Wix, 100% of sites with framework third-party technology categories have a good INP, against 100% of Wix sites with CDN. Within Wix, sites with framework and CDN have a good INP about equally often. On WordPress, 100% of sites with map embed third-party technology categories have a good INP, against 100% of WordPress sites with framework. Within WordPress, sites with map embed 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, 87% of sites with RUM third-party technology categories have a good CLS, against 75% 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 (1,979 with desktop Chrome field data, 9,568 sites with third-party technology categories, October 2026). How we measured.