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 ·

withleaf.io

https://withleaf.io/

59 96 77 100 –CWV 5AXE

Data from Aug 21, 2026, 10:36 AM UTC — 8h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 8h

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.

Cl Hosted by CloudFront

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

59
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 10.17 s — — 10.17 s 10.17 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 346 ms — — 346 ms 346 ms
FCP First Contentful Paint 1.58 s — — 1.58 s 1.58 s
Speed Index 7.33 s — — 7.33 s 7.33 s
TTFB Time to First Byte 639 ms — — 639 ms 639 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.

resource load duration 182 ms
time to first byte 147 ms
element render delay 54 ms
resource load delay 10 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 2.40 s — 0 1.92 s 959 ms
2026-06-27 2.39 s — 0 2.11 s 939 ms
2026-06-20 2.45 s — 0 2.15 s —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.32 MB — — 4.32 MB 4.32 MB
Requests 41 — — 41 41
Third-party Weight 345.5 kB — — 345.5 kB 345.5 kB
Third-party CPU 123 ms — — 123 ms 123 ms
Unused JS 136.4 kB — — 136.4 kB 136.4 kB
Unused CSS 19.6 kB — — 19.6 kB 19.6 kB

By resource type

image 3.91 MB · 22 req
script 361.8 kB · 10 req
stylesheet 26.3 kB · 2 req
other 9.4 kB · 5 req
document 8.3 kB · 1 req
third party 345.5 kB · 11 req

Third parties 7 entities

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

Google Tag Manager 190.5 kB · 88 ms CPU
Mixpanel 138.2 kB · 30 ms CPU
cloudfront.net 10.4 kB · 2 ms CPU
Google/Doubleclick Ads 2.7 kB · 1 ms CPU
Plausible 2.4 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.83 s — — 1.83 s 1.83 s
Long Tasks 7 — — 7 7
DOM Elements 500 — — 500 500
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 5 — — 5 5
A11y Failures 1 — — 1 1
A11y Failing Nodes 5 — — 5 5

Main thread work

script evaluation 775 ms
other 634 ms
style layout 190 ms
script parse compile 108 ms
paint composite render 84 ms
parse HTML 36 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 3 rules, 18 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.

  • moderate region — All page content should be contained by landmarks 3 nodes
  • serious html-has-lang — <html> element must have a lang attribute 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 26 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. 5 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 21, 2026, 10:36 AM UTC 59 10.17 s 0 346 ms 4.32 MB 3/3 ±7 2,286 31.6s

Embed this score

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