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

vitest.dev

https://vitest.dev/

80 96 100 92 ✗AXE ✓CWV

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

Overall #1,235 Developer Tooling #38 Test Runners #7 · 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 1.64 s good
INP 123 ms good
CLS 0 good

Scores

80
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Without JavaScript

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

Scripts disabled
As rendered

0.7% 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 4.75 s — — 4.75 s 4.75 s
CLS Cumulative Layout Shift 0.021 — — 0.021 0.021
TBT Total Blocking Time 69 ms — — 69 ms 69 ms
FCP First Contentful Paint 2.28 s — — 2.28 s 2.28 s
Speed Index 2.28 s — — 2.28 s 2.28 s
TTFB Time to First Byte 626 ms — — 626 ms 626 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 4.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.

resource load delay 78 ms
element render delay 64 ms
resource load duration 40 ms
time to first byte 27 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.64 s good 87.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 123 ms good 87.4% good
CLS CWV 0 good 98.3% good
FCP 1.25 s good 86.9% good
TTFB 563 ms good 87.3% good

Lab vs field LCP

Lab 4.75 s
Field p75 1.64 s

The lab LCP is 2.9× 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 1.66 s 128 ms 0 1.26 s 565 ms
2026-08-15 1.84 s 140 ms 0 1.36 s 628 ms
2026-08-08 1.91 s 144 ms 0 1.37 s 686 ms
2026-08-01 1.95 s 140 ms 0 1.40 s 705 ms
2026-07-25 2.07 s 132 ms 0 1.46 s 741 ms
2026-07-18 2.09 s 128 ms 0 1.48 s 727 ms
2026-07-11 2.09 s 136 ms 0 1.48 s 704 ms
2026-07-04 2.08 s 136 ms 0 1.43 s 729 ms
2026-06-27 2.03 s 137 ms 0 1.28 s 670 ms
2026-06-20 2.03 s 144 ms 0 1.27 s 670 ms
2026-06-13 1.98 s 145 ms 0 1.25 s 672 ms
2026-06-06 2.03 s 145 ms 0 1.26 s 603 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.47 MB — — 1.47 MB 1.47 MB
Requests 58 — — 58 58
Third-party Weight 6.8 kB — — 6.8 kB 6.8 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 46.5 kB — — 46.5 kB 46.5 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 770 kB · 23 req
other 310 kB · 11 req
font 188 kB · 4 req
script 137 kB · 7 req
stylesheet 48.5 kB · 3 req
document 12.9 kB · 1 req
third party 6.8 kB · 6 req

Third parties 3 entities

6.8 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
iconify.design 2.7 kB · 0 ms CPU
Google Fonts 901 B · 0 ms CPU

Page health

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

Main thread work

other 747 ms
script evaluation 541 ms
style layout 237 ms
paint composite render 147 ms
parse HTML 33 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

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

Accessibility failures 2 of 21 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 2 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, 6:59 PM UTC 80 4.75 s 0.021 69 ms 1.47 MB 3/3 ±31 2,366 31.7s

Embed this score

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