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 ·

tanstack.com

https://tanstack.com/

48 84 100 92 ✗CWV 23AXE

Data from Aug 21, 2026, 9:35 AM UTC — 9h old.

Site Generators · 1 measurement · since Aug 21, 2026 · last attempt 9h

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

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

LCP 3.61 s needs-improvement
INP 388 ms needs-improvement
CLS 0.010 good

Scores

48
Performance
no change
84
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.91 s — — 7.91 s 7.91 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 607 ms — — 607 ms 607 ms
FCP First Contentful Paint 4.18 s — — 4.18 s 4.18 s
Speed Index 5.36 s — — 5.36 s 5.36 s
TTFB Time to First Byte 494 ms — — 494 ms 494 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 1.21 s
time to first byte 314 ms
resource load duration 23 ms
resource load delay 18 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 3.61 s needs-improvement 47.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 388 ms needs-improvement 43% good
CLS CWV 0.010 good 93.3% good
FCP 3.32 s poor 31.7% good
TTFB 2.61 s poor 15.5% good

Lab vs field

Lab LCP 7.91 s · field p75 3.61 s · real users are 0.46× 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 3.59 s 389 ms 0.010 3.31 s 2.62 s
2026-08-08 3.59 s 373 ms 0.010 3.35 s 2.66 s
2026-08-01 3.50 s 341 ms 0.010 3.34 s 2.67 s
2026-07-25 3.70 s 318 ms 0 3.52 s 2.85 s
2026-07-18 3.72 s 294 ms 0 3.55 s 2.87 s
2026-07-11 3.34 s 294 ms 0 3.16 s 2.54 s
2026-07-04 2.85 s 314 ms 0 2.67 s 2.10 s
2026-06-27 2.27 s 319 ms 0 2.00 s 1.23 s
2026-06-20 2.02 s 352 ms 0 1.81 s 1.01 s
2026-06-13 1.98 s 364 ms 0 1.82 s 999 ms
2026-06-06 1.84 s 372 ms 0 1.72 s 912 ms
2026-05-30 1.85 s 387 ms 0 1.74 s 946 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.07 MB — — 3.07 MB 3.07 MB
Requests 57 — — 57 57
Third-party Weight 119.9 kB — — 119.9 kB 119.9 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 354.2 kB — — 354.2 kB 354.2 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

media 1.57 MB · 2 req
script 665.5 kB · 33 req
image 521.4 kB · 5 req
font 180.6 kB · 5 req
stylesheet 72.9 kB · 2 req
document 41.1 kB · 1 req
other 13.6 kB · 8 req
third party 119.9 kB · 7 req

Third parties 3 entities

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

Google Fonts 108.3 kB · 0 ms CPU
Cloudflare 11.5 kB · 2 ms CPU
Sentry 132 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 4.95 s — — 4.95 s 4.95 s
Long Tasks 13 — — 13 13
DOM Elements 1,037 — — 1,037 1,037
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 23 — — 23 23
A11y Failures 4 — — 4 4
A11y Failing Nodes 9 — — 9 9

Main thread work

script evaluation 1.58 s
style layout 1.31 s
other 1.31 s
paint composite render 333 ms
script parse compile 285 ms
parse HTML 112 ms
garbage collection 31 ms

Axe violations axe-core 4.13.0, full rule set

23 violating nodes across 4 rules, 674 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 16 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 5 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 4 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. 6 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • label — Form elements do not have associated labels 1 node

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 21, 2026, 9:35 AM UTC 48 7.91 s 0 607 ms 3.07 MB 3/3 ±7 2,112 64.9s

Embed this score

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