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 ·

kozen.or.jp

https://kozen.or.jp/

59 91 100 100 CWV 20AXE

Data from Aug 21, 2026, 3:03 AM UTC — 16h old.

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

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.

Self-hosted · nginx Hosted by Self-hosted

Scores

59
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 11.20 s 11.20 s 11.20 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 178 ms 178 ms 178 ms
FCP First Contentful Paint 4.64 s 4.64 s 4.64 s
Speed Index 6.04 s 6.04 s 6.04 s
TTFB Time to First Byte 805 ms 805 ms 805 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.94 s
resource load duration 213 ms
time to first byte 210 ms
resource load delay 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.88 MB 1.88 MB 1.88 MB
Requests 31 31 31
Third-party Weight 1.40 MB 1.40 MB 1.40 MB
Third-party CPU 54 ms 54 ms 54 ms
Unused JS 93.7 kB 93.7 kB 93.7 kB
Unused CSS 41.0 kB 41.0 kB 41.0 kB

By resource type

image 1.41 MB · 15 req
script 213.6 kB · 6 req
font 193.9 kB · 3 req
stylesheet 46.7 kB · 4 req
document 22.0 kB · 1 req
other 613 B · 1 req
third party 1.40 MB · 7 req

Third parties 4 entities

1.40 MB transferred, 54 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

kusarasenai.com 1.02 MB · 0 ms CPU
Cloudflare CDN 197.1 kB · 0 ms CPU
Google Tag Manager 162.5 kB · 54 ms CPU
Google Fonts 14.9 kB · 0 ms CPU

Page health

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

Main thread work

style layout 296 ms
script evaluation 275 ms
other 271 ms
script parse compile 53 ms
parse HTML 53 ms
paint composite render 26 ms

Axe violations axe-core 4.13.0, full rule set

20 violating nodes across 4 rules, 463 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 11 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 7 nodes
  • minor empty-heading — Headings should not be empty 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 23 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 11 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 7 nodes

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, 3:03 AM UTC 59 11.20 s 0 178 ms 1.88 MB 3/3 ±12 2,463 39.8s

Embed this score

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