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 ·

magicball.net

https://magicball.net/

96 94 100 92 –CWV 6AXE

Data from Aug 21, 2026, 4:39 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 Built with Eleventy
Self-hosted · Apache Hosted by Self-hosted

Scores

96
Performance
no change
94
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.30 s — — 2.30 s 2.30 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.47 s — — 1.47 s 1.47 s
Speed Index 3.88 s — — 3.88 s 3.88 s
TTFB Time to First Byte 1.02 s — — 1.02 s 1.02 s

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.35 s
resource load delay 720 ms
time to first byte 142 ms
resource load duration 142 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 185.6 kB — — 185.6 kB 185.6 kB
Requests 16 — — 16 16
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 23.6 kB — — 23.6 kB 23.6 kB
Unused CSS 34.4 kB — — 34.4 kB 34.4 kB

By resource type

image 112.3 kB · 11 req
stylesheet 37.5 kB · 1 req
script 29.5 kB · 1 req
document 3.5 kB · 1 req
other 2.8 kB · 1 req

Page health

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

Main thread work

other 90 ms
style layout 47 ms
script evaluation 17 ms
parse HTML 13 ms
script parse compile 7 ms
paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 177 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 5 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 22 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. 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, 4:39 AM UTC 96 2.30 s 0 0 ms 185.6 kB 3/3 ±3 3,086 27.3s

Embed this score

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