Third-party provider categories on WordPress and the Core Web Vitals
Frameworks (96.5%), CDNs (57.7%), analytics (60.9%), tag managers (55.1%), font services (58.8%), video embeds (43.5%), and ad networks (8.1%) across 63,295 sites.
6.2% of WordPress sites use personalization third-party technology categories, and 63% of those sites pass all three Core Web Vitals, against 60% of all WordPress sites.
1.1% of WordPress sites use cdp third-party technology categories, and 83% of those sites have a good LCP, against 76% of all WordPress sites.
21.0% of WordPress sites use ecommerce runtime third-party technology categories, and 100% of those sites have a good INP, against 100% of all WordPress sites.
0.7% of WordPress sites use scheduling third-party technology categories, and 83% of those sites have a good CLS, against 78% of all WordPress sites.
Core Web Vitals pass rate
Sites with personalization third-party technology categories pass all three Core Web Vitals most often: 63%, against 60% of all WordPress sites. The biggest gap is CLS, 79% against 78%.
Sites with cdp third-party technology categories have a good LCP most often: 83%, against 76% of all WordPress sites. Sites with ecommerce runtime third-party categories have it least often, at 60%.
Sites with ecommerce runtime third-party technology categories have a good INP most often: 100%, against 100% of all WordPress sites. Sites with push notifications third-party categories have it least often, at 98%.
Sites with scheduling third-party technology categories have a good CLS most often: 83%, against 78% of all WordPress sites. Sites with push notifications third-party categories have it least often, at 65%.
Third-party technology categories usage
CMS is the most used: 99.9% of WordPress sites. Personalization is 6.2% of WordPress 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 cdp and ecommerce runtime sits in time to first byte (TTFB): 735 ms median for cdp against 1400 ms for ecommerce runtime. Overall median field LCP is 1.6s for cdp (TTFB 735 ms, load delay 307 ms, load duration 147 ms, render delay 201 ms) versus 2.2s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between cdp and ecommerce runtime sits in time to first byte (TTFB): 735 ms median for cdp against 1400 ms for ecommerce runtime. Overall median field LCP is 1.6s for cdp (TTFB 735 ms, load delay 307 ms, load duration 147 ms, render delay 201 ms) versus 2.2s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between cdp and ecommerce runtime sits in time to first byte (TTFB): 735 ms median for cdp against 1400 ms for ecommerce runtime. Overall median field LCP is 1.6s for cdp (TTFB 735 ms, load delay 307 ms, load duration 147 ms, render delay 201 ms) versus 2.2s for ecommerce runtime.
Across the four LCP sub-parts in Chrome's field data, the largest gap between cdp and ecommerce runtime sits in time to first byte (TTFB): 735 ms median for cdp against 1400 ms for ecommerce runtime. Overall median field LCP is 1.6s for cdp (TTFB 735 ms, load delay 307 ms, load duration 147 ms, render delay 201 ms) versus 2.2s for ecommerce runtime.
Third-party technology categories per framework
On jQuery, 100% of sites use framework third-party technology categories, and 60% of jQuery sites pass all three Core Web Vitals, against 60% of all sites. On Vue, 100% of sites use framework, and 57% of Vue sites pass all three.
On jQuery, 100% of sites use framework third-party technology categories, and 75% of jQuery sites have a good LCP, against 76% of all sites. On Vue, 100% of sites use framework, and 75% of Vue sites have a good LCP.
On jQuery, 100% of sites use framework third-party technology categories, and 100% of jQuery sites have a good INP, against 100% of all sites. On Vue, 100% of sites use framework, and 99% of Vue sites have a good INP.
On jQuery, 100% of sites use framework third-party technology categories, and 77% of jQuery sites have a good CLS, against 78% of all sites. On Vue, 100% of sites use framework, and 75% of Vue sites have a good CLS.
Third-party technology categories or the framework
Does the framework explain the third-party technology categories difference?
On jQuery, 62% of sites with personalization third-party technology categories pass all three Core Web Vitals, against 60% of jQuery sites with CMS. Within jQuery, sites with personalization and CMS pass all three about equally often. On Vue, 49% of sites with personalization third-party technology categories pass all three Core Web Vitals, against 57% of Vue sites with CMS. Within Vue, sites with personalization and CMS pass all three about equally often.
On jQuery, 82% of sites with cdp third-party technology categories have a good LCP, against 75% of jQuery sites with CMS. Within jQuery, sites with cdp and CMS have a good LCP about equally often. On Vue, 75% of sites with CMS third-party technology categories have a good LCP, against 75% of Vue sites with framework. Within Vue, sites with CMS and framework have a good LCP about equally often.
On jQuery, 100% of sites with ecommerce runtime third-party technology categories have a good INP, against 100% of jQuery sites with CMS. Within jQuery, sites with ecommerce runtime and CMS have a good INP about equally often. On Vue, 100% of sites with ecommerce runtime third-party technology categories have a good INP, against 99% of Vue sites with CMS. Within Vue, sites with ecommerce runtime and CMS have a good INP about equally often.
On jQuery, 83% of sites with scheduling third-party technology categories have a good CLS, against 77% of jQuery sites with CMS. Within jQuery, sites with scheduling and CMS have a good CLS about equally often. On Vue, 74% of sites with CMS third-party technology categories have a good CLS, against 75% of Vue sites with framework. Within Vue, sites with CMS and framework have a good CLS about equally often.
By Arjen Karel · 63,295 crawled WordPress sites (17,005 with desktop Chrome field data, October 2026). How we measured.