contentthread.com
Data from Aug 20, 2026, 8:32 PM UTC — 21h old.
Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 21h
https://aircompany.ai/en/adobe.
Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 14.05 s | — | — | 14.05 s | 14.05 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 289 ms | — | — | 289 ms | 289 ms | |
| FCP First Contentful Paint | 3.34 s | — | — | 3.34 s | 3.34 s | |
| Speed Index | 4.14 s | — | — | 4.14 s | 4.14 s | |
| TTFB Time to First Byte | 609 ms | — | — | 609 ms | 609 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 | 3.22 MB | — | — | 3.22 MB | 3.22 MB | |
| Requests | 85 | — | — | 85 | 85 | |
| Third-party Weight | 3.21 MB | — | — | 3.21 MB | 3.21 MB | |
| Third-party CPU | 305 ms | — | — | 305 ms | 305 ms | |
| Unused JS | 340.2 kB | — | — | 340.2 kB | 340.2 kB | |
| Unused CSS | 12.9 kB | — | — | 12.9 kB | 12.9 kB |
By resource type
Third parties 10 entities
3.21 MB transferred, 305 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 | 2.02 s | — | — | 2.02 s | 2.02 s | |
| Long Tasks | 8 | — | — | 8 | 8 | |
| DOM Elements | 659 | — | — | 659 | 659 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 14 | — | — | 14 | 14 | |
| A11y Failures | 6 | — | — | 6 | 6 | |
| A11y Failing Nodes | 19 | — | — | 19 | 19 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
14 violating nodes across 4 rules, 1035 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
aria-required-parent— Certain ARIA roles must be contained by particular parents 6 nodes -
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 6 nodes -
critical
aria-required-children— Certain ARIA roles must contain particular children 1 node -
critical
image-alt— Images must have alternative text 1 node
Accessibility failures 6 of 33 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.
-
aria-required-parent— `[role]`s are not contained by their required parent element 6 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 6 nodes -
target-size— Touch targets do not have sufficient size or spacing. 4 nodes -
aria-required-children— Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 1 node -
image-alt— Image elements do not have `[alt]` attributes 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 20, 2026, 8:32 PM UTC | 61 | 14.05 s | 0 | 289 ms | 3.22 MB | 3/3 | ±7 | 2,506 | 33.3s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
contentthread.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://contentthread.com/"></speedlify-score>