eleventy-solo-starter-njk.vercel.app
https://eleventy-solo-starter-njk.vercel.app/
Ranks Overall #173 Build Awesome Starters #22
Data from Sep 19, 2026, 3:26 AM UTC old, older than this category's 14 days freshness target Measured once a week · 14 runs since Aug 20, 2026
Elsewhere:
PageSpeed Insights ·
Calibre ·
Treo ·
CrUX Vis ·
Tame the Bots ·
Scoring Calculator ·
Wayback Machine
ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404)
Numbers below are from the last successful run, old.
Retries are backing off, so this site is being attempted less often than the rest.
Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).
Stack
Lighthouse Scores LAB Simulated
Metrics LAB
No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.
| Metric | Lab Simulated | ||
|---|---|---|---|
| Value | Change / range | Trend | |
| LCP CWV (estimate) Largest Contentful Paint | 799 ms good | ↓ -12 ms (-1.5%) 799 ms – 813 ms | |
| INP CWV Interaction to Next Paint — field only, no lab run can measure it | n/a | — | |
| CLS CWV (estimate) Cumulative Layout Shift | 0 good | → no change 0 – 0 | |
| TBT Total Blocking Time | 0 ms good | → no change 0 ms – 0 ms | |
| FCP First Contentful Paint | 799 ms good | ↓ -12 ms (-1.5%) 799 ms – 813 ms | |
| Speed Index | 799 ms good | ↓ -12 ms (-1.5%) 799 ms – 813 ms | |
| TTFB Time to First Byte | 630 ms good | ↓ -3 ms (-0.5%) 622 ms – 636 ms | |
LCP Subparts LAB Unthrottled
The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.
Page weight
| Metric | Value | Change / range | Trend |
|---|---|---|---|
| Page Weight | 13.1 kB | ↑ +12 B (+0.1%) 13.1 kB – 13.2 kB | |
| Requests | 3 | → no change 3 – 3 | |
| Third-party Weight | 0 B | → no change 0 B – 0 B | |
| Third-party CPU | 0 ms | → no change 0 ms – 0 ms | |
| Unused JS | 0 B | → no change 0 B – 0 B | |
| Unused CSS | 0 B | → no change 0 B – 0 B |
By resource type
| Type | Transfer | Share | Size | Requests |
|---|---|---|---|---|
| stylesheet | 49.4% | 6.5 kB | 1 | |
| other | 36.4% | 4.8 kB | 1 | |
| document | 14.1% | 1.9 kB | 1 | |
| Total | 13.1 kB | 3 |
Without JavaScript
The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.
0.8% of pixels differ — they are nearly identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.
Page health
| Metric | Value | Change / range | Trend |
|---|---|---|---|
| Main Thread Work | 95 ms | ↓ -14 ms (-12.7%) 92 ms – 117 ms | |
| Long Tasks | 0 | → no change 0 – 0 | |
| DOM Elements | 73 | → no change 73 – 73 | |
| Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) | 0 | → no change 0 – 0 | |
| A11y Failures | 0 | → no change 0 – 0 | |
| A11y Failing Nodes | 0 | → no change 0 – 0 |
Main thread work
| Task | Time | Share | Duration Simulated |
|---|---|---|---|
| other | 54% | 51 ms | |
| style layout | 29% | 28 ms | |
| script evaluation | 9% | 9 ms | |
| parse HTML | 5% | 4 ms | |
| paint composite render | 3% | 3 ms | |
| script parse compile | 0% | 0 ms | |
| Total | 95 ms |
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 156 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.
Hygiene
Measurement log
Every stored run for this URL, newest first.
| When | Scores | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took | Archive |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Oct 8, 2026, 2:34 AM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
11.7s | |||||||||
| Oct 6, 2026, 11:09 PM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.9s | |||||||||
| Oct 5, 2026, 6:17 PM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
17.1s | |||||||||
| Oct 1, 2026, 2:40 PM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.2s | |||||||||
| Sep 30, 2026, 4:04 PM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.4s | |||||||||
| Sep 30, 2026, 1:08 AM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.4s | |||||||||
| Sep 29, 2026, 5:58 PM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.2s | |||||||||
| Sep 29, 2026, 11:11 AM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.4s | |||||||||
| Sep 26, 2026, 9:12 AM UTC | ERRORED_DOCUMENT_REQUEST: Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 404) |
12.9s | |||||||||
| Sep 19, 2026, 3:26 AM UTC | 100 | 799 ms | 0 | 0 ms | 13.1 kB | 3/3 | ±0 | 2,943 +18% | 22.2s |
|
|
| Sep 12, 2026, 1:11 AM UTC | 100 | 811 ms | 0 | 0 ms | 13.1 kB | 3/3 | ±0 | 2,514 +1% | 22.2s |
|
|
| Sep 4, 2026, 11:53 PM UTC | 100 | 813 ms | 0 | 0 ms | 13.1 kB | 3/3 | ±0 | 2,809 +13% | 20.7s |
|
|
| Aug 28, 2026, 11:33 PM UTC | 100 | 799 ms | 0 | 0 ms | 13.2 kB | 3/3 | ±0 | 3,453 +39% | 19.4s |
|
|
| Aug 20, 2026, 9:32 PM UTC | 100 | 800 ms | 0 | 0 ms | 13.1 kB | 3/3 | ±0 | 2,333 -6% | 20.2s |
|
|
Embed this score
Use this web component to show eleventy-solo-starter-njk.vercel.app's scores on any website, updated whenever this instance re-measures. 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-solo-starter-njk.vercel.app/"></speedlify2-score>