Home page

Largest Contentful Paint element

<img src="https://images.stripeassets.com/fzn2n1nzq965/18ArQFiazlljjIKGV0OnTb/2e15ca…" alt="" aria-hidden="true">

• 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 1,090 ms

  Covered by: Unblock the initial render →
  −1.1 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 505 KiB

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

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

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

  2.0 s

  Covered by: Cut and defer JavaScript →
  −800 ms

• Elements with visible text labels do not have matching accessible names.

  Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

• Links do not have descriptive text

  Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

  2 links found

  Covered by: Fix crawlability issues →

• 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
• Uses third-party cookies

  Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.

  9 cookies found
• Uses deprecated APIs

  Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

  1 warning found
• 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.
• 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

  Person/Organization markup found
• ✕
  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

  9271 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

• Google Tag Manager626 KBblocking 375 ms
• LinkedIn Ads42 KBblocking 14 ms
• reddit22 KBblocking 12 ms
• Twitter Online Conversion Tracking15 KBblocking 8 ms
• Bing Ads17 KBblocking 8 ms