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 ·

my.stuffandthings.lol

https://my.stuffandthings.lol/

98 100 100 100 –CWV 3AXE

Data from Aug 21, 2026, 5:37 AM UTC — 13h old.

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

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.

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
Bu Hosted by Bunny CDN

Scores

98
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 1.81 s — — 1.81 s 1.81 s
CLS Cumulative Layout Shift 0.067 — — 0.067 0.067
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.62 s — — 1.62 s 1.62 s
Speed Index 1.62 s — — 1.62 s 1.62 s
TTFB Time to First Byte 604 ms — — 604 ms 604 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 157 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 125.1 kB — — 125.1 kB 125.1 kB
Requests 15 — — 15 15
Third-party Weight 639 B — — 639 B 639 B
Third-party CPU 1 ms — — 1 ms 1 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 51.9 kB · 3 req
script 42.6 kB · 3 req
image 10.4 kB · 4 req
stylesheet 6.3 kB · 1 req
document 5.1 kB · 1 req
third party 614 B · 2 req

Third parties 1 entities

639 B transferred, 1 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

neatstats.net 639 B · 1 ms CPU

Page health

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

Main thread work

other 124 ms
style layout 62 ms
script evaluation 39 ms
paint composite render 14 ms
script parse compile 13 ms
parse HTML 12 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 379 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 2 nodes
  • serious label-title-only — Form elements should have a visible label 1 node

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

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 2 nodes

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, 5:37 AM UTC 98 1.81 s 0.067 0 ms 125.1 kB 3/3 ±1 2,507 23.1s

Embed this score

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