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 ·

tabulate.io

https://www.tabulate.io/

72 91 100 100 –CWV 3AXE

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

Built Awesome · 1 measurement · since Aug 21, 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.

Eleventy Built with Eleventy
Self-hosted · Apache Hosted by Self-hosted

Scores

72
Performance
no change
91
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 12.34 s — — 12.34 s 12.34 s
CLS Cumulative Layout Shift 0.041 — — 0.041 0.041
TBT Total Blocking Time 47 ms — — 47 ms 47 ms
FCP First Contentful Paint 2.25 s — — 2.25 s 2.25 s
Speed Index 2.79 s — — 2.79 s 2.79 s
TTFB Time to First Byte 712 ms — — 712 ms 712 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 1.24 s
time to first byte 114 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.20 MB — — 2.20 MB 2.20 MB
Requests 25 — — 25 25
Third-party Weight 92.9 kB — — 92.9 kB 92.9 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 70.9 kB — — 70.9 kB 70.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.96 MB · 8 req
script 127.1 kB · 6 req
font 91.4 kB · 4 req
stylesheet 11.2 kB · 2 req
document 8.9 kB · 1 req
other 1.9 kB · 4 req
third party 92.9 kB · 5 req

Third parties 1 entities

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

bunny.net 92.9 kB · 0 ms CPU

Page health

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

Main thread work

other 179 ms
script evaluation 169 ms
style layout 145 ms
script parse compile 42 ms
paint composite render 20 ms
parse HTML 17 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 477 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 2 nodes
  • minor empty-heading — Headings should not be empty 1 node

Accessibility failures 2 of 21 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 2 nodes
  • button-name — Buttons do not have an accessible name 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, 2:39 PM UTC 72 12.34 s 0.041 47 ms 2.20 MB 3/3 ±14 2,243 31.5s

Embed this score

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