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/web/google-fonts-display

https://www.zachleat.com/web/google-fonts-display

90 100 100 100 0AXE ✓CWV

Data from Aug 23, 2026, 6:29 PM UTC 3h old

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

90
Performance
↓ -1 (-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.75 s ↑ +153 ms (+8.7%) significant 1.75 s 1.90 s
CLS Cumulative Layout Shift 0.192 0.192 → no change 0.192 0.192
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 1.70 s 1.07 s ↑ +623 ms (+58.1%) significant 1.07 s 1.70 s
Speed Index 1.70 s 1.07 s ↑ +623 ms (+58.1%) significant 1.07 s 1.70 s
TTFB Time to First Byte 627 ms 623 ms ↑ +4 ms (+0.6%) 623 ms 627 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 102 ms
time to first byte 29 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 148 kB 141 kB ↑ +6.9 kB (+5%) significant 140 kB 148 kB
Requests 19 19 → no change 19 19
Third-party Weight 14.9 kB 5.7 kB ↑ +9.0 kB (+161.6%) significant 5.6 kB 14.9 kB
Third-party CPU 3 ms 2 ms ↑ +0 ms (+19%) significant 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

font 70.8 kB · 5 req
document 35.6 kB · 1 req
script 28.1 kB · 7 req
other 4.7 kB · 3 req
image 4.5 kB · 2 req
stylesheet 4.1 kB · 1 req
third party 14.9 kB · 5 req

Third parties 4 entities

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

speedlify.dev 9.4 kB · 0 ms CPU
zgo.at 4.4 kB · 3 ms CPU
11ty.dev 720 B · 0 ms CPU
goatcounter.com 380 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 563 ms 442 ms ↑ +120 ms (+27.2%) 442 ms 563 ms
Long Tasks 1 1 → no change 1 1
DOM Elements 837 788 ↑ +49 (+6.2%) significant 788 837
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

style layout 217 ms
other 161 ms
script evaluation 79 ms
paint composite render 61 ms
parse HTML 41 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 1544 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, 6:29 PM UTC 90 1.90 s 0.192 0 ms 148 kB 3/3 ±2 2,501 39.7s
Aug 22, 2026, 5:21 PM UTC 91 1.75 s 0.192 0 ms 141 kB 3/3 ±3 3,399 37.1s
Aug 21, 2026, 4:35 PM UTC 91 1.76 s 0.192 0 ms 140 kB 3/3 ±4 2,704 38.9s

Embed this score

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