speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

pnpm.io

https://pnpm.io/

59 93 85 83 ✗AXE ✗CWV

Data from Aug 27, 2026, 6:59 PM UTC old

Overall #1,478 Developer Tooling #76 · 1 measurement · since Aug 27, 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.

Docusaurus 3.10.2 Built with Docusaurus 3.10.2
Vercel Hosted by Vercel

Core Web Vitals field data, url-level

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

LCP 2.56 s needs-improvement
INP 238 ms needs-improvement
CLS 0.070 good

Scores

59
Performance
no change
93
Accessibility
no change
85
Best Practices
no change
83
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

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0.9% of pixels differ — they are nearly identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.97 s — — 6.97 s 6.97 s
CLS Cumulative Layout Shift 0.013 — — 0.013 0.013
TBT Total Blocking Time 441 ms — — 441 ms 441 ms
FCP First Contentful Paint 3.22 s — — 3.22 s 3.22 s
Speed Index 3.22 s — — 3.22 s 3.22 s
TTFB Time to First Byte 608 ms — — 608 ms 608 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 6.97 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 540 ms
time to first byte 4 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.56 s needs-improvement 74.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 238 ms needs-improvement 68.6% good
CLS CWV 0.070 good 78.9% good
FCP 1.66 s good 77.7% good
TTFB 544 ms good 86.6% good

Lab vs field LCP

Lab 6.97 s
Field p75 2.56 s

The lab LCP is 2.72× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-22 2.57 s 238 ms 0.070 1.70 s 555 ms
2026-08-15 2.60 s 238 ms 0.070 1.74 s 556 ms
2026-08-08 2.73 s 247 ms 0.070 1.97 s 612 ms
2026-08-01 2.68 s 211 ms 0.070 1.97 s 558 ms
2026-07-25 2.66 s 225 ms 0.070 1.97 s 548 ms
2026-07-18 2.59 s 220 ms 0.070 1.97 s 576 ms
2026-07-11 2.66 s 210 ms 0.120 1.96 s 560 ms
2026-07-04 2.81 s 214 ms 0.120 2.06 s 604 ms
2026-06-27 2.90 s 205 ms 0.120 2.00 s 550 ms
2026-06-20 2.90 s 195 ms 0.120 1.95 s 509 ms
2026-06-13 2.91 s 202 ms 0.090 1.93 s 495 ms
2026-06-06 2.67 s 196 ms 0.090 1.73 s 485 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.32 MB — — 3.32 MB 3.32 MB
Requests 81 — — 81 81
Third-party Weight 410 kB — — 410 kB 410 kB
Third-party CPU 115 ms — — 115 ms 115 ms
Unused JS 216 kB — — 216 kB 216 kB
Unused CSS 24.0 kB — — 24.0 kB 24.0 kB

By resource type

image 1.52 MB · 35 req
script 1.46 MB · 17 req
document 138 kB · 3 req
stylesheet 94.6 kB · 7 req
font 83.2 kB · 3 req
other 17.6 kB · 13 req
third party 1.55 MB · 37 req

Third parties 6 entities

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

Google Tag Manager 286 kB · 101 ms CPU
Google Fonts 50.3 kB · 0 ms CPU
bit.dev 21.9 kB · 0 ms CPU
Twitter 21.6 kB · 0 ms CPU
Google Analytics 20.9 kB · 13 ms CPU

Page health

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

Main thread work

other 6.87 s
style layout 2.44 s
paint composite render 2.40 s
script evaluation 1.45 s
script parse compile 192 ms
parse HTML 38 ms
garbage collection 24 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 5 rules, 1123 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.

  • minor image-redundant-alt — Alternative text of images should not be repeated as text 13 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node
  • critical image-alt — Images must have alternative text 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes
  • image-alt — Image elements do not have `[alt]` attributes 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 3 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 27, 2026, 6:59 PM UTC 59 6.97 s 0.013 441 ms 3.32 MB 3/3 ±29 2,411 83.2s

Embed this score

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