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 ·

indiagrant.com

https://indiagrant.com/

92 97 96 83 –CWV 3AXE

Data from Aug 20, 2026, 11:30 PM UTC — 19h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 19h

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.

Astro 5.12.0 Built with Astro 5.12.0
Cloudflare Hosted by Cloudflare

Scores

92
Performance
no change
97
Accessibility
no change
96
Best Practices
no change
83
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.71 s — — 2.71 s 2.71 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 2.56 s — — 2.56 s 2.56 s
Speed Index 2.56 s — — 2.56 s 2.56 s
TTFB Time to First Byte 460 ms — — 460 ms 460 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.

time to first byte 108 ms
element render delay 44 ms
resource load duration 19 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 145.8 kB — — 145.8 kB 145.8 kB
Requests 13 — — 13 13
Third-party Weight 105.8 kB — — 105.8 kB 105.8 kB
Third-party CPU 6 ms — — 6 ms 6 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 90.0 kB · 3 req
image 31.0 kB · 2 req
script 15.6 kB · 3 req
document 3.1 kB · 1 req
stylesheet 1.3 kB · 2 req
other 455 B · 1 req
third party 105.8 kB · 7 req

Third parties 3 entities

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

Adobe TypeKit 91.3 kB · 0 ms CPU
Cloudflare 11.5 kB · 4 ms CPU
nothingrandom.dev 3.1 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 246 ms — — 246 ms 246 ms
Long Tasks 0 — — 0 0
DOM Elements 29 — — 29 29
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 1 — — 1 1

Main thread work

other 114 ms
script evaluation 60 ms
style layout 59 ms
parse HTML 7 ms
paint composite render 4 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 56 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 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

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.

  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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 20, 2026, 11:30 PM UTC 92 2.71 s 0.004 0 ms 145.8 kB 3/3 ±2 2,452 22.3s

Embed this score

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