aloxe.github.io/huwindty
https://aloxe.github.io/huwindty
Data from Aug 20, 2026, 7:04 PM UTC 3d old
Build Awesome Starters #85 · 1 measurement · since Aug 20, 2026
https://aloxe.github.io/huwindty/.
A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.
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.20 s | — | — | 1.20 s | 1.20 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 771 ms | — | — | 771 ms | 771 ms | |
| Speed Index | 771 ms | — | — | 771 ms | 771 ms | |
| TTFB Time to First Byte | 601 ms | — | — | 601 ms | 601 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 1.20 s 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 | 84.1 kB | — | — | 84.1 kB | 84.1 kB | |
| Requests | 8 | — | — | 8 | 8 | |
| 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 | 186 ms | — | — | 186 ms | 186 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 132 | — | — | 132 | 132 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 162 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 1 node
Accessibility failures 1 of 24 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 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, 7:04 PM UTC | 100 | 1.20 s | 0 | 0 ms | 84.1 kB | 3/3 | ±2 | 2,447 | 23s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
aloxe.github.io/huwindty'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://aloxe.github.io/huwindty"></speedlify2-score>