jspm.org
Data from Aug 27, 2026, 6:59 PM UTC old
Overall #1,186 Developer Tooling #36 · 1 measurement · since Aug 27, 2026
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
Without JavaScript
The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.
0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 4.18 s | — | — | 4.18 s | 4.18 s | |
| CLS Cumulative Layout Shift | 0.001 | — | — | 0.001 | 0.001 | |
| TBT Total Blocking Time | 85 ms | — | — | 85 ms | 85 ms | |
| FCP First Contentful Paint | 2.81 s | — | — | 2.81 s | 2.81 s | |
| Speed Index | 2.99 s | — | — | 2.99 s | 2.99 s | |
| TTFB Time to First Byte | 664 ms | — | — | 664 ms | 664 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 4.18 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 285 kB | — | — | 285 kB | 285 kB | |
| Requests | 14 | — | — | 14 | 14 | |
| Third-party Weight | 223 kB | — | — | 223 kB | 223 kB | |
| Third-party CPU | 55 ms | — | — | 55 ms | 55 ms | |
| Unused JS | 69.8 kB | — | — | 69.8 kB | 69.8 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 3 entities
223 kB transferred, 55 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 | 438 ms | — | — | 438 ms | 438 ms | |
| Long Tasks | 2 | — | — | 2 | 2 | |
| DOM Elements | 98 | — | — | 98 | 98 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 8 | — | — | 8 | 8 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 1 | — | — | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
8 violating nodes across 2 rules, 152 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.
-
moderate
region— All page content should be contained by landmarks 7 nodes -
serious
link-name— Links must have discernible text 1 node
Accessibility failures 1 of 22 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-name— Links do not have a discernible name 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 27, 2026, 6:59 PM UTC | 81 | 4.18 s | 0.001 | 85 ms | 285 kB | 3/3 | ±9 | 2,961 | 21.6s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
jspm.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://jspm.org/"></speedlify2-score>