speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

blades.ninja

https://blades.ninja/

67 77 100 82 29AXE –CWV

Data from Aug 20, 2026, 7:13 PM UTC 3d old

Built Awesome #1,092 · 1 measurement · since Aug 20, 2026

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.

Build Awesome Built with Build Awesome
Netlify Hosted by Netlify

Scores

67
Performance
no change
77
Accessibility
no change
100
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.18 s — — 7.18 s 7.18 s
CLS Cumulative Layout Shift 0.005 — — 0.005 0.005
TBT Total Blocking Time 163 ms — — 163 ms 163 ms
FCP First Contentful Paint 3.21 s — — 3.21 s 3.21 s
Speed Index 3.72 s — — 3.72 s 3.72 s
TTFB Time to First Byte 629 ms — — 629 ms 629 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 7.18 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 1.15 s
time to first byte 335 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 630 kB — — 630 kB 630 kB
Requests 43 — — 43 43
Third-party Weight 606 kB — — 606 kB 606 kB
Third-party CPU 84 ms — — 84 ms 84 ms
Unused JS 138 kB — — 138 kB 138 kB
Unused CSS 39.8 kB — — 39.8 kB 39.8 kB

By resource type

script 305 kB · 5 req
font 236 kB · 2 req
stylesheet 48.9 kB · 5 req
image 16.2 kB · 14 req
document 5.5 kB · 2 req
other 764 B · 14 req
third party 606 kB · 39 req

Third parties 7 entities

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

Google Tag Manager 294 kB · 71 ms CPU
JSDelivr CDN 291 kB · 11 ms CPU
gstatic.com 11.9 kB · 0 ms CPU
zgo.at 4.4 kB · 2 ms CPU
palletsprojects.com 3.0 kB · 0 ms CPU

Page health

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

Main thread work

other 382 ms
script evaluation 316 ms
style layout 274 ms
script parse compile 115 ms
paint composite render 67 ms
parse HTML 37 ms

Axe violations axe-core 4.13.0, full rule set

29 violating nodes across 5 rules, 831 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.

  • critical image-alt — Images must have alternative text 16 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 6 nodes
  • serious link-name — Links must have discernible text 5 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious object-alt — <object> elements must have alternative text 1 node

Accessibility failures 5 of 26 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.

  • image-alt — Image elements do not have `[alt]` attributes 16 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 6 nodes
  • link-name — Links do not have a discernible name 5 nodes
  • object-alt — `<object>` elements do not have alternate text 1 node
  • target-size — Touch targets do not have sufficient size or spacing. 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 20, 2026, 7:13 PM UTC 67 7.18 s 0.005 163 ms 630 kB 2/3 ±15 2,266 197.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show blades.ninja's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://blades.ninja/"></speedlify2-score>