/connect-account/legal

• 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 90 ms
  −100 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,230 ms

  Covered by: Unblock the initial render →
  −2.3 s
• 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 →
• Avoid multiple page redirects

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

  Est savings of 760 ms
  −755 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 14 KiB

  Covered by: Cut and defer JavaScript →
• Use efficient cache lifetimes

  A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

  Est savings of 83 KiB

  Covered by: Set long cache lifetimes for static assets →

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

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

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

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

Top third-party vendors

• Google Tag Manager661 KBblocking 434 ms
• Bing Ads17 KBblocking 12 ms
• reddit22 KBblocking 12 ms
• Twitter Online Conversion Tracking17 KBblocking 11 ms
• DemandBase21 KBblocking 10 ms