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 ·

huphtur.nl

https://huphtur.nl/

100 100 100 100 –CWV 1AXE

Data from Aug 20, 2026, 11:32 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 3.1.2 Built with Eleventy 3.1.2
Cloudflare Hosted by Cloudflare

Scores

100
Performance
no change
100
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.75 s — — 1.75 s 1.75 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.08 s — — 1.08 s 1.08 s
Speed Index 1.08 s — — 1.08 s 1.08 s
TTFB Time to First Byte 538 ms — — 538 ms 538 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.

time to first byte 136 ms
element render delay 99 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 362.9 kB — — 362.9 kB 362.9 kB
Requests 16 — — 16 16
Third-party Weight 205.4 kB — — 205.4 kB 205.4 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 211.1 kB · 9 req
other 138.1 kB · 1 req
document 6.0 kB · 1 req
stylesheet 4.0 kB · 2 req
script 3.6 kB · 2 req
third party 205.4 kB · 10 req

Third parties 2 entities

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

YouTube 202.4 kB · 0 ms CPU
JSDelivr CDN 2.9 kB · 2 ms CPU

Page health

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

Main thread work

other 178 ms
style layout 86 ms
paint composite render 26 ms
script evaluation 21 ms
parse HTML 11 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 393 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.

  • moderate region — All page content should be contained by landmarks 1 node

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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:32 PM UTC 100 1.75 s 0 0 ms 362.9 kB 3/3 ±5 2,299 24.6s

Embed this score

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