/blog

Largest Contentful Paint element

<img alt="" width="448" height="252" loading="lazy" decoding="async" class="Sz_9La_root" data-nimg="1" data-nosnippet="true" data-loaded="true" src="https://webassets.linear.app/images/ornj730p/production/bb303fea92cee2cf3c…" style="border-radius: 5px;">

• Network dependency tree

  Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

  Covered by: Unblock the initial render →
• LCP breakdown

  Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
• LCP request discovery

  Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

  Covered by: Unblock the initial render →
• Forced reflow

  A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

  Covered by: Cut and defer JavaScript →
• Minimize main-thread work

  Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

  2.3 s

  Covered by: Cut and defer JavaScript →
  −200 ms
• Avoid multiple page redirects

  Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

  Est savings of 770 ms
  −770 ms

• Background and foreground colors do not have a sufficient contrast ratio.

  Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

  Covered by: Address accessibility gaps →
• Buttons do not have an accessible name

  When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

  Covered by: Address accessibility gaps →
• Heading elements are not in a sequentially-descending order

  Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

  Covered by: Address accessibility gaps →

• Browser errors were logged to the console

  Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
• Issues were logged in the `Issues` panel in Chrome Devtools

  Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
• Missing source maps for large first-party JavaScript

  Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

• ✓
  Canonical URL

  Page has a stable URL to cite
• ✕
  Author identity

  No author meta or schema — citation confidence drops without a named source
• ✕
  Publication date

  No publication or modification date in JSON-LD — answer engines deprioritize undated content
• !
  Article schema

  No Article / NewsArticle / BlogPosting schema — limits rich-snippet eligibility
• ✓
  Content depth

  8011 words — substantial for a citation source
• ✓
  Semantic structure

  Uses <main>, <article> or <header>

Top third-party vendors

• Sentry539 B