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 ·

bharatkat.axcora.com

https://bharatkat.axcora.com/

75 90 96 100 CWV 18AXE

Data from Aug 20, 2026, 7:06 PM UTC — 24h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 24h

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 2.0.1 Built with Eleventy 2.0.1
Cloudflare Hosted by Cloudflare

Scores

75
Performance
no change
90
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 7.24 s 7.24 s 7.24 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.72 s 1.72 s 1.72 s
Speed Index 1.72 s 1.72 s 1.72 s
TTFB Time to First Byte 642 ms 642 ms 642 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 149 ms
resource load duration 134 ms
time to first byte 74 ms
resource load delay 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.43 MB 3.43 MB 3.43 MB
Requests 43 43 43
Third-party Weight 229.7 kB 229.7 kB 229.7 kB
Third-party CPU 26 ms 26 ms 26 ms
Unused JS 29.0 kB 29.0 kB 29.0 kB
Unused CSS 43.8 kB 43.8 kB 43.8 kB

By resource type

image 3.13 MB · 27 req
font 160.8 kB · 3 req
script 75.9 kB · 2 req
stylesheet 58.6 kB · 9 req
document 6.8 kB · 1 req
third party 229.7 kB · 7 req

Third parties 3 entities

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

Unpkg 128.5 kB · 0 ms CPU
JSDelivr CDN 55.8 kB · 26 ms CPU
Google Fonts 45.4 kB · 0 ms CPU

Page health

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

Main thread work

other 302 ms
style layout 149 ms
script evaluation 114 ms
parse HTML 43 ms
paint composite render 26 ms
script parse compile 21 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 5 rules, 731 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 11 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious marquee — <marquee> elements are deprecated and must not be used 1 node

Accessibility failures 3 of 23 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.

  • target-size — Touch targets do not have sufficient size or spacing. 9 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes
  • 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 h2 4 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 20, 2026, 7:06 PM UTC 75 7.24 s 0 0 ms 3.43 MB 3/3 ±10 3,004 27.7s

Embed this score

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