nextjs.org

Data from Aug 23, 2026, 5:28 AM UTC 17h old

Site Generators #6 · 3 measurements · since Aug 21, 2026

The measuring machine was slower than usual.

Lighthouse benchmark index was 2175 against a baseline of 3474.3 (-37.4%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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.

Built with Next.js

Hosted by Vercel

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.

LCP 1.47 s good

INP 125 ms good

CLS 0 good

Scores

Performance

↓ -3 (-3.2%)

100

Accessibility

no change

Best Practices

no change

100

SEO

no change

Filmstrip Lighthouse, mobile

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

375 ms
750 ms
1.13 s
1.50 s
1.88 s
2.25 s
2.63 s
3.00 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	2.65 s	2.13 s	↑ +513 ms (+24.1%) significant	1.97 s	2.65 s
CLS Cumulative Layout Shift	0	0	→ no change	0	0
TBT Total Blocking Time	261 ms	223 ms	↑ +38 ms (+17%)	106 ms	261 ms
FCP First Contentful Paint	1.52 s	1.53 s	↓ -12 ms (-0.8%)	1.52 s	1.53 s
Speed Index	1.59 s	1.86 s	↓ -266 ms (-14.3%)	1.52 s	1.86 s
TTFB Time to First Byte	620 ms	632 ms	↓ -12 ms (-1.9%)	620 ms	632 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

2.65 s

2.13 s

↑ +513 ms (+24.1%) significant

1.97 s

2.65 s

CLS Cumulative Layout Shift

→ no change

TBT Total Blocking Time

261 ms

223 ms

↑ +38 ms (+17%)

106 ms

261 ms

FCP First Contentful Paint

1.52 s

1.53 s

↓ -12 ms (-0.8%)

1.52 s

1.53 s

Speed Index

1.59 s

1.86 s

↓ -266 ms (-14.3%)

1.52 s

1.86 s

TTFB Time to First Byte

620 ms

632 ms

↓ -12 ms (-1.9%)

620 ms

632 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 2.65 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 200 ms

time to first byte 8 ms

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	1.47 s	good	88.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	125 ms	good	85.9% good
CLS CWV	0	good	98.2% good
FCP	1.40 s	good	84.2% good
TTFB	619 ms	good	82.7% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.47 s

good

88.5% good

INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run

125 ms

good

85.9% good

CLS CWV

good

98.2% good

FCP

1.40 s

good

84.2% good

TTFB

619 ms

good

82.7% good

Lab vs field

Lab LCP 2.65 s · field p75 1.47 s · real users are 0.55× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	FCP	TTFB
2026-08-15	1.47 s	123 ms	1.39 s	615 ms
2026-08-08	1.45 s	120 ms	1.37 s	608 ms
2026-08-01	1.45 s	121 ms	1.37 s	595 ms
2026-07-25	1.44 s	120 ms	1.38 s	595 ms
2026-07-18	1.45 s	121 ms	1.40 s	607 ms
2026-07-11	1.50 s	120 ms	1.45 s	617 ms
2026-07-04	1.55 s	115 ms	1.52 s	625 ms
2026-06-27	1.58 s	118 ms	1.56 s	627 ms
2026-06-20	1.68 s	118 ms	1.65 s	636 ms
2026-06-13	1.65 s	119 ms	1.63 s	618 ms
2026-06-06	1.63 s	124 ms	1.60 s	614 ms
2026-05-30	1.62 s	121 ms	1.59 s	622 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.47 s

123 ms

1.39 s

615 ms

2026-08-08

1.45 s

120 ms

1.37 s

608 ms

2026-08-01

1.45 s

121 ms

1.37 s

595 ms

2026-07-25

1.44 s

120 ms

1.38 s

595 ms

2026-07-18

1.45 s

121 ms

1.40 s

607 ms

2026-07-11

1.50 s

120 ms

1.45 s

617 ms

2026-07-04

1.55 s

115 ms

1.52 s

625 ms

2026-06-27

1.58 s

118 ms

1.56 s

627 ms

2026-06-20

1.68 s

118 ms

1.65 s

636 ms

2026-06-13

1.65 s

119 ms

1.63 s

618 ms

2026-06-06

1.63 s

124 ms

1.60 s

614 ms

2026-05-30

1.62 s

121 ms

1.59 s

622 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	1.05 MB	1.05 MB	↑ +6.0 kB (+0.6%)	854 kB	1.05 MB
Requests	82	82	→ no change	71	82
Third-party Weight	7.6 kB	7.6 kB	↓ -1 B	7.6 kB	7.6 kB
Third-party CPU	5 ms	5 ms	↑ +0 ms (+6.2%)	3 ms	5 ms
Unused JS	90.7 kB	90.7 kB	→ no change	90.6 kB	90.7 kB
Unused CSS	13.0 kB	13.0 kB	→ no change	13.0 kB	13.0 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

1.05 MB

↑ +6.0 kB (+0.6%)

854 kB

1.05 MB

Requests

→ no change

Third-party Weight

7.6 kB

↓ -1 B

7.6 kB

Third-party CPU

5 ms

↑ +0 ms (+6.2%)

3 ms

5 ms

Unused JS

90.7 kB

→ no change

90.6 kB

90.7 kB

Unused CSS

13.0 kB

→ no change

13.0 kB

By resource type

script 534 kB · 35 req

image 242 kB · 21 req

font 95.0 kB · 2 req

stylesheet 91.7 kB · 3 req

other 53.8 kB · 14 req

document 37.0 kB · 1 req

third party 7.6 kB · 2 req

Third parties 1 entities

7.6 kB transferred, 5 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 · 5 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	3.90 s	3.58 s	↑ +327 ms (+9.2%)	2.29 s	3.90 s
Long Tasks	7	6	↑ +1 (+16.7%)	5	7
DOM Elements	2,213	2,213	→ no change	2,213	2,213
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	3	3	→ no change	3	3
A11y Failures	1	1	→ no change	1	2
A11y Failing Nodes	5	5	→ no change	5	8

Main thread work

script evaluation 1.56 s

other 1.27 s

style layout 486 ms

paint composite render 247 ms

script parse compile 233 ms

parse HTML 88 ms

garbage collection 18 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 1 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

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	Perf	LCP	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 5:28 AM UTC	91	2.65 s	261 ms	1.05 MB	3/3	±27	2,175	51.4s
Aug 22, 2026, 5:26 AM UTC	94	2.13 s	223 ms	1.05 MB	3/3	±26	2,857	51.4s
Aug 21, 2026, 4:43 AM UTC	98	1.97 s	106 ms	854 kB	3/3	±11	4,092	41.9s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 5:28 AM UTC

2.65 s

261 ms

1.05 MB

3/3

±27

2,175

51.4s

Aug 22, 2026, 5:26 AM UTC

2.13 s

223 ms

1.05 MB

3/3

±26

2,857

51.4s

Aug 21, 2026, 4:43 AM UTC

1.97 s

106 ms

854 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 speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://nextjs.org/"></speedlify2-score>