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 ·

fifty.snook.ca

https://fifty.snook.ca/

95 97 100 100 –CWV 2AXE

Data from Aug 20, 2026, 10:31 PM UTC — 20h old.

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

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.

GitHub Pages Hosted by GitHub Pages

Scores

95
Performance
no change
97
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.41 s — — 2.41 s 2.41 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 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 603 ms — — 603 ms 603 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 65 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 123.8 kB — — 123.8 kB 123.8 kB
Requests 10 — — 10 10
Third-party Weight 113.1 kB — — 113.1 kB 113.1 kB
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

image 81.9 kB · 2 req
font 30.9 kB · 2 req
stylesheet 4.6 kB · 4 req
document 4.4 kB · 1 req
other 2.1 kB · 1 req
third party 113.1 kB · 5 req

Third parties 2 entities

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

Cloudinary 81.2 kB · 0 ms CPU
Adobe TypeKit 31.9 kB · 0 ms CPU

Page health

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

Main thread work

other 88 ms
style layout 62 ms
paint composite render 14 ms
script evaluation 9 ms
parse HTML 9 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 696 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 landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

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

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, 10:31 PM UTC 95 2.41 s 0 0 ms 123.8 kB 3/3 ±5 2,756 22.7s

Embed this score

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