speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

vite.dev

https://vite.dev/

65 96 100 100 ✗AXE ✓CWV

Data from Aug 27, 2026, 7:00 PM UTC old

Overall #1,263 Developer Tooling #42 · 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.

VitePress 2.0.0 Built with VitePress 2.0.0
Netlify 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 2.03 s good
INP 193 ms good
CLS 0 good

Scores

65
Performance
no change
96
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 7.71 s.

  1. 963 ms
  2. 1.93 s
  3. 2.89 s
  4. 3.85 s
  5. 4.82 s
  6. 5.78 s
  7. 6.74 s
  8. 7.71 s

Without JavaScript

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

Scripts disabled
As rendered

1.1% of pixels differ — they are nearly identical. 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 Trend
LCP Largest Contentful Paint 5.63 s — — 5.63 s 5.63 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 435 ms — — 435 ms 435 ms
FCP First Contentful Paint 2.40 s — — 2.40 s 2.40 s
Speed Index 2.40 s — — 2.40 s 2.40 s
TTFB Time to First Byte 605 ms — — 605 ms 605 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.63 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 121 ms
time to first byte 6 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 2.03 s good 86.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 193 ms good 76.1% good
CLS CWV 0 good 98% good
FCP 1.48 s good 81.7% good
TTFB 787 ms good 75.3% good

Lab vs field LCP

Lab 5.63 s
Field p75 2.03 s

The lab LCP is 2.77× 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 LCPINPCLSFCPTTFB
2026-08-22 2.03 s 189 ms 0 1.49 s 792 ms
2026-08-15 2.03 s 185 ms 0 1.48 s 792 ms
2026-08-08 2.00 s 184 ms 0 1.43 s 766 ms
2026-08-01 2.04 s 179 ms 0 1.44 s 780 ms
2026-07-25 2.05 s 183 ms 0 1.43 s 788 ms
2026-07-18 2.05 s 187 ms 0 1.43 s 788 ms
2026-07-11 2.05 s 194 ms 0 1.47 s 799 ms
2026-07-04 2.03 s 195 ms 0 1.44 s 777 ms
2026-06-27 1.89 s 189 ms 0 1.35 s 737 ms
2026-06-20 1.91 s 194 ms 0 1.38 s 751 ms
2026-06-13 1.89 s 192 ms 0 1.36 s 746 ms
2026-06-06 1.91 s 195 ms 0 1.37 s 781 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.43 MB — — 2.43 MB 2.43 MB
Requests 88 — — 88 88
Third-party Weight 92.7 kB — — 92.7 kB 92.7 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 25.0 kB — — 25.0 kB 25.0 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.47 MB · 40 req
other 624 kB · 9 req
font 147 kB · 3 req
script 134 kB · 7 req
stylesheet 43.9 kB · 2 req
document 10.3 kB · 1 req
third party 92.7 kB · 5 req

Third parties 3 entities

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

GitHub 46.5 kB · 0 ms CPU
opencollective.com 43.6 kB · 0 ms CPU
iconify.design 2.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 12.81 s — — 12.81 s 12.81 s
Long Tasks 11 — — 11 11
DOM Elements 650 — — 650 650
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 45 — — 45 45
A11y Failures 2 — — 2 2
A11y Failing Nodes 4 — — 4 4

Main thread work

script evaluation 6.66 s
other 4.41 s
paint composite render 949 ms
style layout 610 ms
parse HTML 97 ms
garbage collection 51 ms
script parse compile 30 ms

Axe violations axe-core 4.13.0, full rule set

45 violating nodes across 3 rules, 669 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 41 nodes
  • moderate heading-order — Heading levels should only increase by one 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 20 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.

  • heading-order — Heading elements are not in a sequentially-descending order 3 nodes
  • 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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 27, 2026, 7:00 PM UTC 65 5.63 s 0.001 435 ms 2.43 MB 2/3 ±5 2,961 113.1s

Embed this score

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