journal.thenewpolis.com
https://journal.thenewpolis.com/
Data from Aug 21, 2026, 3:02 AM UTC — 16h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 16h
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 6.59 s | — | — | 6.59 s | 6.59 s | |
| CLS Cumulative Layout Shift | 0.003 | — | — | 0.003 | 0.003 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 2.50 s | — | — | 2.50 s | 2.50 s | |
| Speed Index | 2.50 s | — | — | 2.50 s | 2.50 s | |
| TTFB Time to First Byte | 496 ms | — | — | 496 ms | 496 ms |
What LCP is made of
A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 1.03 MB | — | — | 1.03 MB | 1.03 MB | |
| Requests | 21 | — | — | 21 | 21 | |
| Third-party Weight | 85.7 kB | — | — | 85.7 kB | 85.7 kB | |
| Third-party CPU | 4 ms | — | — | 4 ms | 4 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 26.2 kB | — | — | 26.2 kB | 26.2 kB |
By resource type
Third parties 2 entities
85.7 kB transferred, 4 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 | 451 ms | — | — | 451 ms | 451 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 110 | — | — | 110 | 110 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 6 | — | — | 6 | 6 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 2 | — | — | 2 | 2 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
6 violating nodes across 5 rules, 184 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
color-contrast— Elements must meet minimum color contrast ratio thresholds 2 nodes -
moderate
landmark-main-is-top-level— Main landmark should not be contained in another landmark 1 node -
moderate
landmark-no-duplicate-main— Document should not have more than one main landmark 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node -
moderate
region— All page content should be contained by landmarks 1 node
Accessibility failures 1 of 20 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.
-
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 2 nodes
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 21, 2026, 3:02 AM UTC | 74 | 6.59 s | 0.003 | 0 ms | 1.03 MB | 3/3 | ±3 | 2,322 | 29.5s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
journal.thenewpolis.com's scores, updated whenever this instance
re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site!
<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://journal.thenewpolis.com/"></speedlify-score>