festive-haibt-b7ead0.netlify.app
https://festive-haibt-b7ead0.netlify.app/
Data from Aug 20, 2026, 9:33 PM UTC — 21h old.
Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 21h
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 | 799 ms | — | — | 799 ms | 799 ms | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 799 ms | — | — | 799 ms | 799 ms | |
| Speed Index | 799 ms | — | — | 799 ms | 799 ms | |
| TTFB Time to First Byte | 628 ms | — | — | 628 ms | 628 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 | 3.2 kB | — | — | 3.2 kB | 3.2 kB | |
| Requests | 3 | — | — | 3 | 3 | |
| 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 | 89 ms | — | — | 89 ms | 89 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 52 | — | — | 52 | 52 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 6 | — | — | 6 | 6 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 140 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.
Accessibility failures 1 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.
-
target-size— Touch targets do not have sufficient size or spacing. 6 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 20, 2026, 9:33 PM UTC | 100 | 799 ms | 0 | 0 ms | 3.2 kB | 3/3 | ±0 | 3,272 | 21.7s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
festive-haibt-b7ead0.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://festive-haibt-b7ead0.netlify.app/"></speedlify-score>