/about

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

  Covered by: Unblock the initial render →
  −850 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.0 s

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

  Covered by: Cut and defer JavaScript →
  −1.2 s
• Improve image delivery

  Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

  Est savings of 94 KiB

  Covered by: Right-size and modernize images →
  −600 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 18 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 →

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

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

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

Top third-party vendors

• Google Tag Manager676 KBblocking 705 ms
• reddit26 KBblocking 51 ms
• Twitter Online Conversion Tracking19 KBblocking 17 ms
• Bing Ads18 KBblocking 13 ms
• DemandBase21 KBblocking 13 ms