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 ·

yarnpkg.com

https://yarnpkg.com/

68 93 100 92 ✗AXE ✗CWV

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

Overall #1,433 Package Managers #12 · 1 measurement · since Aug 25, 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.7.0 Built with Docusaurus 3.7.0
Netlify Hosted by Netlify

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.96 s good
INP 211 ms needs-improvement
CLS 0 good

Scores

68
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Filmstrip Lighthouse, mobile

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

  1. 407 ms
  2. 815 ms
  3. 1.22 s
  4. 1.63 s
  5. 2.04 s
  6. 2.44 s
  7. 2.85 s
  8. 3.26 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 8.71 s — — 8.71 s 8.71 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 294 ms — — 294 ms 294 ms
FCP First Contentful Paint 1.10 s — — 1.10 s 1.10 s
Speed Index 3.10 s — — 3.10 s 3.10 s
TTFB Time to First Byte 640 ms — — 640 ms 640 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 8.71 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 99 ms
resource load delay 86 ms
resource load duration 77 ms
time to first byte 28 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.96 s good 83.1% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 211 ms needs-improvement 73.4% good
CLS CWV 0 good 94.6% good
FCP 1.67 s good 78% good
TTFB 783 ms good 76.4% good

Lab vs field

Lab LCP 8.71 s · field p75 1.96 s · real users are 0.23× 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.96 s 211 ms 0 1.67 s 777 ms
2026-08-15 2.04 s 223 ms 0 1.74 s 786 ms
2026-08-08 1.96 s 233 ms 0 1.69 s 780 ms
2026-08-01 1.97 s 235 ms 0 1.70 s 788 ms
2026-07-25 2.00 s 242 ms 0 1.69 s 824 ms
2026-07-18 1.89 s 220 ms 0 1.64 s 813 ms
2026-07-11 1.93 s 215 ms 0 1.64 s 843 ms
2026-07-04 1.90 s 242 ms 0 1.62 s 819 ms
2026-06-27 1.85 s 234 ms 0 1.60 s 770 ms
2026-06-20 2.04 s 219 ms 0 1.69 s 837 ms
2026-06-13 2.07 s 209 ms 0 1.74 s 832 ms
2026-06-06 1.98 s 188 ms 0 1.70 s 831 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.70 MB — — 1.70 MB 1.70 MB
Requests 32 — — 32 32
Third-party Weight 54.9 kB — — 54.9 kB 54.9 kB
Third-party CPU 33 ms — — 33 ms 33 ms
Unused JS 290 kB — — 290 kB 290 kB
Unused CSS 50.1 kB — — 50.1 kB 50.1 kB

By resource type

image 966 kB · 10 req
script 608 kB · 7 req
stylesheet 58.1 kB · 1 req
font 45.5 kB · 1 req
other 12.5 kB · 10 req
document 7.0 kB · 1 req
third party 54.9 kB · 4 req

Third parties 3 entities

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

datadoghq-browser-agent.com 49.5 kB · 33 ms CPU
GitHub 5.3 kB · 0 ms CPU
browser-intake-datadoghq.eu 136 B · 0 ms CPU

Page health

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

Main thread work

other 2.86 s
script evaluation 939 ms
script parse compile 350 ms
style layout 82 ms
paint composite render 59 ms
parse HTML 21 ms
garbage collection 5 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 2 rules, 179 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.

  • critical image-alt — Images must have alternative text 6 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

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

  • image-alt — Image elements do not have `[alt]` attributes 6 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 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:38 PM UTC 68 8.71 s 0.002 294 ms 1.70 MB 3/3 ±11 2,325 30.3s

Embed this score

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