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 ·

aaronmorey.com

https://aaronmorey.com/

77 94 100 92 –CWV 1AXE

Data from Aug 20, 2026, 4:24 PM UTC — 26h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 26h

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.

Cloudflare Hosted by Cloudflare

Scores

77
Performance
no change
94
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.97 s — — 5.97 s 5.97 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.99 s — — 1.99 s 1.99 s
Speed Index 1.99 s — — 1.99 s 1.99 s
TTFB Time to First Byte 471 ms — — 471 ms 471 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 120 ms
time to first byte 18 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.29 MB — — 1.29 MB 1.29 MB
Requests 25 — — 25 25
Third-party Weight 11.4 kB — — 11.4 kB 11.4 kB
Third-party CPU 4 ms — — 4 ms 4 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 18.4 kB — — 18.4 kB 18.4 kB

By resource type

font 1.12 MB · 8 req
image 64.3 kB · 5 req
script 53.5 kB · 2 req
stylesheet 39.1 kB · 5 req
document 4.4 kB · 1 req
other 1.2 kB · 2 req
third party 11.4 kB · 1 req

Third parties 1 entities

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

Cloudflare 11.4 kB · 4 ms CPU

Page health

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

Main thread work

other 211 ms
style layout 109 ms
script evaluation 74 ms
parse HTML 35 ms
paint composite render 16 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

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

  • critical meta-refresh — Delayed refresh under 20 hours must not be used 1 node

Accessibility failures 2 of 22 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.

  • target-size — Touch targets do not have sufficient size or spacing. 7 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 h3

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 20, 2026, 4:24 PM UTC 77 5.97 s 0 0 ms 1.29 MB 3/3 ±13 2,472 25.1s

Embed this score

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