hendricks.rocks
Data from Aug 21, 2026, 6:40 PM UTC — 33m old.
11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 33m
https://www.d-hendricks.com/.
Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.
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 | 3.26 s | — | — | 3.26 s | 3.26 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 46 ms | — | — | 46 ms | 46 ms | |
| FCP First Contentful Paint | 1.95 s | — | — | 1.95 s | 1.95 s | |
| Speed Index | 1.95 s | — | — | 1.95 s | 1.95 s | |
| TTFB Time to First Byte | 527 ms | — | — | 527 ms | 527 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 | 376.2 kB | — | — | 376.2 kB | 376.2 kB | |
| Requests | 18 | — | — | 18 | 18 | |
| Third-party Weight | 375.5 kB | — | — | 375.5 kB | 375.5 kB | |
| Third-party CPU | 80 ms | — | — | 80 ms | 80 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
375.5 kB transferred, 80 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 | 569 ms | — | — | 569 ms | 569 ms | |
| Long Tasks | 1 | — | — | 1 | 1 | |
| DOM Elements | 94 | — | — | 94 | 94 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 4 | — | — | 4 | 4 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 3 | — | — | 3 | 3 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
4 violating nodes across 2 rules, 200 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
link-name— Links must have discernible text 3 nodes -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
Accessibility failures 1 of 20 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.
-
link-name— Links do not have a discernible name 3 nodes
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, 6:40 PM UTC | 91 | 3.26 s | 0 | 46 ms | 376.2 kB | 3/3 | ±3 | 2,265 | 21.2s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
hendricks.rocks'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.hendricks.rocks/"></speedlify-score>