Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
go.hashicorp.com/js/forms2/js/forms2.min.js	14400.0 s	67.5 KiB
/index.php/form/getForm?munchkinId=845-ZLF-191&form=2459&...	0.0 ms	2.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est 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 KiB	53.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 KiB	16.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.hashicorp.com/_next/static/css/1bbbf3ad62b064c8.css	987 B
www.hashicorp.com/_next/static/css/f3d37eb4d80b6a16.css	2.8 KiB
www.hashicorp.com/_next/static/css/12ed01fe97427b5e.css	1.4 KiB
www.hashicorp.com/_next/static/css/108153a8f1e9f5db.css	1.7 KiB
www.hashicorp.com/_next/static/css/cf25fb514c0e9dd2.css	2.3 KiB
www.hashicorp.com/_next/static/css/1066f06ebe2328af.css	1.2 KiB
www.hashicorp.com/_next/static/css/ef4219439a11ffb9.css	360 B
www.hashicorp.com/_next/static/css/a035a96b81f5e8f2.css	2.4 KiB
www.hashicorp.com/_next/static/css/a32fbf9c97a20505.css	1.3 KiB
www.hashicorp.com/_next/static/css/9059a6844ea231f1.css	1.6 KiB
www.hashicorp.com/_next/static/css/ab6e405182f9f1ed.css	1.5 KiB
www.hashicorp.com/_next/static/css/f6ceabd858d14431.css	545 B
www.hashicorp.com/_next/static/css/37627e2f78be09a9.css	1.2 KiB
www.hashicorp.com/_next/static/css/563b0fe42841e2f1.css	1.1 KiB
www.hashicorp.com/_next/static/css/84f6538bc0e17b7d.css	1.3 KiB
www.hashicorp.com/_next/static/css/c4cc774571cf3aa5.css	1.2 KiB
www.hashicorp.com/_next/static/css/ed9b1d3e1380e59b.css	647 B
www.hashicorp.com/_next/static/css/4430a1b43db3fc8c.css	1.0 KiB
www.hashicorp.com/_next/static/css/629424d415e8a79b.css	948 B
www.hashicorp.com/_next/static/css/727973242bb33abd.css	288 B
www.hashicorp.com/_next/static/css/05d20268d1bb9fc1.css	1.3 KiB
www.hashicorp.com/_next/static/css/bbafba885fda8115.css	1.5 KiB
www.hashicorp.com/_next/static/css/b2af274da38937ca.css	2.3 KiB
www.hashicorp.com/_next/static/css/c6075ba53acb498e.css	5.5 KiB
www.hashicorp.com/_next/static/css/77d49a7e1842baff.css	3.4 KiB
www.hashicorp.com/_next/static/css/a64780ba39bbee71.css	1.2 KiB
www.hashicorp.com/_next/static/css/98027a586c29a17f.css	837 B
www.hashicorp.com/_next/static/css/a375f6663f9d4df9.css	3.3 KiB
www.hashicorp.com/_next/static/css/69bb7cf32be95077.css	909 B
www.hashicorp.com/_next/static/css/01965cf281367182.css	320 B
www.hashicorp.com/_next/static/css/587a4ed359d236d6.css	594 B
www.hashicorp.com/_next/static/css/107e5354ef88feb5.css	1.3 KiB
www.hashicorp.com/_next/static/css/71d7d4e228424d46.css	1.2 KiB
www.hashicorp.com/_next/static/css/6378479266424a10.css	733 B
www.hashicorp.com/_next/static/css/f3065546f9adb33e.css	629 B
www.hashicorp.com/_next/static/css/50b3a2089bdb2651.css	692 B
www.hashicorp.com/_next/static/css/7fe2c60a01370ccb.css	908 B
www.hashicorp.com/_next/static/css/caea2a6899256e83.css	872 B
www.hashicorp.com/_next/static/css/7eb514a1cca6da57.css	2.5 KiB
www.hashicorp.com/_next/static/css/c81b44e93c0d2122.css	772 B
www.hashicorp.com/_next/static/css/cbfb1fd33c48dec0.css	862 B
www.hashicorp.com/_next/static/css/20ebf117539e078e.css	2.3 KiB
www.hashicorp.com/_next/static/css/778fdc69f7af7114.css	2.4 KiB
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css	20.2 KiB
www.hashicorp.com/_next/static/css/e6281b363a9350ab.css	630 B
www.hashicorp.com/_next/static/css/1857f677d781683e.css	1.4 KiB
www.hashicorp.com/_next/static/css/a1948e0a243555c8.css	1.1 KiB
www.hashicorp.com/_next/static/css/9fed4ab059749512.css	663 B
www.hashicorp.com/_next/static/css/dc135269f2f0dae7.css	278 B
www.hashicorp.com/_next/static/css/b890e63d0a5bd128.css	393 B
www.hashicorp.com/_next/static/css/e12617d514c74984.css	2.7 KiB
www.hashicorp.com/_next/static/css/38956c947830126f.css	1.9 KiB
www.hashicorp.com/_next/static/css/91cacd56357cbc31.css	1.3 KiB
www.hashicorp.com/_next/static/css/d7ea2d136c0f6c36.css	1.6 KiB
www.hashicorp.com/_next/static/css/56d3dcd9faec5bb7.css	6.4 KiB
www.hashicorp.com/_next/static/css/17eb7e118d6552e4.css	2.6 KiB
www.hashicorp.com/_next/static/css/bda8a297193d06b3.css	1.0 KiB
www.hashicorp.com/_next/static/css/8e4aac55660c9a8c.css	375 B
www.hashicorp.com/_next/static/css/6518de381bed6b08.css	677 B
www.hashicorp.com/_next/static/css/4cc5463a0ae2ef1a.css	737 B
www.hashicorp.com/_next/static/css/d0d4167438a85aa8.css	266 B
www.hashicorp.com/_next/static/css/1e0a56d5dc915bd7.css	574 B
www.hashicorp.com/_next/static/css/796a43ba18c81aa4.css	9.8 KiB
www.hashicorp.com/_next/static/css/f0d64dd8855c8eab.css	306 B
www.hashicorp.com/_next/static/css/cccbdb8435f4243d.css	1.0 KiB
www.hashicorp.com/_next/static/css/cc0d4e57534ba0de.css	5.3 KiB
www.hashicorp.com/_next/static/css/3be47ef25458da4b.css	6.2 KiB
www.hashicorp.com/_next/static/css/1669634e386534be.css	905 B
www.hashicorp.com/_next/static/css/491bc751548e1ce1.css	550 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 353.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-NRFH7Z9	175.5 KiB	81.2 KiB
www.hashicorp.com/_next/static/chunks/9626-ab3a83821a5f7ed4.js	77.3 KiB	55.8 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js	67.0 KiB	51.6 KiB
www.hashicorp.com/_next/static/chunks/cd24890f-ec7ef9f66f996c8d.js	58.6 KiB	48.7 KiB
www.hashicorp.com/_next/static/chunks/5014-0c132748d0a1a7de.js	53.4 KiB	43.5 KiB
www.hashicorp.com/_next/static/chunks/8796-08745d7caed41166.js	51.1 KiB	37.7 KiB
go.hashicorp.com/js/forms2/js/forms2.min.js	67.0 KiB	34.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 18.6 KiB

URL	Transfer Size	Est Savings
www.hashicorp.com/_next/static/css/74e8ce1bec4dd7f1.css	20.0 KiB	18.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 423 ms

URL	Time Spent
www.hashicorp.com/	423 ms
www.hashicorp.com/	0.0 ms
www.hashicorp.com/en	0.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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
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

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.hashicorp.com/infrastructure-cloud	Learn more
www.hashicorp.com/infrastructure-cloud	Learn more
www.hashicorp.com/infrastructure-cloud	Learn more
www.hashicorp.com/cloud	Learn more
www.hashicorp.com/cloud	Learn more
www.hashicorp.com/cloud	Learn more
www.hashicorp.com/solutions/accelerate-innovation	Learn more
www.hashicorp.com/solutions/accelerate-innovation	Learn more
www.hashicorp.com/solutions/accelerate-innovation	Learn more
www.hashicorp.com/infrastructure-cloud/infrastructure-lifecycle-management	Learn more
www.hashicorp.com/infrastructure-cloud/security-lifecycle-management	Learn more

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