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 ·

rajeevedmonds.com

https://www.rajeevedmonds.com/

94 94 100 100 –CWV 8AXE

Data from Aug 21, 2026, 1:53 PM UTC — 5h old.

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

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

94
Performance
no change
94
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 2.47 s — — 2.47 s 2.47 s
CLS Cumulative Layout Shift 0.010 — — 0.010 0.010
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.47 s — — 2.47 s 2.47 s
Speed Index 2.47 s — — 2.47 s 2.47 s
TTFB Time to First Byte 619 ms — — 619 ms 619 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 95 ms
time to first byte 21 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 59.6 kB — — 59.6 kB 59.6 kB
Requests 9 — — 9 9
Third-party Weight 32.2 kB — — 32.2 kB 32.2 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 31.4 kB · 1 req
image 11.5 kB · 1 req
stylesheet 6.4 kB · 3 req
document 5.9 kB · 1 req
script 4.1 kB · 2 req
other 388 B · 1 req
third party 32.2 kB · 2 req

Third parties 1 entities

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

Google Fonts 32.2 kB · 0 ms CPU

Page health

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

Main thread work

other 228 ms
style layout 193 ms
paint composite render 154 ms
script evaluation 59 ms
parse HTML 15 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 2 rules, 430 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 7 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 24 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. 11 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 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, 1:53 PM UTC 94 2.47 s 0.010 0 ms 59.6 kB 3/3 ±5 2,488 23.1s

Embed this score

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