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 ·

bestwebventures.in

https://bestwebventures.in/

95 93 100 100 CWV 6AXE

Data from Aug 20, 2026, 3:50 PM UTC — 27h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

95
Performance
no change
93
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 2.35 s 2.35 s 2.35 s
CLS Cumulative Layout Shift 0.011 0.011 0.011
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.35 s 2.35 s 2.35 s
Speed Index 2.35 s 2.35 s 2.35 s
TTFB Time to First Byte 512 ms 512 ms 512 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 117 ms
element render delay 69 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 94.1 kB 94.1 kB 94.1 kB
Requests 8 8 8
Third-party Weight 84.7 kB 84.7 kB 84.7 kB
Third-party CPU 4 ms 4 ms 4 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

font 72.2 kB · 4 req
script 11.5 kB · 1 req
document 8.9 kB · 1 req
stylesheet 1.1 kB · 1 req
other 454 B · 1 req
third party 84.7 kB · 6 req

Third parties 2 entities

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

Google Fonts 73.3 kB · 0 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

style layout 121 ms
other 98 ms
script evaluation 45 ms
paint composite render 20 ms
parse HTML 11 ms
garbage collection 3 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 367 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 5 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 22 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. 5 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 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, 3:50 PM UTC 95 2.35 s 0.011 0 ms 94.1 kB 3/3 ±8 2,322 23.3s

Embed this score

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