nuget.org
Data from Aug 25, 2026, 4:37 PM UTC 13h old
Overall #1,414 Package Managers #10 · 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.
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 | 2.67 s | — | — | 2.67 s | 2.67 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 18 ms | — | — | 18 ms | 18 ms | |
| FCP First Contentful Paint | 1.51 s | — | — | 1.51 s | 1.51 s | |
| Speed Index | 1.51 s | — | — | 1.51 s | 1.51 s | |
| TTFB Time to First Byte | 606 ms | — | — | 606 ms | 606 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 2.67 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.80 s | needs-improvement | 72.3% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 104 ms | good | 92.2% good |
| CLS CWV | 0 | good | 96% good |
| FCP | 3.08 s | poor | 59.2% good |
| TTFB | 2.46 s | poor | 40.3% good |
Lab vs field
Lab LCP 2.67 s · field p75 2.80 s · real users are 1.05× slower 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.79 s | 103 ms | 0 | 3.07 s | 2.47 s |
| 2026-08-15 | 2.70 s | 99 ms | 0 | 2.98 s | 2.41 s |
| 2026-08-08 | 2.66 s | 96 ms | 0 | 2.98 s | 2.49 s |
| 2026-08-01 | 2.74 s | 96 ms | 0 | 3.14 s | 2.67 s |
| 2026-07-25 | 2.97 s | 98 ms | 0 | 3.51 s | 2.89 s |
| 2026-07-18 | 3.10 s | 104 ms | 0 | 3.60 s | 2.95 s |
| 2026-07-11 | 3.42 s | 107 ms | 0 | 3.79 s | 3.05 s |
| 2026-07-04 | 3.17 s | 112 ms | 0 | 3.58 s | 2.95 s |
| 2026-06-27 | 3.03 s | 112 ms | 0 | 3.43 s | 2.84 s |
| 2026-06-20 | 3.61 s | 112 ms | 0 | 3.84 s | 3.00 s |
| 2026-06-13 | 3.83 s | 112 ms | 0 | 3.99 s | 3.10 s |
| 2026-06-06 | 3.89 s | 113 ms | 0 | 4.04 s | 3.11 s |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 487 kB | — | — | 487 kB | 487 kB | |
| Requests | 20 | — | — | 20 | 20 | |
| Third-party Weight | 273 kB | — | — | 273 kB | 273 kB | |
| Third-party CPU | 18 ms | — | — | 18 ms | 18 ms | |
| Unused JS | 94.5 kB | — | — | 94.5 kB | 94.5 kB | |
| Unused CSS | 63.5 kB | — | — | 63.5 kB | 63.5 kB |
By resource type
Third parties 4 entities
273 kB transferred, 18 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 | 662 ms | — | — | 662 ms | 662 ms | |
| Long Tasks | 3 | — | — | 3 | 3 | |
| DOM Elements | 131 | — | — | 131 | 131 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 0 | — | — | 0 | 0 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
0 violating nodes across 0 rules, 256 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.
Accessibility failures 1 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.
-
label-content-name-mismatch— Elements with visible text labels do not have matching accessible names. 1 node
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:37 PM UTC | 96 | 2.67 s | 0 | 18 ms | 487 kB | 3/3 | ±15 | 2,352 | 22.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
nuget.org'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.nuget.org/"></speedlify2-score>