Frameworks performance
How JavaScript frameworks score across LCP, INP and CLS.
At a glance the headline numbers for Frameworks performance
How JavaScript frameworks score across LCP, INP and CLS.
The ranking sorted by INP at p75, fastest first
| # | Framework | INP p75 | Passing | Sites | |
|---|---|---|---|---|---|
| 1 | htmx | 60ms | 100.0% | 141 | |
| 2 | jQuery | 62ms | 99.4% | 67,958 | |
| 3 | React | 65ms | 98.7% | 4,396 | |
| 4 | Alpine.js | 66ms | 99.7% | 1,306 | |
| 5 | Vue | 76ms | 99.0% | 5,677 | |
| 6 | Svelte | 86ms | 99.1% | 219 | |
| 7 | Nuxt | 101ms | 98.3% | 628 | |
| 8 | Angular | 104ms | 97.4% | 1,658 | |
| 9 | Next.js | 112ms | 93.5% | 854 | |
| 10 | Gatsby | 130ms | 82.6% | 105 |
Passing INP per framework which group passes the INP most often
100% of htmx sites pass INP. Gatsby trails 17 points behind. computed
All five vitals at once the whole category without toggling - cell is the pass rate, small number the p75
One row per framework, one column per vital - the cell is the share of sites passing, the small number the p75. No toggling needed to see where the category actually differs.
htmx leads on INP: 100% of its sites pass. Gatsby trails at 83%. computed
Why this matters for the Core Web Vitals, and where to start fixing it
A JavaScript framework shapes how much code runs in the browser to put your page on the screen. Some render on the server and ship light; others send a large bundle and rebuild the page on the client, which lands on the main thread and shows up in INP. The framework is not destiny, but its defaults and how you use them decide how much JavaScript the visitor has to pay for.
Start by looking at what ships to the browser and when it runs. Render on the server where you can, split the bundle so each page only loads what it needs, and defer the work that is not required for the first interaction. Framework JavaScript runs on the main thread, so the less of it the browser has to execute, the better INP gets.
How does your framework affect Core Web Vitals?
Among the JavaScript frameworks, htmx reaches a good INP on 100.0% of sites; Gatsby on 82.6%.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.