/changelog

Largest Contentful Paint element

<video preload="metadata" crossorigin="anonymous" poster="https://webassets.linear.app/images/ornj730p/production/b3ef54a4552ef1ca31…" src="https://webassets.linear.app/files/ornj730p/production/80f59b063433c661b3a…" width="1920" height="1080" class="_91f_Kq_video" style="aspect-ratio: 1920 / 1080; cursor: var(--cursor-pointer, var(--pointer, pointer…;" aria-busy="false">

• Legacy JavaScript

  Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

  Est savings of 9 KiB

  Covered by: Cut and defer JavaScript →
  −150 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 5,200 ms

  Covered by: Unblock the initial render →
  −5.2 s
• 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 332 KiB

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

  3.6 s

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

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

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

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

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