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 ·

nextjs.org

https://nextjs.org/

98 96 96 100 ✓CWV 3AXE

Data from Aug 21, 2026, 4:43 AM UTC — 14h old.

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

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.

Next.js Built with Next.js
Vercel Hosted by Vercel

Core Web Vitals field data, url-level

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

LCP 1.47 s good
INP 123 ms good
CLS 0 good

Scores

98
Performance
no change
96
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.97 s — — 1.97 s 1.97 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 106 ms — — 106 ms 106 ms
FCP First Contentful Paint 1.52 s — — 1.52 s 1.52 s
Speed Index 1.52 s — — 1.52 s 1.52 s
TTFB Time to First Byte 624 ms — — 624 ms 624 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 127 ms
time to first byte 15 ms

Field data Chrome UX Report, url-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.47 s good 88.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 123 ms good 86.1% good
CLS CWV 0 good 98.2% good
FCP 1.39 s good 84.3% good
TTFB 617 ms good 82.4% good

Lab vs field

Lab LCP 1.97 s · field p75 1.47 s · real users are 0.74× 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.47 s 123 ms 0 1.39 s 615 ms
2026-08-08 1.45 s 120 ms 0 1.37 s 608 ms
2026-08-01 1.45 s 121 ms 0 1.37 s 595 ms
2026-07-25 1.44 s 120 ms 0 1.38 s 595 ms
2026-07-18 1.45 s 121 ms 0 1.40 s 607 ms
2026-07-11 1.50 s 120 ms 0 1.45 s 617 ms
2026-07-04 1.55 s 115 ms 0 1.52 s 625 ms
2026-06-27 1.58 s 118 ms 0 1.56 s 627 ms
2026-06-20 1.68 s 118 ms 0 1.65 s 636 ms
2026-06-13 1.65 s 119 ms 0 1.63 s 618 ms
2026-06-06 1.63 s 124 ms 0 1.60 s 614 ms
2026-05-30 1.62 s 121 ms 0 1.59 s 622 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 853.6 kB — — 853.6 kB 853.6 kB
Requests 71 — — 71 71
Third-party Weight 7.6 kB — — 7.6 kB 7.6 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 90.6 kB — — 90.6 kB 90.6 kB
Unused CSS 13.0 kB — — 13.0 kB 13.0 kB

By resource type

script 533.7 kB · 35 req
font 95.0 kB · 2 req
stylesheet 91.7 kB · 3 req
image 49.0 kB · 16 req
other 47.1 kB · 14 req
document 37.0 kB · 1 req
third party 7.6 kB · 2 req

Third parties 1 entities

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

cr-relay.com 7.6 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 947 ms
other 659 ms
style layout 278 ms
script parse compile 190 ms
paint composite render 173 ms
parse HTML 45 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 1120 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 landmark-main-is-top-level — Main landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 25 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 5 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 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 1 console error

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, 4:43 AM UTC 98 1.97 s 0 106 ms 853.6 kB 3/3 ±11 4,092 41.9s

Embed this score

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