/kb/builds

• 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 →
• 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.5 s

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

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

  Covered by: Cut and defer JavaScript →
  −1.6 s
• LCP breakdown

  Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
• 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 570 ms

  Covered by: Unblock the initial render →
  −550 ms

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

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

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

Top third-party vendors

• vercel.sh2 KB
• Sentry1 KB
• ctfassets.net337 KB