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 ·

justin.poehnelt.com

https://justin.poehnelt.com/

66 95 100 100 –CWV 12AXE

Data from Aug 21, 2026, 3:03 AM UTC — 16h old.

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

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
Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

66
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 3.30 s — — 3.30 s 3.30 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1.31 s — — 1.31 s 1.31 s
FCP First Contentful Paint 1.93 s — — 1.93 s 1.93 s
Speed Index 2.03 s — — 2.03 s 2.03 s
TTFB Time to First Byte 650 ms — — 650 ms 650 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 110 ms
time to first byte 72 ms
resource load delay 50 ms
resource load duration 17 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 1.52 s 173 ms 0 986 ms 505 ms
2026-07-11 1.52 s 173 ms 0 986 ms 505 ms
2026-07-04 1.35 s 162 ms 0 957 ms 491 ms
2026-06-27 1.52 s 162 ms 0 971 ms 499 ms
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 548.0 kB — — 548.0 kB 548.0 kB
Requests 38 — — 38 38
Third-party Weight 175.0 kB — — 175.0 kB 175.0 kB
Third-party CPU 54 ms — — 54 ms 54 ms
Unused JS 173.4 kB — — 173.4 kB 173.4 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 405.2 kB · 32 req
document 63.2 kB · 1 req
image 53.3 kB · 1 req
stylesheet 22.0 kB · 1 req
other 4.3 kB · 3 req
third party 175.0 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 175.0 kB · 54 ms CPU

Page health

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

Main thread work

script evaluation 2.51 s
other 397 ms
style layout 339 ms
garbage collection 151 ms
script parse compile 78 ms
parse HTML 77 ms
paint composite render 54 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 2 rules, 3450 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 10 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes

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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 10 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 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:03 AM UTC 66 3.30 s 0 1.31 s 548.0 kB 3/3 ±24 2,337 35.3s

Embed this score

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