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 ·

matuzo.at

https://www.matuzo.at/

83 100 100 100 CWV 0AXE

Data from Aug 21, 2026, 6:47 PM UTC — 25m old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 25m

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.

Self-hosted · nginx Hosted by Self-hosted

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

83
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 3.68 s 3.68 s 3.68 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.59 s 2.59 s 2.59 s
Speed Index 4.56 s 4.56 s 4.56 s
TTFB Time to First Byte 713 ms 713 ms 713 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 2.03 s
time to first byte 236 ms
resource load duration 123 ms
resource load delay 10 ms

Field data Chrome UX Report, origin-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)
FCP 2.33 s needs-improvement 68.2% good

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 1.89 s 0 1.82 s 885 ms
2026-07-25 1.96 s 0 1.86 s 885 ms
2026-07-18 2.00 s 0 1.88 s 854 ms
2026-07-11 2.10 s 0 1.98 s 831 ms
2026-07-04 2.09 s 0 1.83 s 753 ms
2026-06-27 2.00 s 0 1.76 s 737 ms
2026-06-20 1.45 s 0 1.43 s 776 ms
2026-06-13 1.37 s 0 1.34 s 776 ms
2026-06-06 1.32 s 0 1.32 s 805 ms
2026-05-30 1.32 s 0 1.32 s 816 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 356.1 kB 356.1 kB 356.1 kB
Requests 54 54 54
Third-party Weight 13.8 kB 13.8 kB 13.8 kB
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

image 215.2 kB · 31 req
font 83.2 kB · 3 req
stylesheet 16.3 kB · 13 req
script 14.8 kB · 3 req
document 6.5 kB · 1 req
other 4.8 kB · 2 req
third party 13.8 kB · 2 req

Third parties 2 entities

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

frontkon.tech 10.0 kB · 0 ms CPU
smashingconf.com 3.7 kB · 0 ms CPU

Page health

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

Main thread work

other 275 ms
style layout 104 ms
script evaluation 58 ms
parse HTML 28 ms
paint composite render 19 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 462 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.

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1

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, 6:47 PM UTC 83 3.68 s 0 0 ms 356.1 kB 3/3 ±5 2,310 36.8s

Embed this score

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