zachleat.com
Data from Aug 21, 2026, 2:42 PM UTC — 2h old.
zachleat.com, Built Awesome · 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.
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 1.96 s | — | — | 1.96 s | 1.96 s | |
| CLS Cumulative Layout Shift | 0.001 | — | — | 0.001 | 0.001 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.08 s | — | — | 1.08 s | 1.08 s | |
| Speed Index | 1.08 s | — | — | 1.08 s | 1.08 s | |
| TTFB Time to First Byte | 607 ms | — | — | 607 ms | 607 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.
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 1.96 s · field p75 1.08 s · real users are 0.55× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 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 | 134.6 kB | — | — | 134.6 kB | 134.6 kB | |
| Requests | 24 | — | — | 24 | 24 | |
| Third-party Weight | 28.1 kB | — | — | 28.1 kB | 28.1 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
Third parties 3 entities
28.1 kB transferred, 2 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 326 ms | — | — | 326 ms | 326 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 473 | — | — | 473 | 473 | |
| 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
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 695 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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 21, 2026, 2:42 PM UTC | 99 | 1.96 s | 0.001 | 0 ms | 134.6 kB | 3/3 | ±1 | 2,493 | 26.1s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
zachleat.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://www.zachleat.com/"></speedlify-score>