tanstack.com
Data from Aug 23, 2026, 10:22 AM UTC 11h old
Site Generators #20 · 3 measurements · since Aug 21, 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.
Core Web Vitals field data, url-level
Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 3.96 s.
-
494 ms
-
989 ms
-
1.48 s
-
1.98 s
-
2.47 s
-
2.97 s
-
3.46 s
-
3.96 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 7.17 s | 7.37 s | ↓ -197 ms (-2.7%) | 7.17 s | 7.91 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 570 ms | 565 ms | ↑ +5 ms (+0.9%) | 565 ms | 607 ms | |
| FCP First Contentful Paint | 4.13 s | 4.23 s | ↓ -102 ms (-2.4%) | 4.13 s | 4.23 s | |
| Speed Index | 4.83 s | 4.34 s | ↑ +481 ms (+11.1%) | 4.34 s | 5.36 s | |
| TTFB Time to First Byte | 473 ms | 619 ms | ↓ -146 ms (-23.6%) | 473 ms | 619 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 7.17 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.
Field data Chrome UX Report, url-level
Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 3.59 s | needs-improvement | 48.2% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 386 ms | needs-improvement | 42.4% good |
| CLS CWV | 0.010 | good | 92.6% good |
| FCP | 3.30 s | poor | 32.6% good |
| TTFB | 2.60 s | poor | 15.9% good |
Lab vs field
Lab LCP 7.17 s · field p75 3.59 s · real users are 0.5× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 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 | ↑ +1.0 kB | 3.07 MB | 3.07 MB | |
| Requests | 57 | 57 | → no change | 57 | 57 | |
| Third-party Weight | 120 kB | 120 kB | → no change | 120 kB | 120 kB | |
| Third-party CPU | 2 ms | 6 ms | ↓ -4 ms (-66.1%) | 2 ms | 6 ms | |
| Unused JS | 354 kB | 354 kB | ↓ -152 B | 354 kB | 354 kB | |
| Unused CSS | 0 B | 0 B | → no change | 0 B | 0 B |
By resource type
Third parties 3 entities
120 kB transferred, 2 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 4.96 s | 4.36 s | ↑ +601 ms (+13.8%) | 4.36 s | 4.96 s | |
| Long Tasks | 11 | 10 | ↑ +1 (+10%) | 10 | 13 | |
| DOM Elements | 1,038 | 1,038 | → no change | 1,037 | 1,038 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 23 | 23 | → no change | 23 | 23 | |
| A11y Failures | 4 | 4 | → no change | 4 | 4 | |
| A11y Failing Nodes | 8 | 8 | → no change | 8 | 9 |
Main thread work
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. 5 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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 23, 2026, 10:22 AM UTC | 51 | 7.17 s | 0 | 570 ms | 3.07 MB | 3/3 | ±5 | 2,271 | 68.4s |
| Aug 22, 2026, 10:21 AM UTC | 51 | 7.37 s | 0 | 565 ms | 3.07 MB | 3/3 | ±4 | 2,442 | 64.3s |
| 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 speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://tanstack.com/"></speedlify2-score>