hex.pm
Data from Aug 25, 2026, 4:35 PM UTC 13h old
Overall #779 Package Managers #2 · 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 | 7.70 s | — | — | 7.70 s | 7.70 s | |
| CLS Cumulative Layout Shift | 0.092 | — | — | 0.092 | 0.092 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 2.94 s | — | — | 2.94 s | 2.94 s | |
| Speed Index | 2.94 s | — | — | 2.94 s | 2.94 s | |
| TTFB Time to First Byte | 646 ms | — | — | 646 ms | 646 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 7.70 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 | 1.15 s | good | 93.1% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 89 ms | good | 94.4% good |
| CLS CWV | 0 | good | 99.6% good |
| FCP | 737 ms | good | 96.2% good |
| TTFB | 481 ms | good | 90.5% good |
Lab vs field
Lab LCP 7.70 s · field p75 1.15 s · real users are 0.15× 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 | 1.15 s | 88 ms | 0 | 739 ms | 463 ms |
| 2026-08-15 | 1.19 s | 86 ms | 0 | 776 ms | 481 ms |
| 2026-08-08 | 1.15 s | 80 ms | 0 | 802 ms | 481 ms |
| 2026-08-01 | 961 ms | 76 ms | 0 | 732 ms | 453 ms |
| 2026-07-25 | 909 ms | 66 ms | 0 | 702 ms | 442 ms |
| 2026-07-18 | 828 ms | 61 ms | 0 | 646 ms | 402 ms |
| 2026-07-11 | 772 ms | 58 ms | 0 | 514 ms | 312 ms |
| 2026-07-04 | 814 ms | 54 ms | 0 | 507 ms | 303 ms |
| 2026-06-27 | 902 ms | 55 ms | 0 | 543 ms | 353 ms |
| 2026-06-20 | 929 ms | 67 ms | 0 | 573 ms | 317 ms |
| 2026-06-13 | 1.04 s | 69 ms | 0 | 658 ms | 361 ms |
| 2026-06-06 | 1.10 s | 69 ms | 0 | 726 ms | 408 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 2.52 MB | — | — | 2.52 MB | 2.52 MB | |
| Requests | 16 | — | — | 16 | 16 | |
| Third-party Weight | 81.1 kB | — | — | 81.1 kB | 81.1 kB | |
| Third-party CPU | 0 ms | — | — | 0 ms | 0 ms | |
| Unused JS | 41.9 kB | — | — | 41.9 kB | 41.9 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 1 entities
81.1 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 | 675 ms | — | — | 675 ms | 675 ms | |
| Long Tasks | 1 | — | — | 1 | 1 | |
| DOM Elements | 605 | — | — | 605 | 605 | |
| 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, 707 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:35 PM UTC | 68 | 7.70 s | 0.092 | 0 ms | 2.52 MB | 3/3 | ±2 | 2,240 | 33.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
hex.pm'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://hex.pm/"></speedlify2-score>