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 ·

manu.ninja

https://manu.ninja/

99 80 100 100 CWV 56AXE

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

Built Awesome · 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.

Cloudflare Hosted by Cloudflare

Scores

99
Performance
no change
80
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.07 s 1.07 s 1.07 s
CLS Cumulative Layout Shift 0.046 0.046 0.046
TBT Total Blocking Time 90 ms 90 ms 90 ms
FCP First Contentful Paint 838 ms 838 ms 838 ms
Speed Index 838 ms 838 ms 838 ms
TTFB Time to First Byte 621 ms 621 ms 621 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.

time to first byte 202 ms
element render delay 60 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 411.3 kB 411.3 kB 411.3 kB
Requests 11 11 11
Third-party Weight 312.6 kB 312.6 kB 312.6 kB
Third-party CPU 86 ms 86 ms 86 ms
Unused JS 137.8 kB 137.8 kB 137.8 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 313.6 kB · 4 req
image 56.2 kB · 2 req
font 16.0 kB · 1 req
document 13.7 kB · 1 req
other 10.3 kB · 2 req
third party 312.6 kB · 3 req

Third parties 2 entities

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

Google Tag Manager 291.7 kB · 76 ms CPU
Google Analytics 20.9 kB · 10 ms CPU

Page health

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

Main thread work

script evaluation 331 ms
other 133 ms
style layout 102 ms
script parse compile 80 ms
paint composite render 27 ms
parse HTML 13 ms

Axe violations axe-core 4.13.0, full rule set

56 violating nodes across 3 rules, 1352 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 52 nodes
  • 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 3 of 13 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.

  • target-size — Touch targets do not have sufficient size or spacing. 132 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 52 nodes
  • 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

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:13 AM UTC 99 1.07 s 0.046 90 ms 411.3 kB 3/3 ±0 2,464 30.4s

Embed this score

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