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 ·

davidrhoden.com

https://davidrhoden.com/

57 94 77 100 CWV 1AXE

Data from Aug 20, 2026, 7:36 PM UTC — 23h old.

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

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

57
Performance
no change
94
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.46 s 7.46 s 7.46 s
CLS Cumulative Layout Shift 0.161 0.161 0.161
TBT Total Blocking Time 185 ms 185 ms 185 ms
FCP First Contentful Paint 3.85 s 3.85 s 3.85 s
Speed Index 3.85 s 3.85 s 3.85 s
TTFB Time to First Byte 650 ms 650 ms 650 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 duration 339 ms
time to first byte 31 ms
element render delay 30 ms
resource load delay 15 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.09 MB 1.09 MB 1.09 MB
Requests 43 43 43
Third-party Weight 586.6 kB 586.6 kB 586.6 kB
Third-party CPU 129 ms 129 ms 129 ms
Unused JS 185.0 kB 185.0 kB 185.0 kB
Unused CSS 15.2 kB 15.2 kB 15.2 kB

By resource type

image 538.2 kB · 16 req
script 352.0 kB · 8 req
font 91.8 kB · 4 req
document 89.1 kB · 1 req
stylesheet 8.6 kB · 6 req
other 2.9 kB · 7 req
third party 586.6 kB · 32 req

Third parties 9 entities

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

Google Tag Manager 183.3 kB · 62 ms CPU
YouTube 156.2 kB · 0 ms CPU
PayPal 102.8 kB · 29 ms CPU
Google Fonts 93.5 kB · 0 ms CPU
Clarity 27.3 kB · 30 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.26 s 1.26 s 1.26 s
Long Tasks 6 6 6
DOM Elements 508 508 508
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 28 28 28

Main thread work

script evaluation 597 ms
other 304 ms
script parse compile 144 ms
style layout 131 ms
parse HTML 51 ms
paint composite render 31 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 73 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 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 27 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, 7:36 PM UTC 57 7.46 s 0.161 185 ms 1.09 MB 3/3 ±18 2,485 32.1s

Embed this score

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