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 ·

galajurk.nl

https://www.galajurk.nl/

94 91 100 100 ✓CWV 24AXE

Data from Aug 21, 2026, 11:44 AM UTC — 7h old.

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

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.

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
Li Hosted by Self-hosted

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 522 ms good
INP 48 ms good
CLS 0 good

Scores

94
Performance
no change
91
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 2.86 s — — 2.86 s 2.86 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.09 s — — 1.09 s 1.09 s
Speed Index 3.71 s — — 3.71 s 3.71 s
TTFB Time to First Byte 759 ms — — 759 ms 759 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 1.99 s
resource load duration 179 ms
time to first byte 156 ms
resource load delay 10 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 522 ms good 99.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 48 ms good 100% good
CLS CWV 0 good 99.7% good
FCP 485 ms good 97.6% good
TTFB 247 ms good 94.9% good

Lab vs field

Lab LCP 2.86 s · field p75 522 ms · real users are 0.18× 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 526 ms 47 ms 0 495 ms 251 ms
2026-08-08 505 ms 53 ms 0 464 ms 269 ms
2026-08-01 501 ms 46 ms 0 459 ms 246 ms
2026-07-25 550 ms 53 ms 0 501 ms 251 ms
2026-07-18 554 ms — 0 506 ms 250 ms
2026-07-11 602 ms — 0 559 ms 290 ms
2026-07-04 620 ms — 0 561 ms 302 ms
2026-06-27 593 ms — 0 550 ms 292 ms
2026-06-20 559 ms 55 ms 0 533 ms 286 ms
2026-06-13 540 ms 55 ms 0 498 ms 265 ms
2026-06-06 548 ms 54 ms 0 506 ms 259 ms
2026-05-30 523 ms 54 ms 0 485 ms 263 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 846.1 kB — — 846.1 kB 846.1 kB
Requests 25 — — 25 25
Third-party Weight 3.8 kB — — 3.8 kB 3.8 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 777.0 kB · 16 req
script 26.3 kB · 2 req
document 14.8 kB · 1 req
font 12.4 kB · 1 req
stylesheet 10.6 kB · 1 req
other 2.5 kB · 3 req
third party 3.8 kB · 2 req

Third parties 1 entities

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

Plausible 3.8 kB · 2 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 641 — — 641 641
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 24 — — 24 24
A11y Failures 3 — — 3 3
A11y Failing Nodes 31 — — 31 31

Main thread work

other 168 ms
style layout 54 ms
script evaluation 31 ms
parse HTML 20 ms
paint composite render 17 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 2 rules, 856 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 23 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 3 of 26 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 25 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 5 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 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 21, 2026, 11:44 AM UTC 94 2.86 s 0 0 ms 846.1 kB 3/3 ±4 2,474 32.1s

Embed this score

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