speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

vess.co.nz

https://www.vess.co.nz/

99 98 96 100 –CWV 10AXE

Data from Aug 21, 2026, 2:43 PM UTC — 4h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 4h

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.

Eleventy 1.0.1 Built with Eleventy 1.0.1
Netlify Hosted by Netlify

Scores

99
Performance
no change
98
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

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

element render delay 79 ms
time to first byte 41 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 300.8 kB — — 300.8 kB 300.8 kB
Requests 13 — — 13 13
Third-party Weight 42.3 kB — — 42.3 kB 42.3 kB
Third-party CPU 4 ms — — 4 ms 4 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 26.1 kB — — 26.1 kB 26.1 kB

By resource type

image 210.4 kB · 3 req
script 43.2 kB · 5 req
document 29.3 kB · 1 req
other 12.1 kB · 2 req
stylesheet 2.5 kB · 1 req
third party 42.3 kB · 4 req

Third parties 2 entities

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

JSDelivr CDN 42.2 kB · 4 ms CPU
FontAwesome CDN 80 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 323 ms — — 323 ms 323 ms
Long Tasks 0 — — 0 0
DOM Elements 104 — — 104 104
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 10 — — 10 10
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 154 ms
style layout 84 ms
parse HTML 42 ms
script evaluation 26 ms
script parse compile 10 ms
paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 2 rules, 172 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 9 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 23 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.

  • 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 1 console error

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 21, 2026, 2:43 PM UTC 99 1.86 s 0 0 ms 300.8 kB 3/3 ±1 2,389 22.7s

Embed this score

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