/contact

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

  Covered by: Cut and defer JavaScript →
  −1.4 s
• 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,390 ms

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

  6.0 s

  Covered by: Cut and defer JavaScript →
  −1.7 s
• 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 9 KiB

  Covered by: Cut and defer JavaScript →
  −150 ms

• Buttons do not have an accessible name

  When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

  Covered by: Address accessibility gaps →

• Document does not have a meta description

  Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

  Covered by: Fix crawlability issues →

• 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

  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

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

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

Top third-party vendors

• LinkedIn Ads23 KBblocking 51 ms