speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

a11yproject.com

https://www.a11yproject.com/

99 100 100 100 ✓CWV 0AXE

Data from Aug 21, 2026, 9:38 AM UTC — 9h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 9h

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.

Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.49 s good
INP — no data
CLS 0 good

Scores

99
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

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

What LCP is made of

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

element render delay 180 ms
time to first byte 29 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.49 s good 96.7% good
CLS CWV 0 good 95% good
FCP 1.27 s good 89.9% good
TTFB 813 ms needs-improvement 73.8% good

Lab vs field

Lab LCP 2.13 s · field p75 1.49 s · real users are 0.7× 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-15 1.36 s — 0 1.15 s 757 ms
2026-08-08 1.41 s — 0 1.20 s 806 ms
2026-08-01 1.36 s — 0 1.15 s 786 ms
2026-07-25 1.42 s — 0 1.15 s 796 ms
2026-07-18 1.55 s — 0 1.35 s 848 ms
2026-07-11 1.25 s — 0 1.01 s 687 ms
2026-07-04 1.28 s — 0 973 ms 615 ms
2026-06-27 1.25 s — 0 916 ms 514 ms
2026-06-20 1.23 s — 0 916 ms 526 ms
2026-06-13 1.26 s — 0 995 ms 552 ms
2026-06-06 1.23 s — 0 1.01 s 655 ms
2026-05-30 1.31 s — 0 1.06 s 691 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 266.3 kB — — 266.3 kB 266.3 kB
Requests 15 — — 15 15
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 11.4 kB — — 11.4 kB 11.4 kB

By resource type

image 194.4 kB · 5 req
font 43.7 kB · 2 req
stylesheet 14.1 kB · 1 req
document 8.8 kB · 1 req
other 2.9 kB · 3 req
script 2.3 kB · 3 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 348 ms — — 348 ms 348 ms
Long Tasks 0 — — 0 0
DOM Elements 250 — — 250 250
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 — — 0 0
A11y Failures 0 — — 0 0
A11y Failing Nodes 0 — — 0 0

Main thread work

other 159 ms
style layout 116 ms
paint composite render 40 ms
script evaluation 16 ms
parse HTML 14 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 562 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.

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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 21, 2026, 9:38 AM UTC 99 2.13 s 0.012 0 ms 266.3 kB 3/3 ±1 2,418 23s

Embed this score

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

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://www.a11yproject.com/"></speedlify-score>