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 ·

reachlightspeed.com

https://reachlightspeed.com/

99 100 100 100 –CWV 4AXE

Data from Aug 21, 2026, 5:36 AM UTC — 13h old.

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

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.

Netlify Hosted by Netlify

Scores

99
Performance
no change
100
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.55 s — — 1.55 s 1.55 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 53 ms — — 53 ms 53 ms
FCP First Contentful Paint 1.55 s — — 1.55 s 1.55 s
Speed Index 1.55 s — — 1.55 s 1.55 s
TTFB Time to First Byte 637 ms — — 637 ms 637 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 52 ms
time to first byte 43 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 243.1 kB — — 243.1 kB 243.1 kB
Requests 11 — — 11 11
Third-party Weight 174.6 kB — — 174.6 kB 174.6 kB
Third-party CPU 63 ms — — 63 ms 63 ms
Unused JS 68.4 kB — — 68.4 kB 68.4 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 174.6 kB · 2 req
other 61.3 kB · 8 req
document 7.2 kB · 1 req
third party 174.6 kB · 3 req

Third parties 3 entities

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

Google Tag Manager 163.1 kB · 60 ms CPU
Cloudflare 11.5 kB · 3 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.65 s — — 1.65 s 1.65 s
Long Tasks 2 — — 2 2
DOM Elements 76 — — 76 76
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 1 — — 1 1

Main thread work

other 1.02 s
script evaluation 477 ms
style layout 54 ms
script parse compile 48 ms
paint composite render 36 ms
garbage collection 13 ms
parse HTML 10 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 1 rule, 90 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 region — All page content should be contained by landmarks 4 nodes

Accessibility failures 1 of 17 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

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, 5:36 AM UTC 99 1.55 s 0 53 ms 243.1 kB 3/3 ±2 2,381 22.8s

Embed this score

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