speedlify2

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

Measurement runs · Embed a score ·

zacharyparsons.co.uk

https://zacharyparsons.co.uk/

99 100 100 100 0AXE –CWV

Data from Aug 21, 2026, 8:32 PM UTC 2d old

Built Awesome #175 · 1 measurement · since Aug 21, 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.

Netlify Hosted by Netlify

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.08 s — — 2.08 s 2.08 s
CLS Cumulative Layout Shift 0.017 — — 0.017 0.017
TBT Total Blocking Time 33 ms — — 33 ms 33 ms
FCP First Contentful Paint 966 ms — — 966 ms 966 ms
Speed Index 966 ms — — 966 ms 966 ms
TTFB Time to First Byte 765 ms — — 765 ms 765 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.08 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.

time to first byte 144 ms
element render delay 44 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 98.1 kB — — 98.1 kB 98.1 kB
Requests 9 — — 9 9
Third-party Weight 60.0 kB — — 60.0 kB 60.0 kB
Third-party CPU 30 ms — — 30 ms 30 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

script 60.5 kB · 3 req
font 25.7 kB · 1 req
other 6.6 kB · 4 req
document 5.3 kB · 1 req
third party 60.0 kB · 3 req

Third parties 3 entities

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

Netlify 55.2 kB · 28 ms CPU
zgo.at 4.3 kB · 2 ms CPU
goatcounter.com 380 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 104 ms
other 95 ms
style layout 81 ms
script parse compile 31 ms
parse HTML 13 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 162 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.

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 21, 2026, 8:32 PM UTC 99 2.08 s 0.017 33 ms 98.1 kB 3/3 ±1 2,485 21.2s

Embed this score

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