---
title: "jQuery Usage Statistics 2026: 64% of 9.58M Sites"
description: "jQuery runs on 64 percent of the mobile web, roughly 6.1 million sites, and those sites pass Core Web Vitals more often at 44.2 versus 39.0 percent."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster",
"description": "jQuery runs on 64 percent of the mobile web, roughly 6.1 million sites, and those sites pass Core Web Vitals more often at 44.2 versus 39.0 percent.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/jquery-core-web-vitals",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What percentage of websites still use jQuery in 2026?",
"acceptedAnswer": {
"@type": "Answer",
"text": "64% of the Mobile Web Still Runs jQuery - and Those Sites Are Faster."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery (May 2026). 9.58 million mobile origins with a CrUX reading, split by whether jQuery was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) 64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster
Data Study · Frameworks
# 64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 15, 2026 7 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals&text=64%25%20of%20the%20Mobile%20Web%20Still%20Runs%20jQuery%2C%20and%20Those%20Sites%20Are%20Faster)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals&title=64%25%20of%20the%20Mobile%20Web%20Still%20Runs%20jQuery%2C%20and%20Those%20Sites%20Are%20Faster)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [What the Data Covers](#what-the-data-covers "What the Data Covers")
- [Two-Thirds of the Mobile Web](#jquery-still-runs-two-thirds-of-the-mobile-web "Two-Thirds of the Mobile Web")
- [jQuery Sites Pass More Often](#the-sites-still-running-jquery-pass-more-often "jQuery Sites Pass More Often")
- [The Whole Gap Is Responsiveness](#the-whole-gap-is-responsiveness "The Whole Gap Is Responsiveness")
- [On Desktop It Flips](#on-desktop-the-ranking-flips "On Desktop It Flips")
- [The Lever Is Main-Thread Work](#the-lever-is-main-thread-work-not-the-library "The Lever Is Main-Thread Work")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals&text=64%25%20of%20the%20Mobile%20Web%20Still%20Runs%20jQuery%2C%20and%20Those%20Sites%20Are%20Faster)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fjquery-core-web-vitals&title=64%25%20of%20the%20Mobile%20Web%20Still%20Runs%20jQuery%2C%20and%20Those%20Sites%20Are%20Faster)
jQuery is supposed to be the slow legacy library you should drop. We checked 9.5 million sites: the ones still running it pass Core Web Vitals more often on mobile (44.2% vs 39.0%) than the ones without it, because the sites that dropped it moved to heavier frameworks.
Analysis of 9.58M origins · CrUX + HTTP Archive, May 2026
Part of our [JavaScript Framework Performance Statistics 2026](/resources/statistics/javascript-frameworks) research.
## Methodology & Source
Data source
HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery
Collection date
May 2026
Notes
9.58 million mobile origins with a CrUX reading, split by whether jQuery was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention.
## Key Findings
1. 1. [jQuery is still on roughly **64%** of mobile origins with a CrUX reading ( **6.1M of 9.6M**). It is nowhere near dead. ](#jquery-still-runs-two-thirds-of-the-mobile-web) Copy stat
2. 2. [Sites with jQuery pass Core Web Vitals on **44.2%** of mobile origins. Sites without it pass on **39.0%**. jQuery sites pass more often, by **5.2 points**. ](#the-sites-still-running-jquery-pass-more-often) Copy stat
3. 3. [The gap is mostly responsiveness. jQuery sites are good on INP **89.8%** of the time on mobile. Non-jQuery sites only **76.1%**, a **13.7-point** difference. ](#the-whole-gap-is-responsiveness) Copy stat
4. 4. [The reason is selection, not magic. The "no jQuery" population is dominated by React, Vue, Angular and other heavy single-page-app frameworks, which are exactly the sites that struggle with INP. ](#the-whole-gap-is-responsiveness) Copy stat
5. 5. [On desktop the picture reverses slightly. Non-jQuery sites edge ahead ( **56.9% vs 55.2%**), because the SPA responsiveness penalty disappears on desktop hardware. ](#on-desktop-the-ranking-flips) Copy stat
6. 6. [jQuery itself is not a Core Web Vitals problem. The work it does is small next to a full client-side framework, and the data shows no responsiveness penalty for using it. ](#the-lever-is-main-thread-work-not-the-library) Copy stat
## Summary
For a decade, 'still using jQuery?' has been a polite way of calling a website old and slow. The advice that follows is always the same: rip it out, move to a modern framework, get faster. The field data says the opposite. Across nine and a half million websites, the ones still shipping jQuery pass Google's Core Web Vitals more often on mobile than the ones that dropped it.
That matters because speed is not a vanity metric. It decides whether a visitor stays or leaves, whether a product page converts, and how a page ranks in Google. Core Web Vitals are Google's attempt to put numbers on the experience real people feel: how fast the main content loads, how quickly the page responds to a tap, and how much the layout jumps around while it settles. A site that falls short is losing users and search visibility every day.
These figures come from Google's real-user field data, the same Chrome UX Report readings Google itself uses to judge a page, not a lab test on a fast connection. They describe how actual Chrome users experienced these sites on their own phones.
## What the data covers
We started with HTTP Archive's technology detection, which records whether each site ships jQuery, and joined it to the Chrome UX Report, Google's field-data programme that collects Core Web Vitals from real Chrome users. That gave us 9.58 million mobile origins with a field reading, split into those that use jQuery and those that do not. Passing [Core Web Vitals](/resources/guides/complete-core-web-vitals-guide) means a site is good on all three metrics at once at the 75th percentile of its visitors: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. It is a high bar, set so that a passing site is fast for three-quarters of the people who load it, and these results are measured on mobile, where most of the web is browsed.
## jQuery still runs two-thirds of the mobile web
jQuery is supposed to be dead. It is not close. jQuery still runs on roughly 64% of the mobile origins in our dataset, about 6.1 million sites. It powers a huge share of the WordPress ecosystem, countless themes and plugins, and a long tail of classic server-rendered sites that have worked reliably for years.
That reach is what makes the comparison meaningful. Because jQuery sits under such a broad, ordinary cross-section of the web, comparing jQuery sites to the rest is really comparing two different architectural worlds, and the performance gap between them turns out to be large.
64%
Share of the mobile web that still runs jQuery in 2026, roughly 6.1 million origins. Copy stat
## The sites still running jQuery pass more often
On mobile, sites that use jQuery pass Core Web Vitals 44.2% of the time. Sites that do not use it pass only 39.0% of the time. The library everyone treats as a performance anchor is attached to the faster-passing half of the web, a 5.2-point advantage.
The reason is not that jQuery makes pages fast. It is that the sites which carry jQuery tend to be lightweight, server-rendered pages that build their HTML on the server and add a little interactivity on top. The sites that removed jQuery usually replaced it with something much heavier.
Core Web Vitals pass rate, jQuery vs no jQuery (mobile)
With jQuery
44.2%
Without jQuery
39%
Source: PageSpeed Matters analysis of 9.5 million origins with CrUX field data, May 2026.
The sites still running the old library pass 5.2 points more often than the ones that moved on.
Copy chart embed Download PNG
## The whole gap is responsiveness
Split the three metrics apart and the story sharpens. Loading is nearly identical between the two groups, and jQuery sites are slightly better on layout stability. Most of the gap lives in responsiveness. jQuery sites are good on Interaction to Next Paint 89.8% of the time on mobile; sites without it only 76.1%, a 13.7-point difference on the metric that measures how fast a page reacts to a tap.
This is selection, not sorcery. The no-jQuery population is dominated by React, Vue, Angular and other single-page-app frameworks, the stacks that, as our [framework study](/resources/data-studies/core-web-vitals-by-javascript-framework) shows, pass Core Web Vitals on barely a third of mobile sites. jQuery does comparatively little work: a bit of DOM manipulation, some event handling. A full framework downloads a large bundle, hydrates a component tree, and re-renders on every state change. On a mid-range phone that difference lands directly on [Interaction to Next Paint](/resources/data-studies/inp-device-gap).
So jQuery sites look good because the typical jQuery site never took on the responsiveness burden of a full client-side app. jQuery is the marker sitting on the lightweight side of the split, not the cause of the speed.
Good responsiveness (INP), jQuery vs no jQuery (mobile)
With jQuery
89.8%
Without jQuery
76.1%
Source: PageSpeed Matters analysis, mobile 75th-percentile field data, May 2026.
jQuery sites do not carry the thing that makes pages slow to respond: a heavy client-side JavaScript framework.
Copy chart embed Download PNG
## On desktop the ranking flips
The clearest proof that jQuery is not the variable comes from desktop. There the ranking reverses: non-jQuery sites pass slightly more often, 56.9% to 55.2%. On a desktop CPU the frameworks' responsiveness penalty disappears, good-INP runs 97% to 99% for everyone, so the no-jQuery group's other advantages, often newer and better-maintained builds, edge them ahead.
The library did not change between mobile and desktop. Only the hardware did. That is the signature of a main-thread-cost story: it only hurts where the processor is slow enough to feel it, which is the phone in your visitor's hand.
**Metric**
**With jQuery**
**Without jQuery**
CWV pass (mobile)
44.2%
39.0%
Good LCP (mobile)
68.7%
67.7%
Good INP (mobile)
89.8%
76.1%
Good CLS (mobile)
89.8%
85.4%
CWV pass (desktop)
55.2%
56.9%
Origins (mobile)
6,097,459
3,477,831
Buckets are non-exclusive. Per-metric good rates are among origins where the metric is reported.
## The lever is main-thread work, not the library
Do not rip out jQuery for Core Web Vitals reasons alone. The 44.2% versus 39.0% mobile pass rate, and the wider 89.8% versus 76.1% split on responsiveness, show no [Interaction to Next Paint](/resources/data-studies/inp-device-gap) penalty for using it. Removing the library will not improve INP unless you are also cutting main-thread work, and the teams that swapped it for a heavier single-page-app framework are the ones now passing on barely a third of mobile origins.
The durable lesson sits underneath the jQuery headline. Most of the gap is responsiveness, and responsiveness is a main-thread cost that only bites where the processor is slow, which is why the ranking flips to 56.9% versus 55.2% on desktop hardware. Fast is an outcome of shipping less JavaScript to the phone, so a team that treats client-side code as a budget and measures INP on real mobile devices will pass more often than one chasing the newest stack.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: 64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). 64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/jquery-core-web-vitals
Plain link Copy
64% of the Mobile Web Still Runs jQuery, and Those Sites Are Faster - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/jquery-core-web-vitals
Download the data (CSV)
## Frequently asked questions
### What percentage of websites still use jQuery in 2026?
64% of the Mobile Web Still Runs jQuery - and Those Sites Are Faster.
### How was this measured?
HTTP Archive technology detection (June 2026 crawl) joined to Chrome UX Report (CrUX) field data via BigQuery (May 2026). 9.58 million mobile origins with a CrUX reading, split by whether jQuery was detected, measured at the 75th percentile against the strict all-three Core Web Vitals pass convention.
## Related studies
- [CSS Bootstrap Passes Core Web Vitals on 45.7% of Mobile Sites. Tailwind Manages 36.8% ](/resources/data-studies/css-frameworks-core-web-vitals)
- [Third-Party Scripts Cookie Banners Cost 3.7 Points of LCP, Yet Those Sites Pass Core Web Vitals More Often ](/resources/data-studies/cookie-consent-banners-core-web-vitals)
- [Third-Party Scripts Live Chat Widgets Cost 9.5 Points of Good LCP ](/resources/data-studies/live-chat-widgets-core-web-vitals)
- [Frameworks The Fastest JavaScript Framework Isn't React, Vue or Angular - Alpine.js Passes 56.3% ](/resources/data-studies/core-web-vitals-by-javascript-framework)
- [Frameworks Astro Passes Core Web Vitals on 48% of Sites. Next.js Manages 29.3% ](/resources/data-studies/core-web-vitals-next-nuxt-astro)
- [Frameworks Static Site Generators Compared: Hugo and Jekyll Hit 90% Good LCP, Next.js 29% ](/resources/data-studies/static-site-generators-core-web-vitals)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)