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 ·

kack.dev

https://kack.dev/

77 67 96 82 CWV 12AXE

Data from Aug 21, 2026, 1:16 AM UTC — 17h old.

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

Scores

77
Performance
no change
67
Accessibility
no change
96
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.90 s 4.90 s 4.90 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.33 s 2.33 s 2.33 s
Speed Index 4.22 s 4.22 s 4.22 s
TTFB Time to First Byte 775 ms 775 ms 775 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.47 s
resource load duration 693 ms
time to first byte 177 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 614.5 kB 614.5 kB 614.5 kB
Requests 13 13 13
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 518.7 kB · 6 req
font 78.0 kB · 3 req
document 8.1 kB · 1 req
stylesheet 6.3 kB · 1 req
other 2.2 kB · 1 req

Page health

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

Main thread work

other 117 ms
style layout 21 ms
script evaluation 10 ms
parse HTML 5 ms
paint composite render 4 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 5 rules, 72 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.

  • serious link-name — Links must have discernible text 4 nodes
  • critical image-alt — Images must have alternative text 3 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 4 of 12 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-name — Links do not have a discernible name 4 nodes
  • image-alt — Image elements do not have `[alt]` attributes 3 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 2 nodes
  • 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 http/1.1

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, 1:16 AM UTC 77 4.90 s 0 0 ms 614.5 kB 3/3 ±7 2,496 28.1s

Embed this score

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