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 ·

local.com.pk

https://www.local.com.pk/

98 81 100 100 ✓CWV 10AXE

Data from Aug 21, 2026, 1:46 PM UTC — 5h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 5h

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

Core Web Vitals field data, url-level

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

LCP 1.36 s good
INP — no data
CLS 0 good

Scores

98
Performance
no change
81
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.70 s — — 1.70 s 1.70 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 136 ms — — 136 ms 136 ms
FCP First Contentful Paint 1.55 s — — 1.55 s 1.55 s
Speed Index 1.55 s — — 1.55 s 1.55 s
TTFB Time to First Byte 476 ms — — 476 ms 476 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 86 ms
time to first byte 16 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.36 s good 90% good
CLS CWV 0 good 100% good
FCP 1.34 s good 84.6% good
TTFB 891 ms needs-improvement 69.4% good

Lab vs field

Lab LCP 1.70 s · field p75 1.36 s · real users are 0.8× 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.34 s — 0 1.34 s 891 ms
2026-08-08 1.52 s — 0 1.49 s 948 ms
2026-08-01 1.65 s — 0 1.57 s 1.16 s
2026-07-25 2.35 s — 0 2.33 s 1.53 s
2026-07-18 2.13 s — 0 1.98 s 1.24 s
2026-07-11 1.62 s — 0 1.62 s 1.00 s
2026-07-04 1.54 s — 0 1.53 s 891 ms
2026-06-27 1.12 s — 0 1.19 s 689 ms
2026-06-20 1.16 s — 0 1.19 s 705 ms
2026-06-13 1.04 s — 0 1.05 s 579 ms
2026-06-06 1.09 s — 0 1.11 s 671 ms
2026-05-30 1.19 s — 0 1.23 s 705 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 353.3 kB — — 353.3 kB 353.3 kB
Requests 13 — — 13 13
Third-party Weight 337.1 kB — — 337.1 kB 337.1 kB
Third-party CPU 91 ms — — 91 ms 91 ms
Unused JS 138.0 kB — — 138.0 kB 138.0 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 337.1 kB · 5 req
other 8.3 kB · 6 req
stylesheet 4.8 kB · 1 req
document 3.1 kB · 1 req
third party 337.1 kB · 8 req

Third parties 4 entities

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

Google Tag Manager 293.3 kB · 72 ms CPU
Cloudflare 22.9 kB · 7 ms CPU
Google Analytics 20.9 kB · 12 ms CPU
cloudflareinsights.com 35 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 359 ms
other 96 ms
script parse compile 78 ms
style layout 26 ms
parse HTML 7 ms
paint composite render 3 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 2 rules, 108 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 9 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node

Accessibility failures 2 of 11 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. 9 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 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 21, 2026, 1:46 PM UTC 98 1.70 s 0 136 ms 353.3 kB 3/3 ±0 2,470 21.7s

Embed this score

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