speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

brew.sh

https://brew.sh/

75 96 100 92 ✗AXE ✓CWV

Data from Aug 25, 2026, 4:36 PM UTC 13h old

Overall #1,245 Package Managers #7 · 1 measurement · since Aug 25, 2026

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.

Jekyll 4.4.1 Built with Jekyll 4.4.1
GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

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

LCP 1.34 s good
INP 123 ms good
CLS 0 good

Scores

75
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 9.75 s — — 9.75 s 9.75 s
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.55 s — — 1.55 s 1.55 s
Speed Index 1.55 s — — 1.55 s 1.55 s
TTFB Time to First Byte 602 ms — — 602 ms 602 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 9.75 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 95 ms
time to first byte 4 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.34 s good 93.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 123 ms good 89.9% good
CLS CWV 0 good 94.8% good
FCP 1.30 s good 87.4% good
TTFB 650 ms good 80.4% good

Lab vs field

Lab LCP 9.75 s · field p75 1.34 s · real users are 0.14× 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-22 1.34 s 124 ms 0 1.30 s 652 ms
2026-08-15 1.32 s 122 ms 0 1.30 s 657 ms
2026-08-08 1.32 s 129 ms 0 1.29 s 650 ms
2026-08-01 1.31 s 127 ms 0 1.29 s 650 ms
2026-07-25 1.30 s 125 ms 0 1.27 s 646 ms
2026-07-18 1.30 s 136 ms 0 1.26 s 635 ms
2026-07-11 1.27 s 134 ms 0 1.24 s 626 ms
2026-07-04 1.25 s 137 ms 0 1.21 s 602 ms
2026-06-27 1.24 s 143 ms 0 1.21 s 614 ms
2026-06-20 1.21 s 130 ms 0 1.19 s 602 ms
2026-06-13 1.19 s 128 ms 0 1.18 s 604 ms
2026-06-06 1.19 s 134 ms 0 1.19 s 614 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.70 MB — — 1.70 MB 1.70 MB
Requests 9 — — 9 9
Third-party Weight 37.5 kB — — 37.5 kB 37.5 kB
Third-party CPU 6 ms — — 6 ms 6 ms
Unused JS 25.7 kB — — 25.7 kB 25.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.64 MB · 3 req
script 34.2 kB · 2 req
stylesheet 8.7 kB · 2 req
document 7.5 kB · 1 req
third party 37.5 kB · 3 req

Third parties 1 entities

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

Cloudflare CDN 37.5 kB · 6 ms CPU

Page health

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

Main thread work

style layout 161 ms
other 142 ms
script evaluation 49 ms
script parse compile 18 ms
parse HTML 16 ms
paint composite render 15 ms

Axe violations axe-core 4.13.0, full rule set

33 violating nodes across 2 rules, 656 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 27 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 6 nodes

Accessibility failures 1 of 24 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. 26 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 25, 2026, 4:36 PM UTC 75 9.75 s 0.004 0 ms 1.70 MB 3/3 ±23 2,461 26.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show brew.sh's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://brew.sh/"></speedlify2-score>