speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

raymondcamden.com

https://www.raymondcamden.com/

100 96 100 100 7AXE ✓CWV

Data from Aug 21, 2026, 7:28 PM UTC 2d old

Built Awesome #799 · 1 measurement · since Aug 21, 2026

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 3.0.0 Built with Eleventy 3.0.0
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.48 s good
INP 83 ms good
CLS 0 good

Scores

100
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.53 s — — 1.53 s 1.53 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 813 ms — — 813 ms 813 ms
Speed Index 2.20 s — — 2.20 s 2.20 s
TTFB Time to First Byte 1.23 s — — 1.23 s 1.23 s

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.53 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 1.23 s
element render delay 98 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.48 s good 88.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 83 ms good 96.1% good
CLS CWV 0 good 92.7% good
FCP 1.44 s good 82.5% good
TTFB 969 ms needs-improvement 67.5% good

Lab vs field

Lab LCP 1.53 s · field p75 1.48 s · real users are 0.97× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.47 s 77 ms 0 1.42 s 985 ms
2026-08-08 1.44 s 72 ms 0 1.38 s 979 ms
2026-08-01 1.44 s 73 ms 0 1.37 s 969 ms
2026-07-25 1.42 s 77 ms 0 1.37 s 953 ms
2026-07-18 1.40 s 78 ms 0 1.32 s 953 ms
2026-07-11 1.46 s 81 ms 0 1.37 s 975 ms
2026-07-04 1.51 s 76 ms 0 1.41 s 1.05 s
2026-06-27 1.44 s 76 ms 0 1.38 s 1.08 s
2026-06-20 1.41 s 71 ms 0 1.31 s 933 ms
2026-06-13 1.31 s 73 ms 0 1.24 s 869 ms
2026-06-06 1.26 s 78 ms 0 1.22 s 799 ms
2026-05-30 1.33 s 73 ms 0 1.24 s 870 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 69.0 kB — — 69.0 kB 69.0 kB
Requests 14 — — 14 14
Third-party Weight 7.5 kB — — 7.5 kB 7.5 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

script 25.8 kB · 5 req
other 21.5 kB · 3 req
stylesheet 5.7 kB · 2 req
font 4.9 kB · 1 req
document 4.0 kB · 1 req
image 2.8 kB · 1 req
third party 7.5 kB · 3 req

Third parties 3 entities

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

zgo.at 4.3 kB · 2 ms CPU
Cloudinary 2.8 kB · 0 ms CPU
goatcounter.com 380 B · 0 ms CPU

Page health

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

Main thread work

other 104 ms
style layout 64 ms
script evaluation 40 ms
parse HTML 13 ms
paint composite render 9 ms
script parse compile 8 ms

Axe violations axe-core 4.13.0, full rule set

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

Accessibility failures 1 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. 7 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, 7:28 PM UTC 100 1.53 s 0 0 ms 69.0 kB 3/3 ±5 2,464 23.9s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show raymondcamden.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.raymondcamden.com/"></speedlify2-score>