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 ·

bight.dev

https://bight.dev/

98 100 100 91 –CWV 1AXE

Data from Aug 20, 2026, 7:05 PM UTC — 24h old.

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

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

98
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 2.04 s — — 2.04 s 2.04 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1 ms — — 1 ms 1 ms
FCP First Contentful Paint 1.86 s — — 1.86 s 1.86 s
Speed Index 1.86 s — — 1.86 s 1.86 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 61 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 108.0 kB — — 108.0 kB 108.0 kB
Requests 8 — — 8 8
Third-party Weight 58.4 kB — — 58.4 kB 58.4 kB
Third-party CPU 27 ms — — 27 ms 27 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

script 57.9 kB · 2 req
font 45.6 kB · 3 req
document 2.1 kB · 1 req
other 1.9 kB · 1 req
image 434 B · 1 req
third party 58.4 kB · 3 req

Third parties 2 entities

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

Netlify 55.2 kB · 26 ms CPU
Fathom Analytics 3.2 kB · 1 ms CPU

Page health

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

Main thread work

script evaluation 97 ms
other 85 ms
script parse compile 26 ms
style layout 20 ms
parse HTML 12 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 135 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-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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, 7:05 PM UTC 98 2.04 s 0 1 ms 108.0 kB 3/3 ±1 2,491 21.6s

Embed this score

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