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 ·

clean.000000076.xyz

https://clean.000000076.xyz/

99 98 96 100 –CWV 2AXE

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

Build Awesome Starters · 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.

Eleventy 3.1.6 Built with Eleventy 3.1.6
Cloudflare Hosted by Cloudflare

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.83 s — — 1.83 s 1.83 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 23 ms — — 23 ms 23 ms
FCP First Contentful Paint 1.68 s — — 1.68 s 1.68 s
Speed Index 1.68 s — — 1.68 s 1.68 s
TTFB Time to First Byte 461 ms — — 461 ms 461 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 350 ms
element render delay 35 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 624.3 kB — — 624.3 kB 624.3 kB
Requests 10 — — 10 10
Third-party Weight 516.9 kB — — 516.9 kB 516.9 kB
Third-party CPU 28 ms — — 28 ms 28 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 29.1 kB — — 29.1 kB 29.1 kB

By resource type

script 539.9 kB · 3 req
other 51.6 kB · 5 req
document 32.8 kB · 1 req
third party 516.9 kB · 3 req

Third parties 2 entities

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

FontAwesome CDN 505.4 kB · 27 ms CPU
Cloudflare 11.5 kB · 2 ms CPU

Page health

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

Main thread work

other 190 ms
script evaluation 70 ms
script parse compile 66 ms
style layout 35 ms
parse HTML 19 ms
paint composite render 4 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 189 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 2 of 21 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
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3 1 console error

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:38 PM UTC 99 1.83 s 0 23 ms 624.3 kB 3/3 ±1 4,249 24.4s

Embed this score

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