packagist.org
Data from Aug 25, 2026, 4:35 PM UTC 13h old
Overall #1,444 Package Managers #13 · 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.45 s.
-
431 ms
-
862 ms
-
1.29 s
-
1.73 s
-
2.16 s
-
2.59 s
-
3.02 s
-
3.45 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 3.96 s | — | — | 3.96 s | 3.96 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 113 ms | — | — | 113 ms | 113 ms | |
| FCP First Contentful Paint | 1.63 s | — | — | 1.63 s | 1.63 s | |
| Speed Index | 3.14 s | — | — | 3.14 s | 3.14 s | |
| TTFB Time to First Byte | 726 ms | — | — | 726 ms | 726 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.96 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.56 s | needs-improvement | 73.5% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 187 ms | good | 76.7% good |
| CLS CWV | 0 | good | 96.4% good |
| FCP | 2.50 s | needs-improvement | 57.7% good |
| TTFB | 1.68 s | needs-improvement | 39.1% good |
Lab vs field
Lab LCP 3.96 s · field p75 2.56 s · real users are 0.65× 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.59 s | 194 ms | 0 | 2.51 s | 1.71 s |
| 2026-08-15 | 2.66 s | 198 ms | 0 | 2.62 s | 1.74 s |
| 2026-08-08 | 2.66 s | 192 ms | 0 | 2.62 s | 1.75 s |
| 2026-08-01 | 2.69 s | 193 ms | 0 | 2.64 s | 1.75 s |
| 2026-07-25 | 2.54 s | 173 ms | 0 | 2.51 s | 1.69 s |
| 2026-07-18 | 2.18 s | 164 ms | 0 | 2.17 s | 1.49 s |
| 2026-07-11 | 1.35 s | 155 ms | 0 | 1.36 s | 952 ms |
| 2026-07-04 | 1.29 s | 153 ms | 0 | 1.30 s | 902 ms |
| 2026-06-27 | 1.27 s | 148 ms | 0 | 1.26 s | 868 ms |
| 2026-06-20 | 1.30 s | 129 ms | 0 | 1.30 s | 867 ms |
| 2026-06-13 | 1.29 s | 125 ms | 0 | 1.28 s | 842 ms |
| 2026-06-06 | 1.28 s | 131 ms | 0 | 1.25 s | 806 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 463 kB | — | — | 463 kB | 463 kB | |
| Requests | 17 | — | — | 17 | 17 | |
| Third-party Weight | 4.7 kB | — | — | 4.7 kB | 4.7 kB | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 97.5 kB | — | — | 97.5 kB | 97.5 kB | |
| Unused CSS | 32.0 kB | — | — | 32.0 kB | 32.0 kB |
By resource type
Third parties 1 entities
4.7 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 | 619 ms | — | — | 619 ms | 619 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 707 | — | — | 707 | 707 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 20 | — | — | 20 | 20 | |
| A11y Failures | 4 | — | — | 4 | 4 | |
| A11y Failing Nodes | 16 | — | — | 16 | 16 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
20 violating nodes across 6 rules, 356 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
link-in-text-block— Links must be distinguishable without relying on color 9 nodes -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 5 nodes -
moderate
region— All page content should be contained by landmarks 3 nodes -
serious
html-has-lang— <html> element must have a lang attribute 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node -
serious
tabindex— Elements should not have tabindex greater than zero 1 node
Accessibility failures 4 of 21 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. 9 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 5 nodes -
html-has-lang— `<html>` element does not have a `[lang]` attribute 1 node -
tabindex— Some elements have a `[tabindex]` value greater than 0 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:35 PM UTC | 85 | 3.96 s | 0 | 113 ms | 463 kB | 3/3 | ±9 | 2,354 | 29.2s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
packagist.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://packagist.org/"></speedlify2-score>