11ty.dev
Data from Aug 21, 2026, 5:28 PM UTC — 1h old.
Site Generators, Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 1h
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, url-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.21 s | — | — | 1.21 s | 1.21 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 9 ms | — | — | 9 ms | 9 ms | |
| FCP First Contentful Paint | 1.06 s | — | — | 1.06 s | 1.06 s | |
| Speed Index | 1.06 s | — | — | 1.06 s | 1.06 s | |
| TTFB Time to First Byte | 610 ms | — | — | 610 ms | 610 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, url-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.05 s | good | 93.5% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 89 ms | good | 94.7% good |
| CLS CWV | 0 | good | 93.4% good |
| FCP | 1.07 s | good | 88.9% good |
| TTFB | 528 ms | good | 85% good |
Lab vs field
Lab LCP 1.21 s · field p75 1.05 s · real users are 0.87× 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.07 s | 88 ms | 0 | 1.07 s | 560 ms |
| 2026-08-08 | 1.10 s | 88 ms | 0 | 1.10 s | 527 ms |
| 2026-08-01 | 1.18 s | 89 ms | 0 | 1.16 s | 593 ms |
| 2026-07-25 | 1.21 s | 93 ms | 0 | 1.19 s | 607 ms |
| 2026-07-18 | 1.19 s | 96 ms | 0 | 1.19 s | 607 ms |
| 2026-07-11 | 1.18 s | 97 ms | 0 | 1.17 s | 604 ms |
| 2026-07-04 | 1.13 s | 95 ms | 0 | 1.14 s | 573 ms |
| 2026-06-27 | 1.10 s | 89 ms | 0 | 1.06 s | 558 ms |
| 2026-06-20 | 1.06 s | 87 ms | 0 | 994 ms | 506 ms |
| 2026-06-13 | 1.13 s | 91 ms | 0 | 953 ms | 532 ms |
| 2026-06-06 | 1.14 s | 91 ms | 0 | 942 ms | 544 ms |
| 2026-05-30 | 1.15 s | 94 ms | 0 | 938 ms | 544 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 92.2 kB | — | — | 92.2 kB | 92.2 kB | |
| Requests | 11 | — | — | 11 | 11 | |
| Third-party Weight | 0 B | — | — | 0 B | 0 B | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 598 ms | — | — | 598 ms | 598 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 1,489 | — | — | 1,489 | 1,489 | |
| 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, 2464 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, 5:28 PM UTC | 100 | 1.21 s | 0 | 9 ms | 92.2 kB | 3/3 | ±1 | 2,471 | 35.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
11ty.dev'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.11ty.dev/"></speedlify-score>