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 ·

web.dev

https://web.dev/

50 90 100 92 ✗CWV 19AXE

Data from Aug 21, 2026, 10:32 AM UTC — 8h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 8h

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.

Go Hosted by Google Frontend

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 3.03 s needs-improvement
INP 208 ms needs-improvement
CLS 0.010 good

Scores

50
Performance
no change
90
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.28 s — — 4.28 s 4.28 s
CLS Cumulative Layout Shift 0.090 — — 0.090 0.090
TBT Total Blocking Time 1.10 s — — 1.10 s 1.10 s
FCP First Contentful Paint 4.21 s — — 4.21 s 4.21 s
Speed Index 4.21 s — — 4.21 s 4.21 s
TTFB Time to First Byte 721 ms — — 721 ms 721 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.

time to first byte 478 ms
element render delay 164 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 3.03 s needs-improvement 65.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 208 ms needs-improvement 73.3% good
CLS CWV 0.010 good 87.4% good
FCP 3.06 s poor 45.2% good
TTFB 1.82 s poor 21% good

Lab vs field

Lab LCP 4.28 s · field p75 3.03 s · real users are 0.71× 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 3.00 s 210 ms 0.010 3.01 s 1.79 s
2026-08-08 3.08 s 208 ms 0.010 3.10 s 1.80 s
2026-08-01 3.07 s 207 ms 0.010 3.08 s 1.79 s
2026-07-25 3.08 s 205 ms 0.010 3.08 s 1.79 s
2026-07-18 3.04 s 202 ms 0 3.03 s 1.76 s
2026-07-11 3.02 s 208 ms 0 3.02 s 1.75 s
2026-07-04 2.98 s 211 ms 0 3.00 s 1.70 s
2026-06-27 2.97 s 216 ms 0 2.98 s 1.69 s
2026-06-20 2.90 s 217 ms 0 2.93 s 1.67 s
2026-06-13 2.81 s 215 ms 0 2.81 s 1.63 s
2026-06-06 2.77 s 219 ms 0.010 2.77 s 1.62 s
2026-05-30 2.64 s 214 ms 0 2.65 s 1.61 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.44 MB — — 2.44 MB 2.44 MB
Requests 95 — — 95 95
Third-party Weight 1.62 MB — — 1.62 MB 1.62 MB
Third-party CPU 495 ms — — 495 ms 495 ms
Unused JS 459.5 kB — — 459.5 kB 459.5 kB
Unused CSS 133.2 kB — — 133.2 kB 133.2 kB

By resource type

script 1.37 MB · 48 req
font 541.1 kB · 12 req
stylesheet 374.5 kB · 10 req
image 85.7 kB · 7 req
document 64.7 kB · 4 req
other 2.5 kB · 10 req
third party 2.33 MB · 81 req

Third parties 5 entities

1.62 MB transferred, 495 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google CDN 806.2 kB · 117 ms CPU
Google Tag Manager 592.3 kB · 374 ms CPU
Google Fonts 207.2 kB · 0 ms CPU
Unpkg 15.7 kB · 4 ms CPU
Google Analytics 591 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 4.14 s — — 4.14 s 4.14 s
Long Tasks 14 — — 14 14
DOM Elements 842 — — 842 842
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 19 — — 19 19
A11y Failures 3 — — 3 3
A11y Failing Nodes 14 — — 14 14

Main thread work

script evaluation 2.10 s
other 836 ms
style layout 614 ms
script parse compile 384 ms
paint composite render 116 ms
parse HTML 70 ms
garbage collection 20 ms

Axe violations axe-core 4.13.0, full rule set

19 violating nodes across 4 rules, 1783 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 link-name — Links must have discernible text 9 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 6 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 3 nodes
  • serious frame-title — Frames must have an accessible name 1 node

Accessibility failures 3 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.

  • link-name — Links do not have a discernible name 9 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 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

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, 10:32 AM UTC 50 4.28 s 0.090 1.10 s 2.44 MB 3/3 ±10 2,475 47.3s

Embed this score

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