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 ·

imkhoi.com

https://www.imkhoi.com/

78 95 100 100 –CWV 3AXE

Data from Aug 21, 2026, 12:45 PM UTC — 6h old.

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

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

Scores

78
Performance
no change
95
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 6.16 s — — 6.16 s 6.16 s
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 914 ms — — 914 ms 914 ms
Speed Index 914 ms — — 914 ms 914 ms
TTFB Time to First Byte 614 ms — — 614 ms 614 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 102 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.24 MB — — 1.24 MB 1.24 MB
Requests 16 — — 16 16
Third-party Weight 295.5 kB — — 295.5 kB 295.5 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 20.6 kB — — 20.6 kB 20.6 kB

By resource type

image 912.2 kB · 1 req
font 261.3 kB · 2 req
other 29.9 kB · 5 req
script 23.5 kB · 3 req
stylesheet 6.5 kB · 3 req
document 2.2 kB · 1 req
third party 295.5 kB · 8 req

Third parties 3 entities

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

FontAwesome CDN 290.8 kB · 0 ms CPU
zgo.at 4.4 kB · 2 ms CPU
goatcounter.com 379 B · 0 ms CPU

Page health

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

Main thread work

other 137 ms
script evaluation 89 ms
style layout 73 ms
parse HTML 22 ms
paint composite render 15 ms
script parse compile 14 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 260 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-in-text-block — Links must be distinguishable without relying on color 2 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 1 of 20 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-in-text-block — Links rely on color to be distinguishable. 2 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, 12:45 PM UTC 78 6.16 s 0.004 0 ms 1.24 MB 3/3 ±8 2,488 22.6s

Embed this score

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