/blog

Largest Contentful Paint element

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

• Avoid multiple page redirects

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

  Est savings of 930 ms
  −932 ms
• Render-blocking requests

  Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

  Est savings of 2,430 ms

  Covered by: Unblock the initial render →
  −2.5 s
• Document request latency

  Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

  Est savings of 150 ms
  −150 ms
• 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 →
• Reduce unused JavaScript

  Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

  Est savings of 333 KiB

  Covered by: Cut and defer JavaScript →
  −900 ms
• Reduce JavaScript execution time

  Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

  1.9 s

  Covered by: Cut and defer JavaScript →
  −550 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 →
• 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 →
• 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 →

• 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.

• ✓
  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

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

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