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 ·

wolstenhol.me

https://wolstenhol.me/

100 93 96 100 –CWV 6AXE

Data from Aug 21, 2026, 10:35 AM UTC — 8h old.

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

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.

Netlify Hosted by Netlify

Scores

100
Performance
no change
93
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.38 s — — 1.38 s 1.38 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 34 ms — — 34 ms 34 ms
FCP First Contentful Paint 1.09 s — — 1.09 s 1.09 s
Speed Index 1.09 s — — 1.09 s 1.09 s
TTFB Time to First Byte 632 ms — — 632 ms 632 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 95 ms
time to first byte 85 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 309.6 kB — — 309.6 kB 309.6 kB
Requests 50 — — 50 50
Third-party Weight 11.5 kB — — 11.5 kB 11.5 kB
Third-party CPU 7 ms — — 7 ms 7 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 87.1 kB · 11 req
other 79.2 kB · 9 req
document 51.1 kB · 1 req
script 45.8 kB · 14 req
font 37.7 kB · 2 req
stylesheet 8.8 kB · 1 req
third party 11.5 kB · 3 req

Third parties 2 entities

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

Cloudflare 11.5 kB · 7 ms CPU
cloudflareinsights.com 36 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.36 s — — 1.36 s 1.36 s
Long Tasks 3 — — 3 3
DOM Elements 1,905 — — 1,905 1,905
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 — — 6 6
A11y Failures 2 — — 2 2
A11y Failing Nodes 3 — — 3 3

Main thread work

other 501 ms
style layout 369 ms
script evaluation 337 ms
parse HTML 106 ms
paint composite render 39 ms
script parse compile 8 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 1579 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 5 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node

Accessibility failures 2 of 28 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 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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 1 console error

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, 10:35 AM UTC 100 1.38 s 0.003 34 ms 309.6 kB 3/3 ±4 2,488 50.3s

Embed this score

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