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 ·

kailoon.com

https://kailoon.com/

97 100 96 100 –CWV 1AXE

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

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

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.

Next.js Built with Next.js
Vercel Hosted by Vercel

Scores

97
Performance
no change
100
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 1.66 s — — 1.66 s 1.66 s
CLS Cumulative Layout Shift 0.069 — — 0.069 0.069
TBT Total Blocking Time 148 ms — — 148 ms 148 ms
FCP First Contentful Paint 806 ms — — 806 ms 806 ms
Speed Index 1.05 s — — 1.05 s 1.05 s
TTFB Time to First Byte 609 ms — — 609 ms 609 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 65 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 478.9 kB — — 478.9 kB 478.9 kB
Requests 43 — — 43 43
Third-party Weight 245.9 kB — — 245.9 kB 245.9 kB
Third-party CPU 53 ms — — 53 ms 53 ms
Unused JS 271.9 kB — — 271.9 kB 271.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 301.8 kB · 15 req
font 80.6 kB · 3 req
other 71.9 kB · 21 req
image 12.6 kB · 1 req
stylesheet 7.6 kB · 1 req
document 4.4 kB · 1 req
third party 245.9 kB · 10 req

Third parties 5 entities

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

Google Tag Manager 161.3 kB · 53 ms CPU
Google Fonts 80.6 kB · 0 ms CPU
sanity.io 3.5 kB · 1 ms CPU
vercel-insights.com 330 B · 0 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 638 ms
other 260 ms
style layout 126 ms
script parse compile 118 ms
paint composite render 18 ms
garbage collection 18 ms
parse HTML 9 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 219 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 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 1 console error

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 97 1.66 s 0.069 148 ms 478.9 kB 3/3 ±5 2,494 25.4s

Embed this score

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