The State of Web Vitals

JS framework

The JavaScript framework detected on the site.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · Phone field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for JS framework

The JavaScript framework detected on the site.

11
Categories
In the distribution
82.0%
Fleet share
Top: jquery
68.2%
Sites with any
Of jquery

jQuery appears on 82.0% of sites.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

The JS framework mix who uses what, and how fast each group loads

Median INP (sites using feature)
0
100ms
200ms
300ms
400ms
500ms
Jquery96ms82% of sites
Vue114ms7% of sites
React90ms5% of sites
Angular139ms2% of sites
Alpine104ms2% of sites
Next js171ms1% of sites
Nuxt136ms1% of sites
Svelte119ms0% of sites
Htmx102ms0% of sites
Gatsby129ms0% of sites
Remix147ms0% of sites
VariantShare of sitesMedian
Jquery
82%
96ms
Vue
7%
114ms
React
5%
90ms
Angular
2%
139ms
Alpine
2%
104ms
Next js
1%
171ms
Nuxt
1%
136ms
Svelte
0%
119ms
Htmx
0%
102ms
Gatsby
0%
129ms
Remix
0%
147ms

JS framework. On the fleet: 82.0% jquery, 6.8% vue, 5.4% react. 68.2% of sites use at least one jquery.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3

Why this matters for the Core Web Vitals, and where to start fixing it

A JavaScript framework moves work onto the visitor's main thread. Hydration is the toll: the server-rendered HTML arrives fast, then the framework rebuilds its component tree in the browser before interactions fully work. That window is where frameworks pay INP.

The rendering mode decides the bill. Static or server-rendered output with islands of interactivity costs little. Full client-side rendering makes every visitor's device build the page from scratch. The framework pages compare them on field data.

How does this affect the Core Web Vitals?

JS framework correlates with the INP. With jQuery, 95% of sites pass the INP. With Next.js, 60% do. The causal link is weak: the choice mostly marks what kind of site made it.

Go fix it Framework standings → JavaScript priority levels → Yield to the main thread →
Related signals Consent platforms → Ad networks on page → Third-party categories → Optimization plugins → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured