/changelog

Largest Contentful Paint element

<img src="https://webassets.linear.app/images/ornj730p/production/3770c67200a675f2ce…" alt="Linear Diffs showing the current pull request within a four-part stack, wi…" width="3600" height="2098" loading="lazy" decoding="async" class="Sz_9La_root" data-nimg="1" style="border-radius:8px" data-nosnippet="true" data-loaded="true">

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

  Covered by: Cut and defer JavaScript →
  −400 ms
• 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 →
• 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 299 KiB

  Covered by: Cut and defer JavaScript →
  −1.1 s
• 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 4,900 ms

  Covered by: Unblock the initial render →
  −4.9 s
• Improve image delivery

  Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

  Est savings of 375 KiB

  Covered by: Right-size and modernize images →
  −1.5 s

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

• 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

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

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