Skip to content
Audit Complete

Results for https://www.hashicorp.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 19:57 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

No favicon or icon links detected

Accessibility › Favicon & Branding
5

152 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.hashicorp.com)](https://beavercheck.com/results/4eb35237-3004-7fb0-4d5f-ac06e77b1bdb)
<a href="https://beavercheck.com/results/4eb35237-3004-7fb0-4d5f-ac06e77b1bdb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.hashicorp.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.hashicorp.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

61
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.91 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.81 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

498 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.70 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

10.22 s

Detailed Report

Audit breakdown by category with detailed findings.

61

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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.

URLTransfer SizeDuration
www.hashicorp.com/_next/static/css/01965cf281367182.css368 B
www.hashicorp.com/_next/static/css/56d3dcd9faec5bb7.css6.4 KiB150 ms
www.hashicorp.com/_next/static/css/caea2a6899256e83.css893 B150 ms
www.hashicorp.com/_next/static/css/ef4219439a11ffb9.css314 B
www.hashicorp.com/_next/static/css/c6075ba53acb498e.css5.5 KiB
www.hashicorp.com/_next/static/css/77d49a7e1842baff.css3.5 KiB
www.hashicorp.com/_next/static/css/629424d415e8a79b.css872 B
www.hashicorp.com/_next/static/css/1066f06ebe2328af.css1.2 KiB
www.hashicorp.com/_next/static/css/9059a6844ea231f1.css1.6 KiB
www.hashicorp.com/_next/static/css/108153a8f1e9f5db.css1.7 KiB
www.hashicorp.com/_next/static/css/ed9b1d3e1380e59b.css668 B
www.hashicorp.com/_next/static/css/a32fbf9c97a20505.css1.3 KiB
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css20.2 KiB300 ms
www.hashicorp.com/_next/static/css/3be47ef25458da4b.css6.1 KiB
www.hashicorp.com/_next/static/css/37627e2f78be09a9.css1.2 KiB
www.hashicorp.com/_next/static/css/9fed4ab059749512.css721 B
www.hashicorp.com/_next/static/css/6378479266424a10.css705 B
www.hashicorp.com/_next/static/css/69bb7cf32be95077.css852 B
www.hashicorp.com/_next/static/css/98027a586c29a17f.css862 B
www.hashicorp.com/_next/static/css/1669634e386534be.css915 B
www.hashicorp.com/_next/static/css/f6ceabd858d14431.css603 B
www.hashicorp.com/_next/static/css/b890e63d0a5bd128.css421 B
www.hashicorp.com/_next/static/css/cf25fb514c0e9dd2.css2.3 KiB
www.hashicorp.com/_next/static/css/587a4ed359d236d6.css597 B
www.hashicorp.com/_next/static/css/84f6538bc0e17b7d.css1.3 KiB
www.hashicorp.com/_next/static/css/dc135269f2f0dae7.css279 B
www.hashicorp.com/_next/static/css/12ed01fe97427b5e.css1.5 KiB
www.hashicorp.com/_next/static/css/f0d64dd8855c8eab.css306 B
www.hashicorp.com/_next/static/css/563b0fe42841e2f1.css1.1 KiB
www.hashicorp.com/_next/static/css/a64780ba39bbee71.css1.1 KiB
www.hashicorp.com/_next/static/css/d0d4167438a85aa8.css307 B
www.hashicorp.com/_next/static/css/a1948e0a243555c8.css1.2 KiB
www.hashicorp.com/_next/static/css/38956c947830126f.css1.9 KiB
www.hashicorp.com/_next/static/css/a035a96b81f5e8f2.css2.4 KiB
www.hashicorp.com/_next/static/css/e6281b363a9350ab.css602 B
www.hashicorp.com/_next/static/css/cbfb1fd33c48dec0.css859 B
www.hashicorp.com/_next/static/css/491bc751548e1ce1.css636 B
www.hashicorp.com/_next/static/css/778fdc69f7af7114.css2.4 KiB
www.hashicorp.com/_next/static/css/d7ea2d136c0f6c36.css1.6 KiB
www.hashicorp.com/_next/static/css/1857f677d781683e.css1.3 KiB
www.hashicorp.com/_next/static/css/a375f6663f9d4df9.css3.3 KiB
www.hashicorp.com/_next/static/css/e12617d514c74984.css2.7 KiB
www.hashicorp.com/_next/static/css/05d20268d1bb9fc1.css1.4 KiB
www.hashicorp.com/_next/static/css/796a43ba18c81aa4.css9.9 KiB
www.hashicorp.com/_next/static/css/8e4aac55660c9a8c.css369 B
www.hashicorp.com/_next/static/css/20ebf117539e078e.css2.2 KiB
www.hashicorp.com/_next/static/css/727973242bb33abd.css244 B
www.hashicorp.com/_next/static/css/f3d37eb4d80b6a16.css2.8 KiB
www.hashicorp.com/_next/static/css/1e0a56d5dc915bd7.css539 B
www.hashicorp.com/_next/static/css/1bbbf3ad62b064c8.css1.0 KiB150 ms
www.hashicorp.com/_next/static/css/4430a1b43db3fc8c.css1.0 KiB
www.hashicorp.com/_next/static/css/ab6e405182f9f1ed.css1.5 KiB
www.hashicorp.com/_next/static/css/50b3a2089bdb2651.css674 B
www.hashicorp.com/_next/static/css/4cc5463a0ae2ef1a.css767 B
www.hashicorp.com/_next/static/css/6518de381bed6b08.css678 B
www.hashicorp.com/_next/static/css/71d7d4e228424d46.css1.2 KiB
www.hashicorp.com/_next/static/css/17eb7e118d6552e4.css2.6 KiB
www.hashicorp.com/_next/static/css/c81b44e93c0d2122.css830 B
www.hashicorp.com/_next/static/css/107e5354ef88feb5.css1.2 KiB
www.hashicorp.com/_next/static/css/b2af274da38937ca.css2.3 KiB
www.hashicorp.com/_next/static/css/7fe2c60a01370ccb.css860 B
www.hashicorp.com/_next/static/css/bda8a297193d06b3.css1.0 KiB
www.hashicorp.com/_next/static/css/f3065546f9adb33e.css653 B
www.hashicorp.com/_next/static/css/c4cc774571cf3aa5.css1.1 KiB
www.hashicorp.com/_next/static/css/cccbdb8435f4243d.css1.0 KiB
www.hashicorp.com/_next/static/css/7eb514a1cca6da57.css2.6 KiB
www.hashicorp.com/_next/static/css/91cacd56357cbc31.css1.2 KiB
www.hashicorp.com/_next/static/css/bbafba885fda8115.css1.5 KiB
www.hashicorp.com/_next/static/css/cc0d4e57534ba0de.css5.3 KiB

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

RequestCache TTLTransfer Size
go.hashicorp.com/js/forms2/js/forms2.min.js14400.0 s67.5 KiB
/index.php/form/getForm?munchkinId=845-ZLF-191&form=2459&...0.0 ms2.2 KiB

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

URLResource SizeEst Savings
section#panel-:Rnd5kvf4upjsq: > div.style_root__hH0PD > div.style_image__k3olL > img section#panel-:Rnd5kvf4upjsq: > div.style_root__hH0PD > div.style_image__k3olL > img
/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2...71.5 KiB51.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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

Estimated savings: 1.3 s
URLTime Spent
www.hashicorp.com/1.3 s
www.hashicorp.com/0.0 ms
www.hashicorp.com/en0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 150 ms 18.6 KiB
URLTransfer SizeEst Savings
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css20.0 KiB18.6 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 900 ms 353.0 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-NRFH7Z9175.5 KiB81.2 KiB
www.hashicorp.com/_next/static/chunks/9626-ab3a83821a5f7ed4.js77.3 KiB55.6 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js67.0 KiB51.6 KiB
www.hashicorp.com/_next/static/chunks/cd24890f-ec7ef9f66f996c8d.js58.6 KiB48.7 KiB
www.hashicorp.com/_next/static/chunks/5014-0c132748d0a1a7de.js53.4 KiB43.5 KiB
www.hashicorp.com/_next/static/chunks/8796-08745d7caed41166.js51.1 KiB37.7 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js67.0 KiB34.6 KiB

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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable821 ms5.9 ms0.0 ms
www.hashicorp.com/_next/static/chunks/1528-1941c34bec7d3e71.js496 ms475 ms11 ms
www.hashicorp.com/en462 ms22 ms34 ms
www.hashicorp.com/_next/static/chunks/webpack-9955c6bc909ee506.js324 ms322 ms1.1 ms
www.hashicorp.com/280 ms250 ms6.7 ms
www.googletagmanager.com/gtm.js?id=GTM-NRFH7Z9265 ms200 ms56 ms
go.hashicorp.com/js/forms2/js/forms2.min.js141 ms108 ms17 ms

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

CategoryTime Spent
Script Evaluation1.5 s
Other969 ms
Script Parsing & Compilation386 ms
Style & Layout384 ms
Parse HTML & CSS136 ms
Rendering63 ms
Garbage Collection6.1 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable
Back/forward cache is disabled because WebSocket has been used.Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,160 KiB
●User Timing marks and measures 1 user timing
●Avoid long main-thread tasks 10 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Non-human identities (NHI) now outnumber humans by up to 50x. Read the Kuppinge… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
Our new Cloud Complexity Report reveals how global enterprise leaders are tackl… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
80% of organizations aren’t seeing the results they expect from the cloud. This… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
Discover how HashiCorp and IBM are transforming identity management with an "id… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.layout__bSrhA > div.style_root__0Zuhx > div.style_mobileImage__iC9ZE > img div.layout__bSrhA > div.style_root__0Zuhx > div.style_mobileImage__iC9ZE > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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.

Failing Elements
English div.dg-app > div > div.dg-main-language-dropdown > button.language-dropdown-trigger
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

SourceDescription
www.hashicorp.com/_next/static/chunks/1528-1941c34bec7d3e71.js
[PostHog.js] PostHog was initialized without a token. This likely indicates a misconfiguration. Please check the first argument passed to posthog.init()
www.hashicorp.com/
Failed to load resource: the server responded with a status of 429 ()
www.hashicorp.com/favicon.ico
Failed to load resource: the server responded with a status of 429 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.layout__bSrhA > div.style_root__0Zuhx > div.style_mobileImage__iC9ZE > img div.layout__bSrhA > div.style_root__0Zuhx > div.style_mobileImage__iC9ZE > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

93
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

503 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.70 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

54 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

997 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.13 s

Detailed Report

Audit breakdown by category with detailed findings.

93

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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

RequestCache TTLTransfer Size
go.hashicorp.com/js/forms2/js/forms2.min.js14400.0 s67.5 KiB
/index.php/form/getForm?munchkinId=845-ZLF-191&form=2459&...0.0 ms2.2 KiB

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

URLResource SizeEst Savings
section#panel-:Rnd5kvf4upjsq: > div.style_root__hH0PD > div.style_image__k3olL > img section#panel-:Rnd5kvf4upjsq: > div.style_root__hH0PD > div.style_image__k3olL > img
/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2...71.5 KiB53.9 KiB
body.mds-fonts > main#main > div.centered-text-hero_root__pde6O > img.centered-text-hero_image__C4grC body.mds-fonts > main#main > div.centered-text-hero_root__pde6O > img.centered-text-hero_image__C4grC
/_next/image?url=https%3A%2F%2Fwww.datocms-assets.com%2F2...25.3 KiB16.4 KiB

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.

URLTransfer Size
www.hashicorp.com/_next/static/css/1bbbf3ad62b064c8.css987 B
www.hashicorp.com/_next/static/css/f3d37eb4d80b6a16.css2.8 KiB
www.hashicorp.com/_next/static/css/12ed01fe97427b5e.css1.4 KiB
www.hashicorp.com/_next/static/css/108153a8f1e9f5db.css1.7 KiB
www.hashicorp.com/_next/static/css/cf25fb514c0e9dd2.css2.3 KiB
www.hashicorp.com/_next/static/css/1066f06ebe2328af.css1.2 KiB
www.hashicorp.com/_next/static/css/ef4219439a11ffb9.css360 B
www.hashicorp.com/_next/static/css/a035a96b81f5e8f2.css2.4 KiB
www.hashicorp.com/_next/static/css/a32fbf9c97a20505.css1.3 KiB
www.hashicorp.com/_next/static/css/9059a6844ea231f1.css1.6 KiB
www.hashicorp.com/_next/static/css/ab6e405182f9f1ed.css1.5 KiB
www.hashicorp.com/_next/static/css/f6ceabd858d14431.css545 B
www.hashicorp.com/_next/static/css/37627e2f78be09a9.css1.2 KiB
www.hashicorp.com/_next/static/css/563b0fe42841e2f1.css1.1 KiB
www.hashicorp.com/_next/static/css/84f6538bc0e17b7d.css1.3 KiB
www.hashicorp.com/_next/static/css/c4cc774571cf3aa5.css1.2 KiB
www.hashicorp.com/_next/static/css/ed9b1d3e1380e59b.css647 B
www.hashicorp.com/_next/static/css/4430a1b43db3fc8c.css1.0 KiB
www.hashicorp.com/_next/static/css/629424d415e8a79b.css948 B
www.hashicorp.com/_next/static/css/727973242bb33abd.css288 B
www.hashicorp.com/_next/static/css/05d20268d1bb9fc1.css1.3 KiB
www.hashicorp.com/_next/static/css/bbafba885fda8115.css1.5 KiB
www.hashicorp.com/_next/static/css/b2af274da38937ca.css2.3 KiB
www.hashicorp.com/_next/static/css/c6075ba53acb498e.css5.5 KiB
www.hashicorp.com/_next/static/css/77d49a7e1842baff.css3.4 KiB
www.hashicorp.com/_next/static/css/a64780ba39bbee71.css1.2 KiB
www.hashicorp.com/_next/static/css/98027a586c29a17f.css837 B
www.hashicorp.com/_next/static/css/a375f6663f9d4df9.css3.3 KiB
www.hashicorp.com/_next/static/css/69bb7cf32be95077.css909 B
www.hashicorp.com/_next/static/css/01965cf281367182.css320 B
www.hashicorp.com/_next/static/css/587a4ed359d236d6.css594 B
www.hashicorp.com/_next/static/css/107e5354ef88feb5.css1.3 KiB
www.hashicorp.com/_next/static/css/71d7d4e228424d46.css1.2 KiB
www.hashicorp.com/_next/static/css/6378479266424a10.css733 B
www.hashicorp.com/_next/static/css/f3065546f9adb33e.css629 B
www.hashicorp.com/_next/static/css/50b3a2089bdb2651.css692 B
www.hashicorp.com/_next/static/css/7fe2c60a01370ccb.css908 B
www.hashicorp.com/_next/static/css/caea2a6899256e83.css872 B
www.hashicorp.com/_next/static/css/7eb514a1cca6da57.css2.5 KiB
www.hashicorp.com/_next/static/css/c81b44e93c0d2122.css772 B
www.hashicorp.com/_next/static/css/cbfb1fd33c48dec0.css862 B
www.hashicorp.com/_next/static/css/20ebf117539e078e.css2.3 KiB
www.hashicorp.com/_next/static/css/778fdc69f7af7114.css2.4 KiB
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css20.2 KiB
www.hashicorp.com/_next/static/css/e6281b363a9350ab.css630 B
www.hashicorp.com/_next/static/css/1857f677d781683e.css1.4 KiB
www.hashicorp.com/_next/static/css/a1948e0a243555c8.css1.1 KiB
www.hashicorp.com/_next/static/css/9fed4ab059749512.css663 B
www.hashicorp.com/_next/static/css/dc135269f2f0dae7.css278 B
www.hashicorp.com/_next/static/css/b890e63d0a5bd128.css393 B
www.hashicorp.com/_next/static/css/e12617d514c74984.css2.7 KiB
www.hashicorp.com/_next/static/css/38956c947830126f.css1.9 KiB
www.hashicorp.com/_next/static/css/91cacd56357cbc31.css1.3 KiB
www.hashicorp.com/_next/static/css/d7ea2d136c0f6c36.css1.6 KiB
www.hashicorp.com/_next/static/css/56d3dcd9faec5bb7.css6.4 KiB
www.hashicorp.com/_next/static/css/17eb7e118d6552e4.css2.6 KiB
www.hashicorp.com/_next/static/css/bda8a297193d06b3.css1.0 KiB
www.hashicorp.com/_next/static/css/8e4aac55660c9a8c.css375 B
www.hashicorp.com/_next/static/css/6518de381bed6b08.css677 B
www.hashicorp.com/_next/static/css/4cc5463a0ae2ef1a.css737 B
www.hashicorp.com/_next/static/css/d0d4167438a85aa8.css266 B
www.hashicorp.com/_next/static/css/1e0a56d5dc915bd7.css574 B
www.hashicorp.com/_next/static/css/796a43ba18c81aa4.css9.8 KiB
www.hashicorp.com/_next/static/css/f0d64dd8855c8eab.css306 B
www.hashicorp.com/_next/static/css/cccbdb8435f4243d.css1.0 KiB
www.hashicorp.com/_next/static/css/cc0d4e57534ba0de.css5.3 KiB
www.hashicorp.com/_next/static/css/3be47ef25458da4b.css6.2 KiB
www.hashicorp.com/_next/static/css/1669634e386534be.css905 B
www.hashicorp.com/_next/static/css/491bc751548e1ce1.css550 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 160 ms 353.4 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtm.js?id=GTM-NRFH7Z9175.5 KiB81.2 KiB
www.hashicorp.com/_next/static/chunks/9626-ab3a83821a5f7ed4.js77.3 KiB55.8 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js67.0 KiB51.6 KiB
www.hashicorp.com/_next/static/chunks/cd24890f-ec7ef9f66f996c8d.js58.6 KiB48.7 KiB
www.hashicorp.com/_next/static/chunks/5014-0c132748d0a1a7de.js53.4 KiB43.5 KiB
www.hashicorp.com/_next/static/chunks/8796-08745d7caed41166.js51.1 KiB37.7 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js67.0 KiB34.9 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable
Back/forward cache is disabled because WebSocket has been used.Not actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 0.0 ms 18.6 KiB
URLTransfer SizeEst Savings
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css20.0 KiB18.6 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

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

Estimated savings: 423 ms
URLTime Spent
www.hashicorp.com/423 ms
www.hashicorp.com/0.0 ms
www.hashicorp.com/en0.0 ms
●Time to Interactive 2.1 s
●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,161 KiB
●User Timing marks and measures 1 user timing
●JavaScript execution time 0.4 s
●Minimizes main-thread work 0.9 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 100 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
94

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Failing Elements
AI assistant body.mds-fonts > q-focus-sentinel > div
After AI assistant body.mds-fonts > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Non-human identities (NHI) now outnumber humans by up to 50x. Read the Kuppinge… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
Our new Cloud Complexity Report reveals how global enterprise leaders are tackl… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
80% of organizations aren’t seeing the results they expect from the cloud. This… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL
Discover how HashiCorp and IBM are transforming identity management with an "id… li.style_card__5DpYX > a.style_cardInner__CnTtz > div.style_text__H0L2F > p.style_description__AJrmL

These are opportunities to improve the legibility of your content.

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.

Failing Elements
English div.dg-app > div > div.dg-main-language-dropdown > button.language-dropdown-trigger
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

SourceDescription
www.hashicorp.com/_next/static/chunks/1528-1941c34bec7d3e71.js
[PostHog.js] PostHog was initialized without a token. This likely indicates a misconfiguration. Please check the first argument passed to posthog.init()
www.hashicorp.com/
Failed to load resource: the server responded with a status of 429 ()
www.hashicorp.com/favicon.ico
Failed to load resource: the server responded with a status of 429 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback