/connect/legal

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

  Covered by: Cut and defer JavaScript →
  −850 ms
• Avoid multiple page redirects

  Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

  Est savings of 920 ms
  −924 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.4 s

  Covered by: Cut and defer JavaScript →
  −850 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 2,190 ms

  Covered by: Unblock the initial render →
  −2.2 s
• Document request latency

  Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

  Est savings of 690 ms
  −700 ms

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

  4 links found

  Covered by: Fix crawlability issues →

• 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
• Uses deprecated APIs

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

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

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

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

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

Top third-party vendors

• Google Tag Manager661 KBblocking 686 ms
• reddit22 KBblocking 21 ms
• Twitter Online Conversion Tracking17 KBblocking 17 ms
• DemandBase21 KBblocking 14 ms
• Bing Ads17 KBblocking 14 ms