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 ·

example.chobble.com

https://example.chobble.com/

93 80 96 100 CWV AXE

Data from Aug 20, 2026, 10:29 PM UTC — 20h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 20h

Scores

93
Performance
no change
80
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 2.62 s 2.62 s 2.62 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 41 ms 41 ms 41 ms
FCP First Contentful Paint 2.47 s 2.47 s 2.47 s
Speed Index 2.47 s 2.47 s 2.47 s
TTFB Time to First Byte 619 ms 619 ms 619 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 139 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 9.19 MB 9.19 MB 9.19 MB
Requests 112 112 112
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 22.9 kB 22.9 kB 22.9 kB
Unused CSS 16.9 kB 16.9 kB 16.9 kB

By resource type

other 6.60 MB · 32 req
script 1.64 MB · 23 req
image 650.3 kB · 24 req
document 132.7 kB · 3 req
stylesheet 98.6 kB · 8 req
font 54.4 kB · 2 req
third party 8.52 MB · 65 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.21 s 1.21 s 1.21 s
Long Tasks 2 2 2
DOM Elements 1,173 1,173 1,173
A11y Failures 6 6 6
A11y Failing Nodes 20 20 20

Main thread work

other 534 ms
script evaluation 315 ms
style layout 207 ms
paint composite render 108 ms
parse HTML 44 ms
script parse compile 1 ms

Axe violations axe-core , full rule set

The axe run failed: Navigation timeout of 120000 ms exceeded

Accessibility failures 6 of 33 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.

  • aria-prohibited-attr — Elements use prohibited ARIA attributes 7 nodes
  • link-name — Links do not have a discernible name 6 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 nodes
  • aria-hidden-focus — `[aria-hidden="true"]` elements contain focusable descendents 2 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • link-in-text-block — Links rely on color to be distinguishable. 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, 10:29 PM UTC 93 2.62 s 0 41 ms 9.19 MB 3/3 ±37 3,268 156.4s

Embed this score

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