eleventy-explorer.netlify.app
https://eleventy-explorer.netlify.app/
Data from Aug 20, 2026, 8:35 PM UTC — 22h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 22h
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 1.01 s | — | — | 1.01 s | 1.01 s | |
| CLS Cumulative Layout Shift | 0.163 | — | — | 0.163 | 0.163 | |
| TBT Total Blocking Time | 16 ms | — | — | 16 ms | 16 ms | |
| FCP First Contentful Paint | 1.01 s | — | — | 1.01 s | 1.01 s | |
| Speed Index | 1.01 s | — | — | 1.01 s | 1.01 s | |
| TTFB Time to First Byte | 625 ms | — | — | 625 ms | 625 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 109.0 kB | — | — | 109.0 kB | 109.0 kB | |
| Requests | 19 | — | — | 19 | 19 | |
| Third-party Weight | 24.1 kB | — | — | 24.1 kB | 24.1 kB | |
| 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
Third parties 1 entities
24.1 kB transferred, 0 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 | 469 ms | — | — | 469 ms | 469 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 1,293 | — | — | 1,293 | 1,293 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 7 | — | — | 7 | 7 | |
| A11y Failures | 4 | — | — | 4 | 4 | |
| A11y Failing Nodes | 39 | — | — | 39 | 39 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
7 violating nodes across 4 rules, 2586 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.
-
moderate
region— All page content should be contained by landmarks 4 nodes -
moderate
heading-order— Heading levels should only increase by one 1 node -
moderate
landmark-one-main— Document should have one main landmark 1 node -
serious
link-name— Links must have discernible text 1 node
Accessibility failures 4 of 16 audits
Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.
-
target-size— Touch targets do not have sufficient size or spacing. 36 nodes -
heading-order— Heading elements are not in a sequentially-descending order 1 node -
link-name— Links do not have a discernible name 1 node -
landmark-one-main— Document does not have a main landmark. 1 node
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 20, 2026, 8:35 PM UTC | 93 | 1.01 s | 0.163 | 16 ms | 109.0 kB | 3/3 | ±0 | 2,483 | 28.3s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
eleventy-explorer.netlify.app'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://eleventy-explorer.netlify.app/"></speedlify-score>