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 ·

debitpay.directory

https://debitpay.directory/

95 100 100 91 –CWV 4AXE

Data from Aug 21, 2026, 2:37 PM UTC — 4h old.

Built Awesome · 2 measurements · since Aug 20, 2026 · last attempt 4h

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 · nginx Hosted by Self-hosted

Scores

95
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.58 s — — 1.58 s 1.58 s
CLS Cumulative Layout Shift 0.135 — — 0.135 0.135
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 949 ms — — 949 ms 949 ms
Speed Index 949 ms — — 949 ms 949 ms
TTFB Time to First Byte 625 ms — — 625 ms 625 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 122 ms
time to first byte 45 ms

Page weight

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

By resource type

image 11.9 kB · 3 req
script 7.9 kB · 2 req
stylesheet 5.2 kB · 1 req
document 2.0 kB · 1 req
other 1.1 kB · 3 req
third party 7.4 kB · 4 req

Third parties 2 entities

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

parity.domains 6.3 kB · 3 ms CPU
namecheap.com 1.1 kB · 0 ms CPU

Page health

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

Main thread work

other 119 ms
script evaluation 41 ms
style layout 36 ms
paint composite render 12 ms
parse HTML 8 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 1 rule, 143 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes

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

  • td-has-header — `<td>` elements in a large `<table>` do not have table headers. 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 21, 2026, 2:37 PM UTC 95 1.58 s 0.135 0 ms 28.2 kB 3/3 ±5 2,477 24.8s
Aug 20, 2026, 7:37 PM UTC NO_FCP: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP) 270.2s

Embed this score

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