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 ·

chadams.me

https://www.chadams.me/

66 98 100 100 –CWV 3AXE

Data from Aug 21, 2026, 11:29 AM UTC — 7h old.

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

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

66
Performance
no change
98
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 28.31 s — — 28.31 s 28.31 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 8 ms — — 8 ms 8 ms
FCP First Contentful Paint 1.11 s — — 1.11 s 1.11 s
Speed Index 10.59 s — — 10.59 s 10.59 s
TTFB Time to First Byte 615 ms — — 615 ms 615 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 177 ms
resource load duration 33 ms
resource load delay 10 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 9.56 MB — — 9.56 MB 9.56 MB
Requests 20 — — 20 20
Third-party Weight 2.4 kB — — 2.4 kB 2.4 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 42.0 kB — — 42.0 kB 42.0 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 9.42 MB · 7 req
script 119.1 kB · 9 req
stylesheet 8.8 kB · 1 req
document 5.4 kB · 1 req
other 521 B · 1 req
third party 2.4 kB · 2 req

Third parties 1 entities

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

Plausible 2.4 kB · 2 ms CPU

Page health

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

Main thread work

other 388 ms
script evaluation 214 ms
style layout 55 ms
script parse compile 31 ms
parse HTML 21 ms
paint composite render 12 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 231 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 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

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

  • landmark-one-main — Document does not have a main landmark. 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, 11:29 AM UTC 66 28.31 s 0 8 ms 9.56 MB 3/3 ±0 2,454 22.9s

Embed this score

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