vuejs.org

Data from Aug 27, 2026, 6:59 PM UTC 10h old

Overall #1,457 Developer Tooling #68 Frameworks and Libraries #13 · 1 measurement · since Aug 27, 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-29 → 2026-08-25). This is what Google measures you on.

LCP 1.82 s good

INP 187 ms good

CLS 0.180 needs-improvement

Scores

Performance

no change

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

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

34.4% of pixels differ — parts of the page change. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	2.75 s	—	—	2.75 s	2.75 s
CLS Cumulative Layout Shift	0.176	—	—	0.176	0.176
TBT Total Blocking Time	33 ms	—	—	33 ms	33 ms
FCP First Contentful Paint	1.89 s	—	—	1.89 s	1.89 s
Speed Index	1.89 s	—	—	1.89 s	1.89 s
TTFB Time to First Byte	650 ms	—	—	650 ms	650 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.75 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 158 ms

time to first byte 28 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	1.82 s	good	85.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	187 ms	good	78.1% good
CLS CWV	0.180	needs-improvement	42.3% good
FCP	1.77 s	good	75.9% good
TTFB	674 ms	good	78.8% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.82 s

good

85.3% good

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

187 ms

good

78.1% good

CLS CWV

0.180

needs-improvement

42.3% good

FCP

1.77 s

good

75.9% good

TTFB

674 ms

good

78.8% good

Lab vs field LCP

Lab 2.75 s

Field p75 1.82 s

The lab LCP is 1.51× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

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

Week ending	LCP	INP	CLS	FCP	TTFB
2026-08-22	1.78 s	186 ms	0.180	1.74 s	655 ms
2026-08-15	1.79 s	184 ms	0.180	1.74 s	661 ms
2026-08-08	1.79 s	181 ms	0.180	1.76 s	672 ms
2026-08-01	1.87 s	184 ms	0.130	1.85 s	716 ms
2026-07-25	1.89 s	186 ms	0.100	1.89 s	726 ms
2026-07-18	1.90 s	184 ms	0.100	1.88 s	712 ms
2026-07-11	1.88 s	181 ms	0	1.85 s	690 ms
2026-07-04	1.84 s	180 ms	0	1.82 s	676 ms
2026-06-27	1.80 s	176 ms	0	1.78 s	664 ms
2026-06-20	1.86 s	178 ms	0	1.83 s	684 ms
2026-06-13	1.85 s	180 ms	0	1.83 s	672 ms
2026-06-06	1.88 s	175 ms	0	1.86 s	707 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-22

1.78 s

186 ms

0.180

1.74 s

655 ms

2026-08-15

1.79 s

184 ms

0.180

1.74 s

661 ms

2026-08-08

1.79 s

181 ms

0.180

1.76 s

672 ms

2026-08-01

1.87 s

184 ms

0.130

1.85 s

716 ms

2026-07-25

1.89 s

186 ms

0.100

1.89 s

726 ms

2026-07-18

1.90 s

184 ms

0.100

1.88 s

712 ms

2026-07-11

1.88 s

181 ms

1.85 s

690 ms

2026-07-04

1.84 s

180 ms

1.82 s

676 ms

2026-06-27

1.80 s

176 ms

1.78 s

664 ms

2026-06-20

1.86 s

178 ms

1.83 s

684 ms

2026-06-13

1.85 s

180 ms

1.83 s

672 ms

2026-06-06

1.88 s

175 ms

1.86 s

707 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	308 kB	—	—	308 kB	308 kB
Requests	32	—	—	32	32
Third-party Weight	12.0 kB	—	—	12.0 kB	12.0 kB
Third-party CPU	8 ms	—	—	8 ms	8 ms
Unused JS	0 B	—	—	0 B	0 B
Unused CSS	34.9 kB	—	—	34.9 kB	34.9 kB

By resource type

font 120 kB · 2 req

script 103 kB · 14 req

stylesheet 40.5 kB · 4 req

document 21.5 kB · 2 req

other 20.3 kB · 8 req

image 2.6 kB · 2 req

third party 100 kB · 12 req

Third parties 3 entities

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

bitterbrains.com 8.0 kB · 7 ms CPU

Fathom Analytics 3.2 kB · 1 ms CPU

Google Fonts 822 B · 0 ms CPU

Page health

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

Main thread work

other 214 ms

script evaluation 211 ms

style layout 118 ms

garbage collection 33 ms

parse HTML 29 ms

paint composite render 18 ms

script parse compile 9 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 5 rules, 519 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.

serious color-contrast — Elements must meet minimum color contrast ratio thresholds 10 nodes
moderate region — All page content should be contained by landmarks 4 nodes
serious frame-title — Frames must have an accessible name 1 node
moderate heading-order — Heading levels should only increase by one 1 node
serious link-in-text-block — Links must be distinguishable without relying on color 1 node

Accessibility failures 4 of 27 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. 10 nodes
frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node
heading-order — Heading elements are not in a sequentially-descending order 1 node
link-in-text-block — Links rely on color to be distinguishable. 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 27, 2026, 6:59 PM UTC	87	2.75 s	0.176	33 ms	308 kB	3/3	±15	2,311	27.6s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 27, 2026, 6:59 PM UTC

2.75 s

0.176

33 ms

308 kB

3/3

±15

2,311

27.6s

Embed this score

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