nuxt.com

Data from Aug 23, 2026, 6:38 AM UTC 15h old

Site Generators #19 · 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.

Built with Nuxt

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 2.28 s good

INP 890 ms poor

CLS 0 good

Scores

Performance

↑ +8 (+24.2%)

Accessibility

no change

100

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	5.28 s	15.12 s	↓ -9839 ms (-65.1%)	5.24 s	15.12 s
CLS Cumulative Layout Shift	0.014	0.014	→ no change	0.014	0.014
TBT Total Blocking Time	2.69 s	3.93 s	↓ -1235 ms (-31.4%)	1.62 s	3.93 s
FCP First Contentful Paint	4.15 s	4.66 s	↓ -506 ms (-10.9%)	4.11 s	4.66 s
Speed Index	4.15 s	4.92 s	↓ -766 ms (-15.6%)	4.11 s	4.92 s
TTFB Time to First Byte	704 ms	642 ms	↑ +62 ms (+9.7%) significant	642 ms	704 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

5.28 s

15.12 s

↓ -9839 ms (-65.1%)

5.24 s

15.12 s

CLS Cumulative Layout Shift

0.014

→ no change

0.014

TBT Total Blocking Time

2.69 s

3.93 s

↓ -1235 ms (-31.4%)

1.62 s

3.93 s

FCP First Contentful Paint

4.15 s

4.66 s

↓ -506 ms (-10.9%)

4.11 s

4.66 s

Speed Index

4.15 s

4.92 s

↓ -766 ms (-15.6%)

4.11 s

4.92 s

TTFB Time to First Byte

704 ms

642 ms

↑ +62 ms (+9.7%) significant

642 ms

704 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 5.28 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 334 ms

time to first byte 22 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	2.28 s	good	79.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	890 ms	poor	42% good
CLS CWV	0	good	97.2% good
FCP	2.25 s	needs-improvement	60.2% good
TTFB	1.39 s	needs-improvement	47.8% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.28 s

good

79.6% good

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

890 ms

poor

42% good

CLS CWV

good

97.2% good

FCP

2.25 s

needs-improvement

60.2% good

TTFB

1.39 s

needs-improvement

47.8% good

Lab vs field

Lab LCP 5.28 s · field p75 2.28 s · real users are 0.43× 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	2.28 s	943 ms	2.25 s	1.38 s
2026-08-08	2.22 s	897 ms	2.19 s	1.36 s
2026-08-01	2.11 s	911 ms	2.09 s	1.28 s
2026-07-25	2.01 s	976 ms	2.00 s	1.21 s
2026-07-18	1.98 s	1.02 s	1.97 s	1.20 s
2026-07-11	1.98 s	1.01 s	1.97 s	1.21 s
2026-07-04	1.98 s	938 ms	1.97 s	1.21 s
2026-06-27	1.93 s	803 ms	1.92 s	1.15 s
2026-06-20	1.97 s	748 ms	1.96 s	1.13 s
2026-06-13	1.96 s	697 ms	1.96 s	1.11 s
2026-06-06	2.00 s	655 ms	2.00 s	1.12 s
2026-05-30	1.98 s	681 ms	1.98 s	1.12 s

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.28 s

943 ms

2.25 s

1.38 s

2026-08-08

2.22 s

897 ms

2.19 s

1.36 s

2026-08-01

2.11 s

911 ms

2.09 s

1.28 s

2026-07-25

2.01 s

976 ms

2.00 s

1.21 s

2026-07-18

1.98 s

1.02 s

1.97 s

1.20 s

2026-07-11

1.98 s

1.01 s

1.97 s

1.21 s

2026-07-04

1.98 s

938 ms

1.97 s

1.21 s

2026-06-27

1.93 s

803 ms

1.92 s

1.15 s

2026-06-20

1.97 s

748 ms

1.96 s

1.13 s

2026-06-13

1.96 s

697 ms

1.96 s

1.11 s

2026-06-06

2.00 s

655 ms

2.00 s

1.12 s

2026-05-30

1.98 s

681 ms

1.98 s

1.12 s

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	3.26 MB	3.26 MB	↑ +1.1 kB	3.26 MB	3.26 MB
Requests	318	318	→ no change	318	318
Third-party Weight	1.3 kB	1.3 kB	↓ -16 B (-1.2%)	1.3 kB	1.4 kB
Third-party CPU	0 ms	0 ms	→ no change	0 ms	0 ms
Unused JS	1.85 MB	1.85 MB	→ no change	1.85 MB	1.85 MB
Unused CSS	0 B	0 B	→ no change	0 B	0 B

Metric

Current

Change

Best

Worst

Trend

Page Weight

3.26 MB

↑ +1.1 kB

3.26 MB

Requests

318

→ no change

318

Third-party Weight

1.3 kB

↓ -16 B (-1.2%)

1.3 kB

1.4 kB

Third-party CPU

0 ms

→ no change

0 ms

Unused JS

1.85 MB

→ no change

1.85 MB

Unused CSS

0 B

→ no change

0 B

By resource type

other 2.38 MB · 48 req

script 665 kB · 183 req

image 110 kB · 43 req

document 43.0 kB · 1 req

stylesheet 38.8 kB · 4 req

font 26.9 kB · 1 req

third party 1.3 kB · 2 req

Third parties 2 entities

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

GitHub 974 B · 0 ms CPU

Carbon Ads 355 B · 0 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	9.55 s	11.82 s	↓ -2269 ms (-19.2%)	8.13 s	11.82 s
Long Tasks	20	20	→ no change	17	20
DOM Elements	1,722	1,722	→ no change	1,722	1,722
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	2	2	→ no change	2	2
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	2	2	→ no change	2	2

Main thread work

script evaluation 5.50 s

other 2.37 s

style layout 975 ms

garbage collection 362 ms

paint composite render 182 ms

parse HTML 114 ms

script parse compile 44 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 2557 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.

critical aria-valid-attr-value — ARIA attributes must conform to valid values 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 34 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.

aria-valid-attr-value — `[aria-*]` attributes do not have valid values 1 node
td-has-header — `<td>` elements in a large `<table>` do not have table headers. 1 node

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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 6:38 AM UTC	41	5.28 s	0.014	2.69 s	3.26 MB	3/3	±8	3,066	67.8s
Aug 22, 2026, 6:38 AM UTC	33	15.12 s	0.014	3.93 s	3.26 MB	3/3	±8	2,492	76.6s
Aug 21, 2026, 5:31 AM UTC	44	5.24 s	0.014	1.62 s	3.26 MB	3/3	±10	3,529	65.4s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 6:38 AM UTC

5.28 s

0.014

2.69 s

3.26 MB

3/3

±8

3,066

67.8s

Aug 22, 2026, 6:38 AM UTC

15.12 s

0.014

3.93 s

3.26 MB

3/3

±8

2,492

76.6s

Aug 21, 2026, 5:31 AM UTC

5.24 s

0.014

1.62 s

3.26 MB

3/3

±10

3,529

65.4s

Embed this score

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