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 ·

hno-marienplatz.de

https://www.hno-marienplatz.de/

98 96 96 100 ✓CWV 9AXE

Data from Aug 21, 2026, 12:50 PM UTC — 6h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 6h

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 Built with Eleventy
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 954 ms good
INP — no data
CLS 0 good

Scores

98
Performance
no change
96
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.95 s — — 1.95 s 1.95 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 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 629 ms — — 629 ms 629 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 144 ms
time to first byte 30 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 954 ms good 99.1% good
CLS CWV 0 good 99.1% good
FCP 877 ms good 98.3% good

Lab vs field

Lab LCP 1.95 s · field p75 954 ms · real users are 0.49× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.04 s — 0 972 ms —
2026-08-08 1.04 s — 0 999 ms —
2026-08-01 1.26 s — 0 1.10 s —
2026-07-25 1.33 s — 0 1.18 s —
2026-07-18 1.19 s — 0 1.10 s —
2026-07-11 1.26 s — 0 1.16 s —
2026-07-04 1.23 s — 0 1.16 s 693 ms
2026-06-27 1.13 s — 0 1.06 s —
2026-06-20 1.27 s 79 ms 0 1.07 s 820 ms
2026-06-13 1.16 s 83 ms 0 1.04 s 764 ms
2026-06-06 1.20 s 83 ms 0 1.08 s 715 ms
2026-05-30 1.20 s 86 ms 0 1.08 s 683 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 161.8 kB — — 161.8 kB 161.8 kB
Requests 14 — — 14 14
Third-party Weight 2.4 kB — — 2.4 kB 2.4 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 12.6 kB — — 12.6 kB 12.6 kB

By resource type

document 61.2 kB · 1 req
image 38.3 kB · 3 req
script 24.8 kB · 2 req
font 23.9 kB · 2 req
other 10.0 kB · 4 req
stylesheet 687 B · 1 req
third party 2.4 kB · 2 req

Third parties 1 entities

2.4 kB transferred, 3 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Plausible 2.4 kB · 3 ms CPU

Page health

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

Main thread work

other 152 ms
script evaluation 54 ms
style layout 46 ms
parse HTML 26 ms
paint composite render 10 ms
script parse compile 8 ms
garbage collection 3 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 3 rules, 407 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 6 nodes
  • moderate region — All page content should be contained by landmarks 2 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 21 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 6 nodes

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 21, 2026, 12:50 PM UTC 98 1.95 s 0 0 ms 161.8 kB 3/3 ±2 2,384 24.1s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show hno-marienplatz.de'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.hno-marienplatz.de/"></speedlify-score>