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 ·

rohanbansal.com

https://www.rohanbansal.com/

90 90 100 100 –CWV 11AXE

Data from Aug 21, 2026, 2:35 PM UTC — 4h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 4h

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.

Vercel Hosted by Vercel

Scores

90
Performance
no change
90
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 1.56 s — — 1.56 s 1.56 s
CLS Cumulative Layout Shift 0.190 — — 0.190 0.190
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.56 s — — 1.56 s 1.56 s
Speed Index 1.56 s — — 1.56 s 1.56 s
TTFB Time to First Byte 630 ms — — 630 ms 630 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 69 ms
time to first byte 24 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 37.4 kB — — 37.4 kB 37.4 kB
Requests 7 — — 7 7
Third-party Weight 29.8 kB — — 29.8 kB 29.8 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 29.0 kB · 1 req
stylesheet 2.4 kB · 2 req
document 2.4 kB · 1 req
script 2.2 kB · 1 req
other 1.3 kB · 2 req
third party 29.8 kB · 2 req

Third parties 1 entities

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

Google Fonts 29.8 kB · 0 ms CPU

Page health

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

Main thread work

other 76 ms
style layout 52 ms
script evaluation 16 ms
paint composite render 8 ms
parse HTML 6 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

11 violating nodes across 2 rules, 190 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 6 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 5 nodes

Accessibility failures 2 of 21 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. 6 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 5 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, 2:35 PM UTC 90 1.56 s 0.190 0 ms 37.4 kB 3/3 ±2 2,375 22.7s

Embed this score

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