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 ·

pub.dev

https://pub.dev/

87 92 100 100 !AXE ✓CWV

Data from Aug 25, 2026, 4:37 PM UTC 13h old

Overall #835 Package Managers #4 · 1 measurement · since Aug 25, 2026

Core Web Vitals field data, url-level

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

LCP 1.72 s good
INP 96 ms good
CLS 0 good

Scores

87
Performance
no change
92
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.32 s — — 3.32 s 3.32 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 162 ms — — 162 ms 162 ms
FCP First Contentful Paint 2.46 s — — 2.46 s 2.46 s
Speed Index 2.46 s — — 2.46 s 2.46 s
TTFB Time to First Byte 630 ms — — 630 ms 630 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 3.32 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 191 ms
resource load duration 45 ms
time to first byte 28 ms
resource load delay 12 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.72 s good 85.1% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 96 ms good 91.3% good
CLS CWV 0 good 99.7% good
FCP 1.62 s good 78.1% good
TTFB 861 ms needs-improvement 71.7% good

Lab vs field

Lab LCP 3.32 s · field p75 1.72 s · real users are 0.52× 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-22 1.72 s 96 ms 0 1.62 s 859 ms
2026-08-15 1.73 s 99 ms 0 1.64 s 875 ms
2026-08-08 1.69 s 98 ms 0 1.62 s 863 ms
2026-08-01 1.67 s 98 ms 0 1.59 s 861 ms
2026-07-25 1.70 s 99 ms 0 1.62 s 886 ms
2026-07-18 1.70 s 102 ms 0 1.63 s 876 ms
2026-07-11 1.76 s 104 ms 0 1.68 s 920 ms
2026-07-04 1.79 s 105 ms 0 1.70 s 923 ms
2026-06-27 1.81 s 107 ms 0 1.71 s 922 ms
2026-06-20 1.78 s 104 ms 0 1.70 s 924 ms
2026-06-13 1.78 s 102 ms 0 1.69 s 918 ms
2026-06-06 1.75 s 102 ms 0 1.66 s 906 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 630 kB — — 630 kB 630 kB
Requests 38 — — 38 38
Third-party Weight 373 kB — — 373 kB 373 kB
Third-party CPU 96 ms — — 96 ms 96 ms
Unused JS 192 kB — — 192 kB 192 kB
Unused CSS 12.3 kB — — 12.3 kB 12.3 kB

By resource type

script 446 kB · 16 req
image 68.3 kB · 10 req
font 45.5 kB · 2 req
other 43.6 kB · 4 req
stylesheet 20.1 kB · 3 req
document 6.4 kB · 1 req
third party 373 kB · 10 req

Third parties 4 entities

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

Google Tag Manager 290 kB · 79 ms CPU
Google Fonts 49.0 kB · 0 ms CPU
Google Analytics 20.9 kB · 13 ms CPU
Google CDN 12.9 kB · 5 ms CPU

Page health

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

Main thread work

other 546 ms
script evaluation 526 ms
style layout 148 ms
script parse compile 141 ms
paint composite render 28 ms
parse HTML 17 ms
garbage collection 9 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 812 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 label-title-only — Form elements should have a visible label 1 node
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 26 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.

  • link-in-text-block — Links rely on color to be distinguishable. 1 node
  • target-size — Touch targets do not have sufficient size or spacing. 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

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 25, 2026, 4:37 PM UTC 87 3.32 s 0.003 162 ms 630 kB 3/3 ±12 2,286 26.7s

Embed this score

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