Probably more than use React, by total domains alone. It's a bit like WordPress; so ubiquitous you forget it's even there, and with a long tail that will outlive many people reading this.
Approximately 64% of all websites—or roughly 67 million live domains—currently use jQuery.
We just had a T1 line blow up the entire US air control infrastructure, so I'll happily assume people are still using old garbage in critical workflows.
1: https://blog.jquery.com/2026/11/17/jquery-4-1-0-and-3-8-0-re...
First, modern vanilla JS APIs have been available for more than ten years. A browser without them is absolutely ancient.
And for the browsers that are truly that old, you can use nearly-weightless polyfills instead of jQuery.
hot take: we should not be supporting them.
(i get that this is a hard sell if you use your website to make money)
My only data point was my Blog felt significantly snappier on my 5 year old phone - especially on bad 4G connections - when i simply ditched jQuery and used Vanilla JS.
> The latest version of jQuery (v4.0.0) is 76.8 kB minified and 27.0 kB minified + gzipped.
Very much so. jQuery had 2 major selling points - (1) browser polyfills and (2) conciseness, as per their motto, "Write less, do more". It seems (2) has been largely forgotten since (1) has been rendered obsolete. Its idea of running functions on a collection often made scripts end up at one-third to one-half of the equivalent vanilla JS, which needs loops to do the same thing.
You'd probably usually chain that inside the callback. Instead of addClass('foo').hide(), you'd do el.classList.add('foo'); el.hidden = true; or something. It's not 1:1, but also it's not really that big a deal.
It's sort of the same sort of less-is-more mindset of jQuery but for the modern reactive-component model - intentionally small, allows SSR swapping when possible (like HTMX), and adds the layers of reactivity that can still only be reasonably done with frontend scripting.
And while most of the use cases for jQuery have long since died out with things like classList, querySelector, etc, I do feel there's probably value in a framework that focuses on minor enhancements to a site rather than being the backbone of the whole thing. Like if you want a React or Angular or Vue equivalent, something like jQuery would be a terrible choice, but a lot of sites are static ones where the only scripting needed would be for minor things like dropdown menus or slideshows, and I can see a modern, lean library like this being a decent choice there.