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 ·

mx.sb

https://www.mx.sb/

91 96 96 92 –CWV 4AXE

Data from Aug 21, 2026, 1:50 PM UTC — 5h old.

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

Scores

91
Performance
no change
96
Accessibility
no change
96
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.50 s — — 3.50 s 3.50 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 944 ms — — 944 ms 944 ms
Speed Index 1.08 s — — 1.08 s 1.08 s
TTFB Time to First Byte 789 ms — — 789 ms 789 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.

resource load delay 217 ms
time to first byte 190 ms
element render delay 71 ms
resource load duration 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.59 MB — — 1.59 MB 1.59 MB
Requests 45 — — 45 45
Third-party Weight 225.9 kB — — 225.9 kB 225.9 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 1.57 MB · 30 req
script 13.3 kB · 1 req
document 1.1 kB · 1 req
other 228 B · 12 req
third party 226.1 kB · 36 req

Third parties 2 entities

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

ucarecdn.com 204.3 kB · 0 ms CPU
gstatic.com 21.6 kB · 0 ms CPU

Page health

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

Main thread work

other 277 ms
style layout 100 ms
script evaluation 35 ms
paint composite render 20 ms
parse HTML 4 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 2 rules, 198 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 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 12 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.

  • landmark-one-main — Document does not have a main landmark. 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 3 console errors

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, 1:50 PM UTC 91 3.50 s 0 0 ms 1.59 MB 3/3 ±2 2,453 25s

Embed this score

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