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 ·

mxb.dev

https://mxb.dev/

99 100 100 100 ✓CWV 0AXE

Data from Aug 21, 2026, 4:47 AM UTC — 14h old.

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

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.0.0 Built with Eleventy 3.0.0
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.23 s good
INP — no data
CLS 0 good

Scores

99
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.98 s — — 1.98 s 1.98 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 904 ms — — 904 ms 904 ms
Speed Index 904 ms — — 904 ms 904 ms
TTFB Time to First Byte 604 ms — — 604 ms 604 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 64 ms
resource load delay 10 ms
resource load duration 8 ms
time to first byte 6 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.23 s good 93.7% good
CLS CWV 0 good 95.5% good
FCP 1.23 s good 88% good
TTFB 848 ms needs-improvement 72.3% good

Lab vs field

Lab LCP 1.98 s · field p75 1.23 s · real users are 0.62× 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 1.49 s — 0 1.49 s 961 ms
2026-08-08 1.40 s — 0 1.37 s 942 ms
2026-08-01 1.25 s — 0 1.18 s 864 ms
2026-07-25 1.07 s — 0 1.01 s 710 ms
2026-07-18 1.12 s — 0 1.11 s 710 ms
2026-07-11 1.42 s — 0 1.35 s 805 ms
2026-07-04 1.47 s — 0 1.45 s 837 ms
2026-06-27 1.52 s — 0 1.48 s 805 ms
2026-06-20 1.46 s — 0 1.35 s 881 ms
2026-06-13 1.29 s — 0 1.20 s 747 ms
2026-06-06 1.21 s — 0 1.18 s 656 ms
2026-05-30 1.13 s — 0 1.12 s 612 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 214.8 kB — — 214.8 kB 214.8 kB
Requests 19 — — 19 19
Third-party Weight 0 B — — 0 B 0 B
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 85.1 kB · 8 req
other 66.0 kB · 5 req
font 31.6 kB · 1 req
script 13.1 kB · 1 req
stylesheet 10.8 kB · 2 req
document 8.2 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 321 ms — — 321 ms 321 ms
Long Tasks 0 — — 0 0
DOM Elements 297 — — 297 297
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 162 ms
style layout 91 ms
script evaluation 37 ms
parse HTML 16 ms
paint composite render 14 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 355 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 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, 4:47 AM UTC 99 1.98 s 0 0 ms 214.8 kB 3/3 ±4 2,472 21.5s

Embed this score

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