speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

hans.gerwitz.com

https://hans.gerwitz.com/

100 94 100 92 –CWV 5AXE

Data from Aug 20, 2026, 11:36 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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.

Eleventy 4.0.0 Built with Eleventy 4.0.0
Self-hosted · nginx Hosted by Self-hosted

Scores

100
Performance
no change
94
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 895 ms — — 895 ms 895 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 895 ms — — 895 ms 895 ms
Speed Index 895 ms — — 895 ms 895 ms
TTFB Time to First Byte 719 ms — — 719 ms 719 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.

element render delay 151 ms
time to first byte 121 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 8.3 kB — — 8.3 kB 8.3 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

stylesheet 3.4 kB · 1 req
document 2.5 kB · 1 req
other 512 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 118 ms — — 118 ms 118 ms
Long Tasks 0 — — 0 0
DOM Elements 64 — — 64 64
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 5 — — 5 5
A11y Failures 2 — — 2 2
A11y Failing Nodes 2 — — 2 2

Main thread work

other 69 ms
style layout 31 ms
script evaluation 9 ms
parse HTML 5 ms
paint composite render 4 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 5 rules, 145 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 document-title — Documents must have <title> element to aid in navigation 1 node
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 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.

  • document-title — Document doesn't have a `<title>` element 1 node
  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 11:36 PM UTC 100 895 ms 0 0 ms 8.3 kB 3/3 ±0 2,330 22.7s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show hans.gerwitz.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://hans.gerwitz.com/"></speedlify-score>