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 ·

kadotaproductions.com

https://www.kadotaproductions.com/

58 77 77 91 CWV 60AXE

Data from Aug 21, 2026, 6:41 PM UTC — 31m old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 31m

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
Netlify Hosted by Netlify

Scores

58
Performance
no change
77
Accessibility
no change
77
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.40 s 4.40 s 4.40 s
CLS Cumulative Layout Shift 0.438 0.438 0.438
TBT Total Blocking Time 106 ms 106 ms 106 ms
FCP First Contentful Paint 3.04 s 3.04 s 3.04 s
Speed Index 3.78 s 3.78 s 3.78 s
TTFB Time to First Byte 631 ms 631 ms 631 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 300 ms
time to first byte 34 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 17.51 MB 17.51 MB 17.51 MB
Requests 151 151 151
Third-party Weight 313.3 kB 313.3 kB 313.3 kB
Third-party CPU 44 ms 44 ms 44 ms
Unused JS 60.2 kB 60.2 kB 60.2 kB
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

other 13.96 MB · 62 req
image 3.02 MB · 32 req
font 248.7 kB · 5 req
script 170.0 kB · 26 req
document 83.8 kB · 13 req
stylesheet 22.2 kB · 12 req
third party 14.74 MB · 116 req

Third parties 3 entities

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

Adobe TypeKit 250.0 kB · 0 ms CPU
Netlify 55.3 kB · 38 ms CPU
Vimeo 8.0 kB · 7 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.52 s 1.52 s 1.52 s
Long Tasks 5 5 5
DOM Elements 228 228 228
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 60 60 60
A11y Failures 4 4 4
A11y Failing Nodes 32 32 32

Main thread work

other 652 ms
script evaluation 334 ms
style layout 242 ms
parse HTML 110 ms
script parse compile 109 ms
paint composite render 69 ms

Axe violations axe-core 4.13.0, full rule set

60 violating nodes across 6 rules, 446 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 22 nodes
  • serious link-name — Links must have discernible text 17 nodes
  • critical image-alt — Images must have alternative text 8 nodes
  • minor aria-allowed-role — ARIA role should be appropriate for the element 6 nodes
  • serious frame-title — Frames must have an accessible name 6 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 4 of 17 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 17 nodes
  • image-alt — Image elements do not have `[alt]` attributes 8 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 6 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 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, 6:41 PM UTC 58 4.40 s 0.438 106 ms 17.51 MB 3/3 ±20 2,357 85.8s

Embed this score

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