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 ·

carteakey.dev

https://carteakey.dev/

76 92 100 100 ✓CWV 23AXE

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

Built Awesome · 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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

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

LCP 1.81 s good
INP — no data
CLS 0 good

Scores

76
Performance
no change
92
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 6.18 s — — 6.18 s 6.18 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 91 ms — — 91 ms 91 ms
FCP First Contentful Paint 1.87 s — — 1.87 s 1.87 s
Speed Index 1.87 s — — 1.87 s 1.87 s
TTFB Time to First Byte 490 ms — — 490 ms 490 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 251 ms
time to first byte 66 ms

Field data Chrome UX Report, origin-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.81 s good 83.1% good
CLS CWV 0 good 84.7% good
FCP 1.30 s good 85.2% good
TTFB 829 ms needs-improvement 74.2% good

Lab vs field

Lab LCP 6.18 s · field p75 1.81 s · real users are 0.29× 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.87 s — 0 1.36 s 829 ms
2026-08-08 2.31 s — 0.020 1.64 s 862 ms
2026-08-01 2.19 s — 0.010 1.62 s 829 ms
2026-07-25 2.23 s 49 ms 0.070 1.70 s 803 ms
2026-07-18 2.11 s 53 ms 0.070 1.68 s 733 ms
2026-07-11 2.08 s 53 ms 0.040 1.65 s 719 ms
2026-07-04 2.08 s 51 ms 0.040 1.68 s 717 ms
2026-06-27 2.08 s 53 ms 0.040 1.65 s 709 ms
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 1.70 s — 0 1.21 s 609 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 906.1 kB — — 906.1 kB 906.1 kB
Requests 30 — — 30 30
Third-party Weight 381.2 kB — — 381.2 kB 381.2 kB
Third-party CPU 77 ms — — 77 ms 77 ms
Unused JS 73.9 kB — — 73.9 kB 73.9 kB
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

font 310.3 kB · 4 req
image 279.3 kB · 10 req
script 268.1 kB · 10 req
stylesheet 28.3 kB · 2 req
document 17.1 kB · 1 req
other 3.1 kB · 3 req
third party 381.2 kB · 5 req

Third parties 5 entities

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

Google Tag Manager 168.0 kB · 50 ms CPU
Spotify 143.1 kB · 0 ms CPU
Netlify 55.3 kB · 23 ms CPU
Cloudflare 11.5 kB · 5 ms CPU
JSDelivr CDN 3.4 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.17 s — — 1.17 s 1.17 s
Long Tasks 4 — — 4 4
DOM Elements 782 — — 782 782
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 23 — — 23 23
A11y Failures 3 — — 3 3
A11y Failing Nodes 35 — — 35 35

Main thread work

script evaluation 381 ms
other 313 ms
style layout 268 ms
script parse compile 88 ms
paint composite render 62 ms
parse HTML 40 ms
garbage collection 19 ms

Axe violations axe-core 4.13.0, full rule set

23 violating nodes across 3 rules, 955 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 18 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes

Accessibility failures 3 of 32 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. 17 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 16 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes

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:27 PM UTC 76 6.18 s 0.002 91 ms 906.1 kB 3/3 ±18 3,390 38.5s

Embed this score

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