JavaScript frameworks and UI libraries and the Core Web Vitals
jQuery (89.9%), Vue (7.6%), React (6.0%), Angular (2.1%), Alpine.js (1.7%), Next.js (1.1%), Nuxt (0.8%), and Svelte (0.3%): how frontend runtime choices correlate with passing all three Core Web Vitals.
0.2% of sites use htmx JavaScript frameworks, and 82% of those sites pass all three Core Web Vitals, against 70% of all sites.
0.2% of sites use htmx JavaScript frameworks, and 90% of those sites have a good LCP, against 82% of all sites.
0.2% of sites use htmx JavaScript frameworks, and 97% of those sites have a good INP, against 92% of all sites.
0.2% of sites use htmx JavaScript frameworks, and 93% of those sites have a good CLS, against 89% of all sites.
Core Web Vitals pass rate
Sites with htmx JavaScript frameworks pass all three Core Web Vitals most often: 82%, against 70% of all sites. The biggest gap is LCP, 90% against 82%.
Sites with htmx JavaScript frameworks have a good LCP most often: 90%, against 82% of all sites. Sites with Gatsby frameworks have it least often, at 62%.
Sites with htmx JavaScript frameworks have a good INP most often: 97%, against 92% of all sites. Sites with Next.js frameworks have it least often, at 60%.
Sites with htmx JavaScript frameworks have a good CLS most often: 93%, against 89% of all sites. Sites with Angular frameworks have it least often, at 58%.
JavaScript frameworks usage
JQuery is the most used: 89.9% of sites. Htmx is 0.2% of sites.
How JavaScript frameworks affect the four LCP phases
Across the four LCP sub-parts in Chrome's field data, the largest gap between htmx and Gatsby sits in resource load delay: 305 ms median for htmx against 516 ms for Gatsby. Overall median field LCP is 1.5s for htmx (TTFB 665 ms, load delay 305 ms, load duration 163 ms, render delay 270 ms) versus 2.3s for Gatsby.
Across the four LCP sub-parts in Chrome's field data, the largest gap between htmx and Gatsby sits in resource load delay: 305 ms median for htmx against 516 ms for Gatsby. Overall median field LCP is 1.5s for htmx (TTFB 665 ms, load delay 305 ms, load duration 163 ms, render delay 270 ms) versus 2.3s for Gatsby.
Across the four LCP sub-parts in Chrome's field data, the largest gap between htmx and Gatsby sits in resource load delay: 305 ms median for htmx against 516 ms for Gatsby. Overall median field LCP is 1.5s for htmx (TTFB 665 ms, load delay 305 ms, load duration 163 ms, render delay 270 ms) versus 2.3s for Gatsby.
Across the four LCP sub-parts in Chrome's field data, the largest gap between htmx and Gatsby sits in resource load delay: 305 ms median for htmx against 516 ms for Gatsby. Overall median field LCP is 1.5s for htmx (TTFB 665 ms, load delay 305 ms, load duration 163 ms, render delay 270 ms) versus 2.3s for Gatsby.
How JavaScript frameworks plays out per platform
What the field data shows when you isolate a single CMS or framework.
Shopify 4,023 stores Among Shopify stores loading a JS framework, 81.0% use jQuery, 24.2% use Vue, and 5.5% use Alpine.js.
Across 4,023 Shopify stores loading a detected JS framework, 81.0% load jQuery (80% pass all 3 CWV), 24.2% load Vue (79%), and 5.5% load Alpine.js (86%).
React & Next.js 9,570 sites 27.7% of React sites also load jQuery (54% CWV pass vs 74% across all React sites).
Across 9,570 React sites, 27.7% load jQuery alongside React and pass all three Core Web Vitals at 54% (20 points below the 74% React cohort pass rate).
By Arjen Karel · 210,902 crawled sites (126,761 with phone Chrome field data, 159,630 sites with JavaScript frameworks, October 2026). How we measured.