jcrt.org
Data from Aug 21, 2026, 1:17 AM UTC — 17h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 17h
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, origin-level
Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 2.49 s | — | — | 2.49 s | 2.49 s | |
| CLS Cumulative Layout Shift | 0.008 | — | — | 0.008 | 0.008 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.67 s | — | — | 1.67 s | 1.67 s | |
| Speed Index | 1.67 s | — | — | 1.67 s | 1.67 s | |
| TTFB Time to First Byte | 460 ms | — | — | 460 ms | 460 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.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 1.48 s | good | 85.7% good |
| CLS CWV | 0 | good | 96.4% good |
| FCP | 1.48 s | good | 79.9% good |
| TTFB | 1.12 s | needs-improvement | 65% good |
Lab vs field
Lab LCP 2.49 s · field p75 1.48 s · real users are 0.59× 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-15 | 1.52 s | — | 0 | 1.46 s | 1.14 s |
| 2026-08-08 | 2.08 s | — | 0 | 1.93 s | 1.26 s |
| 2026-08-01 | 1.97 s | — | 0 | 1.90 s | 1.24 s |
| 2026-07-25 | 2.07 s | — | 0 | 1.91 s | 1.23 s |
| 2026-07-18 | 2.01 s | — | 0 | 1.91 s | 1.22 s |
| 2026-07-11 | 2.01 s | — | 0 | 1.77 s | 1.08 s |
| 2026-07-04 | — | — | — | — | — |
| 2026-06-27 | — | — | — | — | — |
| 2026-06-20 | 1.87 s | — | 0 | 1.77 s | 1.32 s |
| 2026-06-13 | 1.87 s | — | 0 | 1.82 s | 1.33 s |
| 2026-06-06 | 2.01 s | — | 0 | 2.00 s | 1.58 s |
| 2026-05-30 | 2.00 s | — | 0 | 2.00 s | 1.64 s |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 265.8 kB | — | — | 265.8 kB | 265.8 kB | |
| Requests | 23 | — | — | 23 | 23 | |
| Third-party Weight | 19.7 kB | — | — | 19.7 kB | 19.7 kB | |
| Third-party CPU | 4 ms | — | — | 4 ms | 4 ms | |
| Unused JS | 23.9 kB | — | — | 23.9 kB | 23.9 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 2 entities
19.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 | 774 ms | — | — | 774 ms | 774 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 315 | — | — | 315 | 315 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 1 | — | — | 1 | 1 | |
| A11y Failing Nodes | 5 | — | — | 5 | 5 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 73 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.
-
critical
meta-refresh— Delayed refresh under 20 hours must not be used 1 node
Accessibility failures 1 of 27 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. 5 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, 1:17 AM UTC | 97 | 2.49 s | 0.008 | 0 ms | 265.8 kB | 3/3 | ±1 | 2,463 | 27s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
jcrt.org'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://jcrt.org/"></speedlify-score>