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 ·

danielshaw.co.nz

https://danielshaw.co.nz/

100 65 92 82 –CWV 5AXE

Data from Aug 20, 2026, 7:33 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.

Self-hosted · Apache Hosted by Self-hosted

Scores

100
Performance
no change
65
Accessibility
no change
92
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

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

time to first byte 188 ms
element render delay 35 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 683 B — — 683 B 683 B
Requests 3 — — 3 3
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

document 408 B · 1 req

Page health

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

Main thread work

other 51 ms
script evaluation 8 ms
style layout 4 ms
paint composite render 1 ms
parse HTML 1 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 5 rules, 5 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 document-title — Documents must have <title> element to aid in navigation 1 node
  • serious html-has-lang — <html> element must have a lang attribute 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 of 8 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.

  • document-title — Document doesn't have a `<title>` element 1 node
  • html-has-lang — `<html>` element does not have a `[lang]` attribute 1 node
  • 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 http/1.1

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 20, 2026, 7:33 PM UTC 100 944 ms 0 0 ms 683 B 3/3 ±4 2,498 26.1s

Embed this score

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