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 ·

tomroseveare.com

https://www.tomroseveare.com/

89 100 92 100 –CWV 1AXE

Data from Aug 21, 2026, 2:40 PM UTC — 4h old.

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

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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Scores

89
Performance
no change
100
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.58 s — — 3.58 s 3.58 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 17 ms — — 17 ms 17 ms
FCP First Contentful Paint 2.00 s — — 2.00 s 2.00 s
Speed Index 2.00 s — — 2.00 s 2.00 s
TTFB Time to First Byte 673 ms — — 673 ms 673 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 93 ms
resource load duration 80 ms
time to first byte 54 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 452.9 kB — — 452.9 kB 452.9 kB
Requests 49 — — 49 49
Third-party Weight 24.6 kB — — 24.6 kB 24.6 kB
Third-party CPU 7 ms — — 7 ms 7 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 242.9 kB · 20 req
font 147.1 kB · 16 req
script 35.0 kB · 8 req
stylesheet 16.1 kB · 1 req
document 6.8 kB · 1 req
other 5.0 kB · 3 req
third party 24.6 kB · 4 req

Third parties 2 entities

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

Cloudflare CDN 23.9 kB · 7 ms CPU
netlify.app 688 B · 0 ms CPU

Page health

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

Main thread work

other 539 ms
style layout 233 ms
script evaluation 158 ms
paint composite render 103 ms
parse HTML 28 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

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

  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 2 console errors

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, 2:40 PM UTC 89 3.58 s 0.002 17 ms 452.9 kB 3/3 ±5 2,266 29.8s

Embed this score

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