/contact

• 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,810 ms

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

  2.2 s

  Covered by: Cut and defer JavaScript →
  −550 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 264 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 86 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 →

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

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

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

Top third-party vendors

• Google Tag Manager676 KBblocking 577 ms
• reddit26 KBblocking 19 ms
• Twitter Online Conversion Tracking19 KBblocking 16 ms
• LinkedIn Ads24 KBblocking 11 ms
• DemandBase21 KBblocking 11 ms