chromeos.dev/en
Data from Aug 20, 2026, 7:32 PM UTC 3d old
11ty Emeritus · 1 measurement · since Aug 20, 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-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.63 s | — | — | 2.63 s | 2.63 s | |
| CLS Cumulative Layout Shift | 0.001 | — | — | 0.001 | 0.001 | |
| TBT Total Blocking Time | 360 ms | — | — | 360 ms | 360 ms | |
| FCP First Contentful Paint | 1.53 s | — | — | 1.53 s | 1.53 s | |
| Speed Index | 1.53 s | — | — | 1.53 s | 1.53 s | |
| TTFB Time to First Byte | 603 ms | — | — | 603 ms | 603 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 2.63 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-22 → 2026-08-18). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 3.35 s | needs-improvement | 64% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 232 ms | needs-improvement | 70.4% good |
| CLS CWV | 0.010 | good | 91.9% good |
| FCP | 1.52 s | good | 79.8% good |
| TTFB | 550 ms | good | 84.2% good |
Lab vs field
Lab LCP 2.63 s · field p75 3.35 s · real users are 1.27× slower 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 | 3.39 s | 230 ms | 0.010 | 1.54 s | 562 ms |
| 2026-08-08 | 3.24 s | 222 ms | 0 | 1.56 s | 553 ms |
| 2026-08-01 | 3.32 s | 217 ms | 0.010 | 1.59 s | 567 ms |
| 2026-07-25 | 3.58 s | 234 ms | 0 | 1.72 s | 643 ms |
| 2026-07-18 | 3.52 s | 235 ms | 0.010 | 1.69 s | 631 ms |
| 2026-07-11 | 3.69 s | 250 ms | 0.010 | 1.69 s | 646 ms |
| 2026-07-04 | 3.64 s | 262 ms | 0.010 | 1.71 s | 647 ms |
| 2026-06-27 | 3.54 s | 246 ms | 0.010 | 1.66 s | 626 ms |
| 2026-06-20 | 3.56 s | 238 ms | 0.010 | 1.71 s | 630 ms |
| 2026-06-13 | 3.54 s | 226 ms | 0.010 | 1.70 s | 619 ms |
| 2026-06-06 | 3.55 s | 222 ms | 0.010 | 1.69 s | 600 ms |
| 2026-05-30 | 3.50 s | 214 ms | 0.010 | 1.68 s | 598 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 982 kB | — | — | 982 kB | 982 kB | |
| Requests | 58 | — | — | 58 | 58 | |
| Third-party Weight | 653 kB | — | — | 653 kB | 653 kB | |
| Third-party CPU | 118 ms | — | — | 118 ms | 118 ms | |
| Unused JS | 181 kB | — | — | 181 kB | 181 kB | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 5 entities
653 kB transferred, 118 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 | 1.95 s | — | — | 1.95 s | 1.95 s | |
| Long Tasks | 8 | — | — | 8 | 8 | |
| DOM Elements | 955 | — | — | 955 | 955 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 6 | — | — | 6 | 6 | |
| A11y Failures | 3 | — | — | 3 | 3 | |
| A11y Failing Nodes | 7 | — | — | 7 | 7 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
6 violating nodes across 5 rules, 763 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
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes -
critical
button-name— Buttons must have discernible text 1 node -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 1 node -
moderate
heading-order— Heading levels should only increase by one 1 node -
moderate
landmark-no-duplicate-contentinfo— Document should not have more than one contentinfo landmark 1 node
Accessibility failures 3 of 29 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 -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 1 node -
heading-order— Heading elements are not in a sequentially-descending order 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 20, 2026, 7:32 PM UTC | 88 | 2.63 s | 0.001 | 360 ms | 982 kB | 3/3 | ±6 | 2,377 | 28.2s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
chromeos.dev/en'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://chromeos.dev/en"></speedlify2-score>