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 ·

maximilianberndt.com

https://maximilianberndt.com/

98 95 100 100 CWV 0AXE

Data from Aug 21, 2026, 3:13 AM UTC — 15h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 15h

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.

SvelteKit Built with SvelteKit
Netlify Hosted by Netlify

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.89 s 1.89 s 1.89 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.18 s 1.18 s 1.18 s
Speed Index 3.67 s 3.67 s 3.67 s
TTFB Time to First Byte 1.87 s 1.87 s 1.87 s

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.

time to first byte 1.87 s
element render delay 450 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 88.4 kB 88.4 kB 88.4 kB
Requests 25 25 25
Third-party Weight 647 B 647 B 647 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

script 49.7 kB · 20 req
font 26.2 kB · 1 req
document 6.5 kB · 1 req
stylesheet 5.3 kB · 1 req
other 647 B · 2 req
third party 647 B · 2 req

Third parties 1 entities

647 B transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

prismic.io 647 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 470 ms 470 ms 470 ms
Long Tasks 1 1 1
DOM Elements 125 125 125
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 13 13 13

Main thread work

other 237 ms
script evaluation 157 ms
style layout 44 ms
paint composite render 17 ms
parse HTML 10 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 252 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 18 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. 13 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, 3:13 AM UTC 98 1.89 s 0 0 ms 88.4 kB 2/3 ±2 2,364 49.9s

Embed this score

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