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

vlt.io

https://www.vlt.io/

34 80 92 83 ✗AXE ✗CWV

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

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

Next.js Built with Next.js
Vercel Hosted by Vercel

Core Web Vitals field data, origin-level

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

LCP 3.26 s needs-improvement
INP 211 ms needs-improvement
CLS 0.080 good

Scores

34
Performance
no change
80
Accessibility
no change
92
Best Practices
no change
83
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 861 ms
  2. 1.72 s
  3. 2.58 s
  4. 3.44 s
  5. 4.30 s
  6. 5.16 s
  7. 6.02 s
  8. 6.88 s

Without JavaScript

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

Scripts disabled
As rendered

96.7% of pixels differ — they have almost nothing in common. 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 12.57 s — — 12.57 s 12.57 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 4.16 s — — 4.16 s 4.16 s
FCP First Contentful Paint 2.29 s — — 2.29 s 2.29 s
Speed Index 9.60 s — — 9.60 s 9.60 s
TTFB Time to First Byte 663 ms — — 663 ms 663 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 12.57 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 1.26 s
resource load duration 1.02 s
element render delay 317 ms
time to first byte 163 ms

Field data Chrome UX Report, origin-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 3.26 s needs-improvement 62.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 211 ms needs-improvement 73.7% good
CLS CWV 0.080 good 80.4% good
FCP 2.56 s needs-improvement 52.7% good
TTFB 873 ms needs-improvement 69.8% good

Lab vs field LCP

Lab 12.57 s
Field p75 3.26 s

The lab LCP is 3.86× 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 3.26 s 211 ms 0.080 2.56 s 872 ms
2026-08-15 3.08 s 179 ms 0.080 2.57 s 858 ms
2026-08-08 2.83 s 141 ms 0.080 2.44 s 835 ms
2026-08-01 — — — — —
2026-07-25 3.80 s — 0.060 3.67 s 1.59 s
2026-07-18 3.34 s — 0.030 3.33 s 1.38 s
2026-07-11 3.33 s — 0.020 3.20 s 1.34 s
2026-07-04 3.33 s — 0.020 3.06 s 1.31 s
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 2.74 s — 0.020 2.55 s 1.07 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 12.89 MB — — 12.89 MB 12.89 MB
Requests 114 — — 114 114
Third-party Weight 8.53 MB — — 8.53 MB 8.53 MB
Third-party CPU 330 ms — — 330 ms 330 ms
Unused JS 711 kB — — 711 kB 711 kB
Unused CSS 12.1 kB — — 12.1 kB 12.1 kB

By resource type

media 8.18 MB · 1 req
script 2.72 MB · 58 req
image 1.57 MB · 14 req
font 173 kB · 5 req
stylesheet 119 kB · 5 req
document 98.3 kB · 3 req
other 28.2 kB · 24 req
third party 9.62 MB · 29 req

Third parties 4 entities

8.53 MB transferred, 330 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Amazon Web Services 8.18 MB · 0 ms CPU
Intercom 291 kB · 306 ms CPU
YouTube 61.6 kB · 24 ms CPU
Sentry 337 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 11.90 s — — 11.90 s 11.90 s
Long Tasks 20 — — 20 20
DOM Elements 1,664 — — 1,664 1,664
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 18 — — 18 18
A11y Failures 6 — — 6 6
A11y Failing Nodes 13 — — 13 13

Main thread work

script evaluation 7.46 s
other 1.90 s
style layout 1.30 s
script parse compile 835 ms
paint composite render 219 ms
parse HTML 104 ms
garbage collection 83 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 7 rules, 1542 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 link-name — Links must have discernible text 5 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 5 nodes
  • critical image-alt — Images must have alternative text 3 nodes
  • critical button-name — Buttons must have discernible text 2 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • serious aria-input-field-name — ARIA input fields must have an accessible name 1 node
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node

Accessibility failures 6 of 31 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.

  • link-name — Links do not have a discernible name 5 nodes
  • image-alt — Image elements do not have `[alt]` attributes 3 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 2 nodes
  • aria-input-field-name — ARIA input fields do not have accessible names 1 node
  • button-name — Buttons do not have an accessible name 1 node
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 34 12.57 s 0.003 4.16 s 12.89 MB 3/3 ±3 2,469 89.4s

Embed this score

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