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 ·

ryanprintup.com

https://ryanprintup.com/

93 96 100 100 –CWV 4AXE

Data from Aug 21, 2026, 3:34 PM UTC — 3h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 3h

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.

Self-hosted · nginx Hosted by Self-hosted

Scores

93
Performance
no change
96
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.85 s — — 1.85 s 1.85 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 299 ms — — 299 ms 299 ms
FCP First Contentful Paint 950 ms — — 950 ms 950 ms
Speed Index 1.28 s — — 1.28 s 1.28 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.

element render delay 109 ms
time to first byte 52 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 11.85 MB — — 11.85 MB 11.85 MB
Requests 34 — — 34 34
Third-party Weight 325.5 kB — — 325.5 kB 325.5 kB
Third-party CPU 60 ms — — 60 ms 60 ms
Unused JS 132.2 kB — — 132.2 kB 132.2 kB
Unused CSS 14.5 kB — — 14.5 kB 14.5 kB

By resource type

media 8.45 MB · 1 req
image 3.08 MB · 14 req
script 247.9 kB · 8 req
font 37.6 kB · 2 req
stylesheet 25.0 kB · 4 req
document 6.9 kB · 1 req
other 5.7 kB · 3 req
third party 325.5 kB · 14 req

Third parties 4 entities

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

curator.io 123.6 kB · 32 ms CPU
YouTube 112.7 kB · 4 ms CPU
Facebook 86.1 kB · 25 ms CPU
bandsintown.com 3.0 kB · 0 ms CPU

Page health

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

Main thread work

other 694 ms
script evaluation 432 ms
style layout 131 ms
script parse compile 105 ms
paint composite render 34 ms
parse HTML 23 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 1 rule, 617 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 4 nodes

Accessibility failures 1 of 23 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. 4 nodes

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:34 PM UTC 93 1.85 s 0 299 ms 11.85 MB 3/3 ±27 2,314 44.6s

Embed this score

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