npmjs.com
Data from Aug 25, 2026, 4:36 PM UTC 13h old
Overall #793 Package Managers #3 · 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.
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.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 3.00 s.
-
375 ms
-
750 ms
-
1.13 s
-
1.50 s
-
1.88 s
-
2.25 s
-
2.63 s
-
3.00 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 8.06 s | — | — | 8.06 s | 8.06 s | |
| CLS Cumulative Layout Shift | 0.002 | — | — | 0.002 | 0.002 | |
| TBT Total Blocking Time | 252 ms | — | — | 252 ms | 252 ms | |
| FCP First Contentful Paint | 3.21 s | — | — | 3.21 s | 3.21 s | |
| Speed Index | 3.21 s | — | — | 3.21 s | 3.21 s | |
| TTFB Time to First Byte | 628 ms | — | — | 628 ms | 628 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.06 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.
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 | 2.03 s | good | 83% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 114 ms | good | 86.2% good |
| CLS CWV | 0.010 | good | 85.9% good |
| FCP | 1.82 s | needs-improvement | 75.4% good |
| TTFB | 1.07 s | needs-improvement | 66.7% good |
Lab vs field
Lab LCP 8.06 s · field p75 2.03 s · real users are 0.25× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 2026-08-22 | 2.04 s | 115 ms | 0.010 | 1.82 s | 1.07 s |
| 2026-08-15 | 2.15 s | 119 ms | 0.010 | 1.98 s | 1.16 s |
| 2026-08-08 | 2.17 s | 121 ms | 0.010 | 1.98 s | 1.16 s |
| 2026-08-01 | 2.19 s | 121 ms | 0.010 | 2.00 s | 1.16 s |
| 2026-07-25 | 2.19 s | 124 ms | 0.010 | 1.99 s | 1.16 s |
| 2026-07-18 | 2.06 s | 123 ms | 0.010 | 1.84 s | 1.07 s |
| 2026-07-11 | 2.03 s | 120 ms | 0.010 | 1.80 s | 1.04 s |
| 2026-07-04 | 2.01 s | 122 ms | 0.010 | 1.80 s | 1.04 s |
| 2026-06-27 | 2.03 s | 123 ms | 0.010 | 1.81 s | 1.04 s |
| 2026-06-20 | 2.09 s | 122 ms | 0.010 | 1.87 s | 1.05 s |
| 2026-06-13 | 2.10 s | 123 ms | 0 | 1.89 s | 1.02 s |
| 2026-06-06 | 2.10 s | 122 ms | 0 | 1.88 s | 1.00 s |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 1.21 MB | — | — | 1.21 MB | 1.21 MB | |
| Requests | 30 | — | — | 30 | 30 | |
| Third-party Weight | 86.8 kB | — | — | 86.8 kB | 86.8 kB | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 302 kB | — | — | 302 kB | 302 kB | |
| Unused CSS | 51.8 kB | — | — | 51.8 kB | 51.8 kB |
By resource type
Third parties 1 entities
86.8 kB transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 894 ms | — | — | 894 ms | 894 ms | |
| Long Tasks | 4 | — | — | 4 | 4 | |
| DOM Elements | 134 | — | — | 134 | 134 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 344 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.
Hygiene
Changes rarely — which is exactly why a change is worth noticing.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 25, 2026, 4:36 PM UTC | 64 | 8.06 s | 0.002 | 252 ms | 1.21 MB | 3/3 | ±8 | 2,294 | 27s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
npmjs.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://www.npmjs.com/"></speedlify2-score>