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 ·

indrajith.dev

https://indrajith.dev/

55 92 92 100 –CWV 24AXE

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

Built Awesome · 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.

Op Hosted by Self-hosted

Scores

55
Performance
no change
92
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 20.58 s — — 20.58 s 20.58 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 18 ms — — 18 ms 18 ms
FCP First Contentful Paint 18.93 s — — 18.93 s 18.93 s
Speed Index 18.93 s — — 18.93 s 18.93 s
TTFB Time to First Byte 776 ms — — 776 ms 776 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 3.20 s
time to first byte 164 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.76 MB — — 3.76 MB 3.76 MB
Requests 40 — — 40 40
Third-party Weight 40.9 kB — — 40.9 kB 40.9 kB
Third-party CPU 7 ms — — 7 ms 7 ms
Unused JS 2.55 MB — — 2.55 MB 2.55 MB
Unused CSS 23.3 kB — — 23.3 kB 23.3 kB

By resource type

script 3.35 MB · 6 req
font 330.6 kB · 26 req
stylesheet 36.1 kB · 4 req
document 10.4 kB · 1 req
image 4.6 kB · 2 req
third party 40.9 kB · 7 req

Third parties 3 entities

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

Google Fonts 29.6 kB · 0 ms CPU
ko-fi.com 5.8 kB · 0 ms CPU
JSDelivr CDN 5.5 kB · 7 ms CPU

Page health

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

Main thread work

script evaluation 468 ms
script parse compile 299 ms
other 178 ms
style layout 64 ms
parse HTML 15 ms
paint composite render 11 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 1 rule, 314 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 24 nodes

Accessibility failures 1 of 13 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 24 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 2 console errors

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:14 AM UTC 55 20.58 s 0 18 ms 3.76 MB 3/3 ±21 2,389 39.1s

Embed this score

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