speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

jquery.com

https://jquery.com/

99 86 88 92 ✗AXE ✓CWV

Data from Aug 27, 2026, 6:58 PM UTC old

Overall #1,301 Developer Tooling #44 Frameworks and Libraries #10 · 1 measurement · since Aug 27, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

WordPress 7.1 Built with WordPress 7.1
Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-29 → 2026-08-25). This is what Google measures you on.

LCP 1.36 s good
INP 102 ms good
CLS 0 good

Scores

99
Performance
no change
86
Accessibility
no change
88
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0.1% of pixels differ — they are nearly identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.67 s — — 1.67 s 1.67 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.67 s — — 1.67 s 1.67 s
Speed Index 1.67 s — — 1.67 s 1.67 s
TTFB Time to First Byte 612 ms — — 612 ms 612 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.67 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 108 ms
time to first byte 31 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-29 → 2026-08-25). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.36 s good 89.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 102 ms good 91.6% good
CLS CWV 0 good 99.2% good
FCP 1.37 s good 83.8% good
TTFB 618 ms good 80.9% good

Lab vs field LCP

Lab 1.67 s
Field p75 1.36 s

The lab LCP is 1.22× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 1.36 s 101 ms 0 1.38 s 625 ms
2026-08-15 1.42 s 103 ms 0 1.43 s 605 ms
2026-08-08 1.47 s 107 ms 0 1.48 s 603 ms
2026-08-01 1.50 s 103 ms 0 1.51 s 624 ms
2026-07-25 1.49 s 100 ms 0 1.49 s 630 ms
2026-07-18 1.39 s 93 ms 0 1.41 s 607 ms
2026-07-11 1.44 s 92 ms 0 1.46 s 636 ms
2026-07-04 1.46 s 92 ms 0 1.49 s 645 ms
2026-06-27 1.47 s 92 ms 0 1.50 s 670 ms
2026-06-20 1.52 s 93 ms 0 1.55 s 703 ms
2026-06-13 1.47 s 97 ms 0 1.50 s 698 ms
2026-06-06 1.47 s 93 ms 0 1.48 s 704 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 184 kB — — 184 kB 184 kB
Requests 20 — — 20 20
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 63.6 kB · 9 req
font 60.0 kB · 2 req
script 31.8 kB · 3 req
stylesheet 19.2 kB · 3 req
document 7.4 kB · 1 req
third party 182 kB · 18 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 393 ms — — 393 ms 393 ms
Long Tasks 1 — — 1 1
DOM Elements 310 — — 310 310
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 29 — — 29 29
A11y Failures 4 — — 4 4
A11y Failing Nodes 22 — — 22 22

Main thread work

style layout 168 ms
other 129 ms
script evaluation 40 ms
paint composite render 37 ms
parse HTML 13 ms
script parse compile 7 ms

Axe violations axe-core 4.13.0, full rule set

29 violating nodes across 6 rules, 418 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 17 nodes
  • moderate region — All page content should be contained by landmarks 6 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 3 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 4 of 28 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 17 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 2 console errors

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 27, 2026, 6:58 PM UTC 99 1.67 s 0.001 0 ms 184 kB 3/3 ±0 3,035 21.3s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show jquery.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://jquery.com/"></speedlify2-score>