webcomponents.dev
Data from Aug 21, 2026, 10:33 AM UTC — 8h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 8h
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 1.56 s | — | — | 1.56 s | 1.56 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 1.52 s | — | — | 1.52 s | 1.52 s | |
| Speed Index | 1.52 s | — | — | 1.52 s | 1.52 s | |
| TTFB Time to First Byte | 604 ms | — | — | 604 ms | 604 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 | 77.9 kB | — | — | 77.9 kB | 77.9 kB | |
| Requests | 28 | — | — | 28 | 28 | |
| Third-party Weight | 26.1 kB | — | — | 26.1 kB | 26.1 kB | |
| Third-party CPU | 2 ms | — | — | 2 ms | 2 ms | |
| Unused JS | 0 B | — | — | 0 B | 0 B | |
| Unused CSS | 0 B | — | — | 0 B | 0 B |
By resource type
Third parties 2 entities
26.1 kB transferred, 2 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 | 394 ms | — | — | 394 ms | 394 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 207 | — | — | 207 | 207 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 20 | — | — | 20 | 20 | |
| A11y Failures | 4 | — | — | 4 | 4 | |
| A11y Failing Nodes | 20 | — | — | 20 | 20 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
20 violating nodes across 4 rules, 511 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 16 nodes -
serious
link-in-text-block— Links must be distinguishable without relying on color 2 nodes -
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 4 of 26 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. 16 nodes -
link-in-text-block— Links rely on color to be distinguishable. 2 nodes -
target-size— Touch targets do not have sufficient size or spacing. 1 node -
label-content-name-mismatch— Elements with visible text labels do not have matching accessible names. 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 21, 2026, 10:33 AM UTC | 99 | 1.56 s | 0 | 0 ms | 77.9 kB | 3/3 | ±1 | 2,459 | 23.1s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
webcomponents.dev'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://webcomponents.dev/"></speedlify-score>