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 ·

darius.codes

https://darius.codes/

74 93 100 100 CWV 1AXE

Data from Aug 20, 2026, 8:29 PM UTC — 22h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 22h

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

74
Performance
no change
93
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 4.44 s 4.44 s 4.44 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 4.36 s 4.36 s 4.36 s
Speed Index 4.36 s 4.36 s 4.36 s
TTFB Time to First Byte 505 ms 505 ms 505 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 247 ms
time to first byte 45 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 451.1 kB 451.1 kB 451.1 kB
Requests 38 38 38
Third-party Weight 11.5 kB 11.5 kB 11.5 kB
Third-party CPU 4 ms 4 ms 4 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

font 326.6 kB · 5 req
script 105.5 kB · 25 req
stylesheet 11.1 kB · 4 req
document 6.9 kB · 1 req
other 1.0 kB · 2 req
third party 11.5 kB · 1 req

Third parties 1 entities

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

Cloudflare 11.5 kB · 4 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.14 s 1.14 s 1.14 s
Long Tasks 3 3 3
DOM Elements 263 263 263
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 1 1
A11y Failures 2 2 2
A11y Failing Nodes 42 42 42

Main thread work

other 667 ms
script evaluation 213 ms
style layout 208 ms
paint composite render 24 ms
parse HTML 24 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 69 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 meta-refresh — Delayed refresh under 20 hours must not be used 1 node

Accessibility failures 2 of 21 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. 41 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 h3

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, 8:29 PM UTC 74 4.44 s 0.001 0 ms 451.1 kB 3/3 ±15 2,366 28.3s

Embed this score

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