vitepress.dev

Data from Aug 21, 2026, 8:45 AM UTC — 10h old.

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

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-23 → 2026-08-19). This is what Google measures you on.

LCP 1.47 s good

INP 176 ms good

CLS 0 good

Scores

Performance

no change

Accessibility

no change

100

Best Practices

no change

100

SEO

no change

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	2.35 s	—	—	2.35 s	2.35 s
CLS Cumulative Layout Shift	0	—	—	0	0
TBT Total Blocking Time	17 ms	—	—	17 ms	17 ms
FCP First Contentful Paint	1.38 s	—	—	1.38 s	1.38 s
Speed Index	1.38 s	—	—	1.38 s	1.38 s
TTFB Time to First Byte	629 ms	—	—	629 ms	629 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.

resource load duration 102 ms

element render delay 35 ms

time to first byte 24 ms

resource load delay 11 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	1.47 s	good	94% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	176 ms	good	81.3% good
CLS CWV	0	good	98.9% good
FCP	1.43 s	good	85.1% good
TTFB	548 ms	good	86.7% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.47 s

good

94% good

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

176 ms

good

81.3% good

CLS CWV

good

98.9% good

FCP

1.43 s

good

85.1% good

TTFB

548 ms

good

86.7% good

Lab vs field

Lab LCP 2.35 s · field p75 1.47 s · real users are 0.62× 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.3 kB	—	—	210.3 kB	210.3 kB
Requests	23	—	—	23	23
Third-party Weight	3.2 kB	—	—	3.2 kB	3.2 kB
Third-party CPU	1 ms	—	—	1 ms	1 ms
Unused JS	0 B	—	—	0 B	0 B
Unused CSS	20.6 kB	—	—	20.6 kB	20.6 kB

By resource type

script 81.0 kB · 6 req

font 73.2 kB · 1 req

stylesheet 39.2 kB · 2 req

other 9.9 kB · 4 req

document 3.6 kB · 1 req

image 3.5 kB · 3 req

third party 3.2 kB · 2 req

Third parties 1 entities

3.2 kB transferred, 1 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 · 1 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	521 ms	—	—	521 ms	521 ms
Long Tasks	1	—	—	1	1
DOM Elements	204	—	—	204	204
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	4	—	—	4	4
A11y Failures	2	—	—	2	2
A11y Failing Nodes	2	—	—	2	2

Main thread work

other 164 ms

script evaluation 163 ms

style layout 102 ms

parse HTML 76 ms

paint composite render 13 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	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 21, 2026, 8:45 AM UTC	98	2.35 s	0	17 ms	210.3 kB	3/3	±2	2,861	23.1s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 21, 2026, 8:45 AM UTC

2.35 s

17 ms

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

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://vitepress.dev/"></speedlify-score>