vitepress.dev

Data from Aug 23, 2026, 9:26 AM UTC 13h old

Site Generators #5 · 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 VitePress 2.0.0

Hosted by Netlify

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 170 ms good

CLS 0 good

Scores

Performance

↓ -1 (-1%)

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	2.41 s	2.33 s	↑ +75 ms (+3.2%)	2.33 s	2.41 s
CLS Cumulative Layout Shift	0	0	→ no change	0	0
TBT Total Blocking Time	31 ms	29 ms	↑ +2 ms (+6.9%)	17 ms	31 ms
FCP First Contentful Paint	1.38 s	1.36 s	↑ +23 ms (+1.7%)	1.36 s	1.38 s
Speed Index	1.38 s	1.36 s	↑ +23 ms (+1.7%)	1.36 s	1.38 s
TTFB Time to First Byte	633 ms	610 ms	↑ +23 ms (+3.8%)	610 ms	633 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

2.41 s

2.33 s

↑ +75 ms (+3.2%)

2.33 s

2.41 s

CLS Cumulative Layout Shift

→ no change

TBT Total Blocking Time

31 ms

29 ms

↑ +2 ms (+6.9%)

17 ms

31 ms

FCP First Contentful Paint

1.38 s

1.36 s

↑ +23 ms (+1.7%)

1.36 s

1.38 s

Speed Index

1.38 s

1.36 s

↑ +23 ms (+1.7%)

1.36 s

1.38 s

TTFB Time to First Byte

633 ms

610 ms

↑ +23 ms (+3.8%)

610 ms

633 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.41 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.

resource load duration 139 ms

element render delay 53 ms

time to first byte 41 ms

resource load delay 12 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	93.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	170 ms	good	81.3% good
CLS CWV	0	good	98.9% good
FCP	1.43 s	good	84.4% good
TTFB	565 ms	good	85.1% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.47 s

good

93.9% good

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

170 ms

good

81.3% good

CLS CWV

good

98.9% good

FCP

1.43 s

good

84.4% good

TTFB

565 ms

good

85.1% good

Lab vs field

Lab LCP 2.41 s · field p75 1.47 s · real users are 0.61× 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.43 s	183 ms	1.37 s	521 ms
2026-08-08	1.44 s	170 ms	1.34 s	503 ms
2026-08-01	1.44 s	167 ms	1.35 s	491 ms
2026-07-25	1.47 s	167 ms	1.38 s	491 ms
2026-07-18	1.44 s	166 ms	1.34 s	511 ms
2026-07-11	1.44 s	164 ms	1.31 s	515 ms
2026-07-04	1.49 s	153 ms	1.30 s	524 ms
2026-06-27	1.42 s	147 ms	1.25 s	512 ms
2026-06-20	1.44 s	159 ms	1.27 s	521 ms
2026-06-13	1.44 s	164 ms	1.31 s	546 ms
2026-06-06	1.30 s	159 ms	1.24 s	525 ms
2026-05-30	1.45 s	154 ms	1.32 s	565 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.43 s

183 ms

1.37 s

521 ms

2026-08-08

1.44 s

170 ms

1.34 s

503 ms

2026-08-01

1.44 s

167 ms

1.35 s

491 ms

2026-07-25

1.47 s

167 ms

1.38 s

491 ms

2026-07-18

1.44 s

166 ms

1.34 s

511 ms

2026-07-11

1.44 s

164 ms

1.31 s

515 ms

2026-07-04

1.49 s

153 ms

1.30 s

524 ms

2026-06-27

1.42 s

147 ms

1.25 s

512 ms

2026-06-20

1.44 s

159 ms

1.27 s

521 ms

2026-06-13

1.44 s

164 ms

1.31 s

546 ms

2026-06-06

1.30 s

159 ms

1.24 s

525 ms

2026-05-30

1.45 s

154 ms

1.32 s

565 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	210 kB	210 kB	↑ +550 B (+0.3%)	210 kB	210 kB
Requests	23	23	→ no change	23	23
Third-party Weight	3.2 kB	3.2 kB	↓ -4 B (-0.1%)	3.2 kB	3.2 kB
Third-party CPU	2 ms	2 ms	↑ +1 ms (+43.7%)	1 ms	2 ms
Unused JS	0 B	0 B	→ no change	0 B	0 B
Unused CSS	20.8 kB	20.6 kB	↑ +129 B (+0.6%)	20.6 kB	20.8 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

210 kB

↑ +550 B (+0.3%)

210 kB

Requests

→ no change

Third-party Weight

3.2 kB

↓ -4 B (-0.1%)

3.2 kB

Third-party CPU

2 ms

↑ +1 ms (+43.7%)

1 ms

2 ms

Unused JS

0 B

→ no change

0 B

Unused CSS

20.8 kB

20.6 kB

↑ +129 B (+0.6%)

20.6 kB

20.8 kB

By resource type

script 80.7 kB · 6 req

font 73.2 kB · 1 req

stylesheet 39.5 kB · 2 req

other 10.1 kB · 4 req

document 3.5 kB · 1 req

image 3.4 kB · 3 req

third party 3.2 kB · 2 req

Third parties 1 entities

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

Fathom Analytics 3.2 kB · 2 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	606 ms	605 ms	↑ +1 ms (+0.1%)	521 ms	606 ms
Long Tasks	2	2	→ no change	1	2
DOM Elements	204	204	→ no change	204	204
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	4	4	→ no change	4	4
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	2	2	→ no change	2	2

Main thread work

script evaluation 213 ms

other 186 ms

style layout 108 ms

parse HTML 80 ms

paint composite render 15 ms

script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 3 rules, 207 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 2 nodes
serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 22 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. 1 node
landmark-one-main — Document does not have a main landmark. 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	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 9:26 AM UTC	97	2.41 s	31 ms	210 kB	3/3	±7	2,440	27.9s
Aug 22, 2026, 9:25 AM UTC	98	2.33 s	29 ms	210 kB	3/3	±5	2,330	26.7s
Aug 21, 2026, 8:45 AM UTC	98	2.35 s	17 ms	210 kB	3/3	±2	2,861	23.1s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 9:26 AM UTC

2.41 s

31 ms

210 kB

3/3

±7

2,440

27.9s

Aug 22, 2026, 9:25 AM UTC

2.33 s

29 ms

210 kB

3/3

±5

2,330

26.7s

Aug 21, 2026, 8:45 AM UTC

2.35 s

17 ms

210 kB

3/3

±2

2,861

23.1s

Embed this score

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