markus-haack.com
Data from Aug 21, 2026, 3:12 AM UTC — 16h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 16h
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.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 1.66 s | — | — | 1.66 s | 1.66 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.66 s | — | — | 1.66 s | 1.66 s | |
| Speed Index | 1.66 s | — | — | 1.66 s | 1.66 s | |
| TTFB Time to First Byte | 623 ms | — | — | 623 ms | 623 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.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.18 s | good | 99% good |
| CLS CWV | 0 | good | 97.6% good |
| FCP | 961 ms | good | 97% good |
| TTFB | 627 ms | good | 90.3% good |
Lab vs field
Lab LCP 1.66 s · field p75 1.18 s · real users are 0.71× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-15 | 1.23 s | — | 0 | 977 ms | 644 ms |
| 2026-08-08 | 1.21 s | — | 0 | 958 ms | 629 ms |
| 2026-08-01 | 1.23 s | — | 0 | 952 ms | 598 ms |
| 2026-07-25 | 1.19 s | — | 0 | 961 ms | 567 ms |
| 2026-07-18 | 1.18 s | — | 0 | 942 ms | 552 ms |
| 2026-07-11 | 1.18 s | — | 0 | 974 ms | 569 ms |
| 2026-07-04 | 1.18 s | — | 0 | 1.01 s | 552 ms |
| 2026-06-27 | 1.18 s | — | 0 | 1.04 s | 614 ms |
| 2026-06-20 | 1.17 s | — | 0 | 1.01 s | 614 ms |
| 2026-06-13 | 1.13 s | — | 0 | 996 ms | 616 ms |
| 2026-06-06 | 1.12 s | — | 0 | 976 ms | 601 ms |
| 2026-05-30 | 1.15 s | — | 0 | 925 ms | 595 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 225.3 kB | — | — | 225.3 kB | 225.3 kB | |
| Requests | 15 | — | — | 15 | 15 | |
| Third-party Weight | 4.5 kB | — | — | 4.5 kB | 4.5 kB | |
| Third-party CPU | 3 ms | — | — | 3 ms | 3 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
4.5 kB transferred, 3 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 | 265 ms | — | — | 265 ms | 265 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 217 | — | — | 217 | 217 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 474 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.
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, 3:12 AM UTC | 99 | 1.66 s | 0 | 0 ms | 225.3 kB | 3/3 | ±4 | 2,325 | 25.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
markus-haack.com'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://markus-haack.com/"></speedlify-score>