speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

geshan.com.np

https://geshan.com.np/

89 100 100 100 3AXE ✓CWV

Data from Aug 20, 2026, 10:32 PM UTC 2d old

Built Awesome #636 · 1 measurement · since Aug 20, 2026

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, origin-level

Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.

LCP 1.40 s good
INP — no data
CLS 0 good

Scores

89
Performance
no change
100
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.90 s — — 2.90 s 2.90 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 214 ms — — 214 ms 214 ms
FCP First Contentful Paint 2.29 s — — 2.29 s 2.29 s
Speed Index 2.29 s — — 2.29 s 2.29 s
TTFB Time to First Byte 468 ms — — 468 ms 468 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 2.90 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 202 ms
time to first byte 8 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.40 s good 89.9% good
CLS CWV 0 good 95% good
FCP 1.40 s good 83.3% good
TTFB 930 ms needs-improvement 69.6% good

Lab vs field

Lab LCP 2.90 s · field p75 1.40 s · real users are 0.48× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.40 s — 0 1.41 s 918 ms
2026-08-08 1.76 s 78 ms 0 1.76 s 1.11 s
2026-08-01 2.80 s 90 ms 0 2.80 s 2.00 s
2026-07-25 3.52 s 141 ms 0 3.52 s 2.56 s
2026-07-18 3.53 s 144 ms 0 3.53 s 2.57 s
2026-07-11 3.61 s 149 ms 0 3.60 s 2.58 s
2026-07-04 3.52 s 148 ms 0 3.56 s 2.58 s
2026-06-27 1.22 s — 0 1.16 s 779 ms
2026-06-20 1.14 s — 0 1.14 s 722 ms
2026-06-13 972 ms — 0 974 ms 642 ms
2026-06-06 1.15 s — 0 1.13 s 722 ms
2026-05-30 1.11 s — 0 981 ms 582 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 704 kB — — 704 kB 704 kB
Requests 40 — — 40 40
Third-party Weight 425 kB — — 425 kB 425 kB
Third-party CPU 146 ms — — 146 ms 146 ms
Unused JS 211 kB — — 211 kB 211 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 436 kB · 7 req
font 160 kB · 9 req
image 62.8 kB · 10 req
other 23.8 kB · 11 req
document 13.1 kB · 1 req
stylesheet 8.7 kB · 2 req
third party 425 kB · 12 req

Third parties 6 entities

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

Google Tag Manager 319 kB · 86 ms CPU
JSDelivr CDN 83.1 kB · 51 ms CPU
Cloudflare 22.9 kB · 8 ms CPU
featureassets.org 151 B · 0 ms CPU
prodregistryv2.org 74 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 546 ms
other 266 ms
style layout 178 ms
script parse compile 123 ms
paint composite render 34 ms
parse HTML 18 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 763 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 landmark-contentinfo-is-top-level — Contentinfo landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-contentinfo — Document should not have more than one contentinfo landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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, 10:32 PM UTC 89 2.90 s 0 214 ms 704 kB 3/3 ±2 2,256 27.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show geshan.com.np's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://geshan.com.np/"></speedlify2-score>