speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

jsr.io

https://jsr.io/

89 95 100 100 ✗AXE ✓CWV

Data from Aug 25, 2026, 4:36 PM UTC 13h old

Overall #1,138 Package Managers #5 · 1 measurement · since Aug 25, 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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

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

LCP 2.11 s good
INP site-wide 88 ms good
CLS 0 good

Scores

89
Performance
no change
95
Accessibility
no change
100
Best Practices
no change
100
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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.13 s — — 3.13 s 3.13 s
CLS Cumulative Layout Shift 0.013 — — 0.013 0.013
TBT Total Blocking Time 122 ms — — 122 ms 122 ms
FCP First Contentful Paint 2.60 s — — 2.60 s 2.60 s
Speed Index 2.60 s — — 2.60 s 2.60 s
TTFB Time to First Byte 493 ms — — 493 ms 493 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 3.13 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 187 ms
time to first byte 26 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.11 s good 80.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 88 ms good 93.6% good
CLS CWV 0 good 99.1% good
FCP 2.07 s needs-improvement 70.5% good
TTFB 1.03 s needs-improvement 67.1% good

Lab vs field

Lab LCP 3.13 s · field p75 2.11 s · real users are 0.67× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-22 2.29 s 88 ms 0 2.21 s 1.07 s
2026-08-15 2.11 s 85 ms 0 2.11 s 976 ms
2026-08-08 1.98 s 83 ms 0 2.04 s 789 ms
2026-08-01 1.93 s 305 ms 0 2.01 s 757 ms
2026-07-25 2.01 s 358 ms 0 2.12 s 880 ms
2026-07-18 2.03 s 360 ms 0 2.05 s 946 ms
2026-07-11 2.04 s 362 ms 0 2.07 s 986 ms
2026-07-04 2.14 s 80 ms 0 2.17 s 1.05 s
2026-06-27 2.04 s 79 ms 0 2.05 s 1.03 s
2026-06-20 2.29 s 79 ms 0 2.32 s 1.13 s
2026-06-13 2.16 s 88 ms 0 2.28 s 1.27 s
2026-06-06 2.07 s 195 ms 0 2.13 s 1.37 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 304 kB — — 304 kB 304 kB
Requests 26 — — 26 26
Third-party Weight 11.5 kB — — 11.5 kB 11.5 kB
Third-party CPU 4 ms — — 4 ms 4 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 194 kB · 3 req
script 61.3 kB · 15 req
stylesheet 31.8 kB · 1 req
document 9.6 kB · 1 req
image 6.2 kB · 4 req
other 1.2 kB · 2 req
third party 11.5 kB · 1 req

Third parties 1 entities

11.5 kB transferred, 4 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Cloudflare 11.5 kB · 4 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.44 s — — 2.44 s 2.44 s
Long Tasks 4 — — 4 4
DOM Elements 368 — — 368 368
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 13 — — 13 13
A11y Failures 2 — — 2 2
A11y Failing Nodes 9 — — 9 9

Main thread work

other 1.65 s
style layout 402 ms
script evaluation 243 ms
paint composite render 124 ms
parse HTML 22 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 1 rule, 542 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.

  • moderate region — All page content should be contained by landmarks 13 nodes

Accessibility failures 2 of 31 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. 8 nodes
  • 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 h3

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 25, 2026, 4:36 PM UTC 89 3.13 s 0.013 122 ms 304 kB 3/3 ±17 2,353 28.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show jsr.io'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://jsr.io/"></speedlify2-score>