eleventy-notist-example.netlify.app
https://eleventy-notist-example.netlify.app/
Data from Aug 20, 2026, 9:35 PM UTC 3d old
Built Awesome #907 · 1 measurement · since Aug 20, 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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 779 ms | — | — | 779 ms | 779 ms | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 779 ms | — | — | 779 ms | 779 ms | |
| Speed Index | 779 ms | — | — | 779 ms | 779 ms | |
| TTFB Time to First Byte | 609 ms | — | — | 609 ms | 609 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 779 ms above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 1.9 kB | — | — | 1.9 kB | 1.9 kB | |
| Requests | 1 | — | — | 1 | 1 | |
| 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 | 83 ms | — | — | 83 ms | 83 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 97 | — | — | 97 | 97 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 6 | — | — | 6 | 6 | |
| A11y Failures | 2 | — | — | 2 | 2 | |
| A11y Failing Nodes | 5 | — | — | 5 | 5 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
6 violating nodes across 3 rules, 252 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.
-
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 4 nodes -
moderate
landmark-one-main— Document should have one main landmark 1 node -
moderate
region— All page content should be contained by landmarks 1 node
Accessibility failures 2 of 13 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.
-
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 4 nodes -
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, 9:35 PM UTC | 100 | 779 ms | 0 | 0 ms | 1.9 kB | 3/3 | ±0 | 2,323 | 20.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
eleventy-notist-example.netlify.app'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://eleventy-notist-example.netlify.app/"></speedlify2-score>