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 ·

bigdetector.com

https://bigdetector.com/

84 84 100 100 CWV 17AXE

Data from Aug 20, 2026, 7:06 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.

Netlify Hosted by Netlify

Scores

84
Performance
no change
84
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 3.42 s 3.42 s 3.42 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 3.42 s 3.42 s 3.42 s
Speed Index 3.42 s 3.42 s 3.42 s
TTFB Time to First Byte 668 ms 668 ms 668 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 131 ms
time to first byte 25 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.02 MB 1.02 MB 1.02 MB
Requests 7 7 7
Third-party Weight 12.1 kB 12.1 kB 12.1 kB
Third-party CPU 4 ms 4 ms 4 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 746.4 kB · 2 req
document 259.4 kB · 1 req
script 9.2 kB · 1 req
stylesheet 2.9 kB · 2 req
other 264 B · 1 req
third party 12.4 kB · 4 req

Third parties 2 entities

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

Unpkg 10.9 kB · 4 ms CPU
Cloudflare CDN 1.2 kB · 0 ms CPU

Page health

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

Main thread work

other 200 ms
script parse compile 102 ms
parse HTML 86 ms
style layout 37 ms
script evaluation 34 ms
paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 4 rules, 253 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 13 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 3 of 16 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.

  • link-in-text-block — Links rely on color to be distinguishable. 2 nodes
  • link-name — Links do not have a discernible name 1 node
  • 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, 7:06 PM UTC 84 3.42 s 0 0 ms 1.02 MB 3/3 ±7 3,019 23.5s

Embed this score

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