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 ·

zachleat.com/about

https://www.zachleat.com/about

99 100 100 100 0AXE ✓CWV

Data from Aug 23, 2026, 1:31 PM UTC 9h old

zachleat.com #1 · 3 measurements · since Aug 21, 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.

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-25 → 2026-08-21). This is what Google measures you on.

LCP 1.08 s good
INP — no data
CLS 0 good

Scores

99
Performance
↓ -1 (-1%)
100
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 1.90 s 1.66 s ↑ +242 ms (+14.6%) 1.66 s 1.90 s
CLS Cumulative Layout Shift 0.001 0.001 → no change 0.001 0.002
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 1.68 s 962 ms ↑ +713 ms (+74.1%) significant 962 ms 1.68 s
Speed Index 1.68 s 962 ms ↑ +713 ms (+74.1%) significant 962 ms 1.68 s
TTFB Time to First Byte 620 ms 605 ms ↑ +15 ms (+2.5%) 605 ms 630 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 1.90 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 38 ms
resource load delay 26 ms
resource load duration 25 ms
time to first byte 22 ms

Field data Chrome UX Report, origin-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.08 s good 93.1% good
CLS CWV 0 good 98.5% good
FCP 1.01 s good 93.7% good
TTFB 693 ms good 81.8% good

Lab vs field

Lab LCP 1.90 s · field p75 1.08 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 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 251 kB 245 kB ↑ +6.4 kB (+2.7%) 242 kB 251 kB
Requests 25 25 → no change 23 25
Third-party Weight 29.0 kB 20.1 kB ↑ +8.7 kB (+44.4%) significant 19.9 kB 29.0 kB
Third-party CPU 2 ms 3 ms ↓ -1 ms (-32.1%) 2 ms 3 ms
Unused JS 0 B 0 B → no change 0 B 0 B
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

image 122 kB · 9 req
font 70.8 kB · 5 req
document 25.7 kB · 1 req
script 23.7 kB · 5 req
other 4.6 kB · 4 req
stylesheet 4.0 kB · 1 req
third party 29.1 kB · 10 req

Third parties 4 entities

29.0 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 15.1 kB · 0 ms CPU
speedlify.dev 9.2 kB · 0 ms CPU
zgo.at 4.3 kB · 2 ms CPU
goatcounter.com 380 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 470 ms 348 ms ↑ +122 ms (+34.9%) 348 ms 470 ms
Long Tasks 0 0 → no change 0 0
DOM Elements 641 592 ↑ +49 (+8.3%) significant 589 641
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 → no change 0 0
A11y Failures 0 1 ↓ -1 (-100%) 0 1
A11y Failing Nodes 0 1 ↓ -1 (-100%) 0 1

Main thread work

other 168 ms
style layout 158 ms
script evaluation 72 ms
paint composite render 37 ms
parse HTML 33 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 1023 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 23, 2026, 1:31 PM UTC 99 1.90 s 0.001 0 ms 251 kB 3/3 ±12 2,476 27.4s
Aug 22, 2026, 1:30 PM UTC 100 1.66 s 0.001 0 ms 245 kB 3/3 ±8 2,929 25.9s
Aug 21, 2026, 12:55 PM UTC 100 1.79 s 0.002 0 ms 242 kB 3/3 ±9 2,301 26.9s

Embed this score

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