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 ·

brennan.day

https://brennan.day/

87 88 96 77 CWV 12AXE

Data from Aug 20, 2026, 7:31 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.

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.82 s good
INP 69 ms good
CLS 0 good

Scores

87
Performance
no change
88
Accessibility
no change
96
Best Practices
no change
77
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.28 s 3.28 s 3.28 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.97 s 2.97 s 2.97 s
Speed Index 3.25 s 3.25 s 3.25 s
TTFB Time to First Byte 1.01 s 1.01 s 1.01 s

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 1.01 s
element render delay 367 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.82 s good 86.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 69 ms good 98.5% good
CLS CWV 0 good 84.1% good
FCP 1.63 s good 79.1% good
TTFB 1.54 s needs-improvement 28.3% good

Lab vs field

Lab LCP 3.28 s · field p75 1.82 s · real users are 0.56× 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.81 s 67 ms 0 1.57 s 1.56 s
2026-08-08 1.82 s 67 ms 0 1.57 s 1.57 s
2026-08-01 2.26 s 67 ms 0.020 1.84 s 1.64 s
2026-07-25 2.30 s 60 ms 0.020 1.84 s 1.59 s
2026-07-18 2.32 s 59 ms 0.070 1.85 s 1.58 s
2026-07-11 2.34 s 59 ms 0.090 1.85 s 1.59 s
2026-07-04 2.19 s 0.210 1.77 s 1.61 s
2026-06-27 2.13 s 68 ms 0.070 1.84 s 1.68 s
2026-06-20 2.21 s 65 ms 0 1.84 s 1.67 s
2026-06-13 2.22 s 63 ms 0 1.85 s 1.69 s
2026-06-06 2.23 s 63 ms 0 1.85 s 1.65 s
2026-05-30 2.34 s 61 ms 0 1.90 s 1.71 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 427.2 kB 427.2 kB 427.2 kB
Requests 78 78 78
Third-party Weight 77.8 kB 77.8 kB 77.8 kB
Third-party CPU 11 ms 11 ms 11 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 240.2 kB · 43 req
script 54.3 kB · 10 req
stylesheet 53.4 kB · 16 req
document 43.8 kB · 1 req
other 18.8 kB · 6 req
font 12.8 kB · 1 req
third party 77.7 kB · 27 req

Third parties 12 entities

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

JSDelivr CDN 20.3 kB · 5 ms CPU
webring.fun 16.2 kB · 2 ms CPU
Google Fonts 13.4 kB · 0 ms CPU
possiblyaxolotl.com 9.2 kB · 2 ms CPU
aaronparecki.com 5.2 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.11 s 1.11 s 1.11 s
Long Tasks 2 2 2
DOM Elements 2,057 2,057 2,057
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 12 12 12
A11y Failures 3 3 3
A11y Failing Nodes 14 14 14

Main thread work

other 473 ms
style layout 331 ms
paint composite render 107 ms
script evaluation 89 ms
parse HTML 68 ms
script parse compile 37 ms
garbage collection 7 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 4 rules, 4546 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 link-name — Links must have discernible text 6 nodes
  • critical image-alt — Images must have alternative text 3 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 3 of 30 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.

  • link-name — Links do not have a discernible name 6 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 5 nodes
  • image-alt — Image elements do not have `[alt]` attributes 3 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 20, 2026, 7:31 PM UTC 87 3.28 s 0 0 ms 427.2 kB 3/3 ±11 2,347 45.9s

Embed this score

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