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 ·

zellwk.com

https://zellwk.com/

56 99 96 100 ✗CWV 9AXE

Data from Aug 21, 2026, 4:34 PM UTC — 2h old.

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

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.

Astro Built with Astro
Cloudflare Hosted by Cloudflare

Core Web Vitals field data, origin-level

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

LCP 2.91 s needs-improvement
INP — no data
CLS 0 good

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.12 s — — 5.12 s 5.12 s
CLS Cumulative Layout Shift 0.140 — — 0.140 0.140
TBT Total Blocking Time 399 ms — — 399 ms 399 ms
FCP First Contentful Paint 4.14 s — — 4.14 s 4.14 s
Speed Index 4.14 s — — 4.14 s 4.14 s
TTFB Time to First Byte 535 ms — — 535 ms 535 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 196 ms
time to first byte 156 ms

Field data Chrome UX Report, origin-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 2.91 s needs-improvement 69.1% good
CLS CWV 0 good 95.1% good
FCP 2.94 s needs-improvement 52.6% good
TTFB 1.60 s needs-improvement 43% good

Lab vs field

Lab LCP 5.12 s · field p75 2.91 s · real users are 0.57× 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.08 s — 0 3.08 s 1.65 s
2026-08-08 2.97 s — 0 2.97 s 1.60 s
2026-08-01 2.64 s — 0 2.69 s 1.55 s
2026-07-25 2.72 s — 0 2.69 s 1.40 s
2026-07-18 2.68 s — 0 2.65 s 1.37 s
2026-07-11 2.69 s — 0 2.61 s 1.37 s
2026-07-04 2.68 s — 0 2.56 s 1.30 s
2026-06-27 2.98 s — 0 2.88 s 1.42 s
2026-06-20 2.73 s 86 ms 0 2.68 s 1.33 s
2026-06-13 2.77 s — 0 2.77 s 1.36 s
2026-06-06 3.11 s — 0 3.12 s 1.43 s
2026-05-30 2.77 s — 0 2.79 s 1.43 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.12 MB — — 1.12 MB 1.12 MB
Requests 32 — — 32 32
Third-party Weight 728.5 kB — — 728.5 kB 728.5 kB
Third-party CPU 159 ms — — 159 ms 159 ms
Unused JS 267.0 kB — — 267.0 kB 267.0 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 612.1 kB · 16 req
font 369.4 kB · 4 req
image 58.5 kB · 3 req
document 31.7 kB · 1 req
stylesheet 26.3 kB · 3 req
other 21.5 kB · 5 req
third party 728.5 kB · 12 req

Third parties 5 entities

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

Adobe TypeKit 370.6 kB · 0 ms CPU
Facebook 173.8 kB · 84 ms CPU
Google Tag Manager 171.1 kB · 71 ms CPU
Cloudflare 11.5 kB · 3 ms CPU
iconify.design 1.5 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.42 s — — 1.42 s 1.42 s
Long Tasks 6 — — 6 6
DOM Elements 262 — — 262 262
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 9 — — 9 9
A11y Failures 1 — — 1 1
A11y Failing Nodes 8 — — 8 8

Main thread work

script evaluation 774 ms
other 289 ms
style layout 175 ms
script parse compile 108 ms
parse HTML 38 ms
paint composite render 23 ms
garbage collection 10 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 2 rules, 513 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 svg-img-alt — <svg> elements with an img or image role must have alternative text 8 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 26 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.

  • svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 8 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3 3 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 21, 2026, 4:34 PM UTC 56 5.12 s 0.140 399 ms 1.12 MB 3/3 ±30 2,474 32.8s

Embed this score

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