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 ·

coreydmccarty.dev

https://coreydmccarty.dev/

92 100 100 100 –CWV 0AXE

Data from Aug 20, 2026, 7:39 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.

GitHub Pages Hosted by GitHub Pages

Scores

92
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 2.73 s — — 2.73 s 2.73 s
CLS Cumulative Layout Shift 0.050 — — 0.050 0.050
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.73 s — — 2.73 s 2.73 s
Speed Index 2.73 s — — 2.73 s 2.73 s
TTFB Time to First Byte 711 ms — — 711 ms 711 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.

time to first byte 306 ms
element render delay 105 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 243.5 kB — — 243.5 kB 243.5 kB
Requests 15 — — 15 15
Third-party Weight 236.9 kB — — 236.9 kB 236.9 kB
Third-party CPU 6 ms — — 6 ms 6 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 12.2 kB — — 12.2 kB 12.2 kB

By resource type

font 208.4 kB · 7 req
other 20.0 kB · 3 req
script 5.9 kB · 1 req
document 5.7 kB · 1 req
stylesheet 2.5 kB · 2 req
third party 236.9 kB · 13 req

Third parties 3 entities

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

FontAwesome CDN 182.3 kB · 6 ms CPU
Google Fonts 53.3 kB · 0 ms CPU
Unpkg 1.3 kB · 0 ms CPU

Page health

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

Main thread work

style layout 152 ms
other 130 ms
script evaluation 68 ms
paint composite render 36 ms
parse HTML 6 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 204 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.

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 20, 2026, 7:39 PM UTC 92 2.73 s 0.050 0 ms 243.5 kB 3/3 ±3 4,259 21s

Embed this score

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