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 ·

catgirlin.space

https://catgirlin.space/

91 96 100 100 –CWV 16AXE

Data from Aug 20, 2026, 4:28 PM UTC — 26h old.

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

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.

Fl Hosted by Fly.io

Scores

91
Performance
no change
96
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.75 s — — 2.75 s 2.75 s
CLS Cumulative Layout Shift 0.105 — — 0.105 0.105
TBT Total Blocking Time 20 ms — — 20 ms 20 ms
FCP First Contentful Paint 2.00 s — — 2.00 s 2.00 s
Speed Index 2.00 s — — 2.00 s 2.00 s
TTFB Time to First Byte 1.03 s — — 1.03 s 1.03 s

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 428 ms
resource load duration 44 ms
element render delay 41 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 506.9 kB — — 506.9 kB 506.9 kB
Requests 26 — — 26 26
Third-party Weight 76.5 kB — — 76.5 kB 76.5 kB
Third-party CPU 5 ms — — 5 ms 5 ms
Unused JS 47.4 kB — — 47.4 kB 47.4 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 365.2 kB · 17 req
script 63.6 kB · 3 req
other 56.0 kB · 4 req
document 12.0 kB · 1 req
stylesheet 10.0 kB · 1 req
third party 76.5 kB · 7 req

Third parties 3 entities

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

splashcat.ink 72.0 kB · 0 ms CPU
szpunar.cloud 3.1 kB · 2 ms CPU
tinylytics.app 1.4 kB · 3 ms CPU

Page health

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

Main thread work

other 194 ms
style layout 108 ms
script evaluation 97 ms
paint composite render 50 ms
parse HTML 32 ms
script parse compile 13 ms

Axe violations axe-core 4.13.0, full rule set

16 violating nodes across 3 rules, 1224 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 14 nodes
  • 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

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, 4:28 PM UTC 91 2.75 s 0.105 20 ms 506.9 kB 3/3 ±8 3,195 36.4s

Embed this score

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