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 ·

belter.io

https://www.belter.io/

100 97 100 100 –CWV 2AXE

Data from Aug 21, 2026, 11:25 AM UTC — 7h old.

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

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.

Netlify Hosted by Netlify

Scores

100
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 904 ms — — 904 ms 904 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 789 ms — — 789 ms 789 ms
Speed Index 789 ms — — 789 ms 789 ms
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 42 ms
time to first byte 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 28.9 kB — — 28.9 kB 28.9 kB
Requests 5 — — 5 5
Third-party Weight 0 B — — 0 B 0 B
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 13.1 kB · 1 req
other 7.7 kB · 2 req
document 7.4 kB · 1 req
script 709 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 145 ms — — 145 ms 145 ms
Long Tasks 0 — — 0 0
DOM Elements 247 — — 247 247
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 74 ms
style layout 41 ms
script evaluation 13 ms
parse HTML 9 ms
paint composite render 7 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 461 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 heading-order — Heading levels should only increase by one 1 node
  • moderate region — All page content should be contained by landmarks 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 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 21, 2026, 11:25 AM UTC 100 904 ms 0 0 ms 28.9 kB 3/3 ±0 2,501 22.1s

Embed this score

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