/docs/oidc

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

  2.0 s

  Covered by: Cut and defer JavaScript →
  −450 ms
• 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.3 s

  Covered by: Cut and defer JavaScript →
  −450 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 51 KiB

  Covered by: Cut and defer JavaScript →
  −150 ms
• Reduce unused CSS

  Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

  Est savings of 12 KiB

  Covered by: Unblock the initial render →
  −150 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 →
• 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 850 KiB

  Covered by: Cut and defer JavaScript →
  −150 ms

• 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 →
• 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 →
• `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

  Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

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

  Person/Organization markup found
• ✓
  Publication date

  datePublished / dateModified present
• ✓
  Article schema

  Article-shaped JSON-LD present
• ✓
  Content depth

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

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

Schema.org types on this page

Vocabulary the page exposes to search engines and LLMs through JSON-LD blocks.

Top third-party vendors

• vercel.sh7 KB
• Sentry1 KB