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 ·

zachleat.com/web/speedlify

https://www.zachleat.com/web/speedlify

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

zachleat.com · 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.

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
Netlify Hosted by Netlify

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 1.08 s good
INP no data
CLS 0 good

Scores

97
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.06 s 2.06 s 2.06 s
CLS Cumulative Layout Shift 0.092 0.092 0.092
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.23 s 1.23 s 1.23 s
Speed Index 1.23 s 1.23 s 1.23 s
TTFB Time to First Byte 606 ms 606 ms 606 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 87 ms
time to first byte 7 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 1.08 s good 92.5% good
CLS CWV 0 good 98.5% good
FCP 1.02 s good 92.7% good
TTFB 693 ms good 81.3% good

Lab vs field

Lab LCP 2.06 s · field p75 1.08 s · real users are 0.53× 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.08 s 0 1.01 s 693 ms
2026-08-08 1.15 s 0 1.08 s 703 ms
2026-08-01 1.09 s 0 1.04 s 693 ms
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 207.2 kB 207.2 kB 207.2 kB
Requests 23 23 23
Third-party Weight 11.7 kB 11.7 kB 11.7 kB
Third-party CPU 2 ms 2 ms 2 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 66.7 kB · 9 req
document 58.8 kB · 1 req
font 55.9 kB · 4 req
script 17.4 kB · 5 req
other 4.2 kB · 3 req
stylesheet 4.1 kB · 1 req
third party 11.8 kB · 6 req

Third parties 3 entities

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

11ty.dev 7.0 kB · 0 ms CPU
zgo.at 4.4 kB · 2 ms CPU
goatcounter.com 379 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 538 ms 538 ms 538 ms
Long Tasks 2 2 2
DOM Elements 1,540 1,540 1,540
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

style layout 180 ms
other 176 ms
script evaluation 83 ms
parse HTML 53 ms
paint composite render 44 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 3414 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, 2:44 PM UTC 97 2.06 s 0.092 0 ms 207.2 kB 3/3 ±2 2,457 50.1s

Embed this score

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