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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:119.982 source:map[column:89807 line:2 type:source-location url:https://redis.io/_next/static/chunks/7369-0f0754218170d7e9.js?dpl=dpl_em4Txm4spqw9TmwDRzvoK8nocXcw urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:112.474 source:map[type:text value:[unattributed]]] map[reflowTime:118.336 source:map[column:14754 line:0 type:source-location url:https://redis.io/_next/static/chunks/5289-ae69001eab3be3dd.js?dpl=dpl_em4Txm4spqw9TmwDRzvoK8nocXcw urlProvider:network]] map[reflowTime:1.713 source:map[column:1793 line:0 type:source-location url:https://redis.io/_next/static/chunks/5289-ae69001eab3be3dd.js?dpl=dpl_em4Txm4spqw9TmwDRzvoK8nocXcw urlProvider:network]] map[reflowTime:1.47 source:map[column:21046 line:0 type:source-location url:https://redis.io/_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4Txm4spqw9TmwDRzvoK8nocXcw urlProvider:network]] map[reflowTime:1.909 source:map[column:280 line:14 type:source-location url:https://consent.trustarc.com/asset/notice.js/v/v1.7-8549 urlProvider:network]] map[reflowTime:0.176 source:map[column:3946 line:6938 type:source-location url:https://consent.trustarc.com/asset/adv-bundle.js?v=v1.7-8549 urlProvider:network]] map[reflowTime:44.85 source:map[column:521 line:18 type:source-location url:https://consent.trustarc.com/asset/adv-bundle.js?v=v1.7-8549 urlProvider:network]] map[reflowTime:0.141 source:map[column:1504 line:25 type:source-location url:https://consent.trustarc.com/asset/adv-bundle.js?v=v1.7-8549 urlProvider:network]]]

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

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	Duration
/_next/static/css/49be2de586598768.css?dpl=dpl_em4Txm4spq...	1.1 KiB
/_next/static/css/84d28999428b7bf8.css?dpl=dpl_em4Txm4spq...	11.6 KiB
/_next/static/css/0f8cab01664563d4.css?dpl=dpl_em4Txm4spq...	5.1 KiB
/_next/static/css/a7bcc090cd00e64d.css?dpl=dpl_em4Txm4spq...	20.1 KiB	56 ms
/_next/static/css/783c2e38c0c8b2d8.css?dpl=dpl_em4Txm4spq...	18.9 KiB
/_next/static/css/38b43148ef4cd4ee.css?dpl=dpl_em4Txm4spq...	19.5 KiB
/_next/static/css/39aa05b323db7ec8.css?dpl=dpl_em4Txm4spq...	18.9 KiB	56 ms
/_next/static/css/f771e03d2bb60b2c.css?dpl=dpl_em4Txm4spq...	7.7 KiB
/_next/static/css/09f20b3b11943100.css?dpl=dpl_em4Txm4spq...	4.0 KiB
/_next/static/css/3b0659f7714ffcdf.css?dpl=dpl_em4Txm4spq...	458 B

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
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	167.8 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	64.8 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js	60.0 s	40.1 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	20.8 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	16.2 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	13.5 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	0.0 ms	9.2 KiB
/notice?domain=redis.com&c=teconsent&js=nj&noticeType=bb&...	3600.0 s	6.2 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/next-integrations/actions/amplitude-plugins/f12a4347e108...	0.0 ms	2.7 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	2.4 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	1.9 KiB
cdn.jsdelivr.net/npm/hockeystack@latest/hockeystack.min.js	604800.0 s	10.1 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	1012 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	971 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	914 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	60.0 s	678 B

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
TrustArc Logo `div.gdpr > div#cookieMainHeader > span.logo > img`	consent.trustarc.com/get?name=Redis_v0424.png	46.2 KiB	43.2 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 256 ms

URL	Time Spent
www.redis.io/	256 ms
redis.io/	0.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 110 ms 82.4 KiB

URL	Transfer Size	Est Savings
/_next/static/css/a7bcc090cd00e64d.css?dpl=dpl_em4Txm4spq...	19.9 KiB	19.6 KiB
/_next/static/css/38b43148ef4cd4ee.css?dpl=dpl_em4Txm4spq...	19.4 KiB	18.9 KiB
/_next/static/css/783c2e38c0c8b2d8.css?dpl=dpl_em4Txm4spq...	18.7 KiB	16.8 KiB
/_next/static/css/39aa05b323db7ec8.css?dpl=dpl_em4Txm4spq...	18.7 KiB	15.7 KiB
/_next/static/css/84d28999428b7bf8.css?dpl=dpl_em4Txm4spq...	11.4 KiB	11.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 110 ms 1.1 MiB

URL	Transfer Size	Est Savings
/_next/static/chunks/c36f3faa-bf8431af233775b3.js?dpl=dpl...	426.3 KiB	341.8 KiB
/_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4...	281.5 KiB	212.8 KiB
/_next/static/chunks/1453-51dbae4c2474dde3.js?dpl=dpl_em4...	177.1 KiB	128.3 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	167.3 KiB	97.8 KiB
/_next/static/chunks/2170a4aa-1514f5a56eef99b1.js?dpl=dpl...	109.6 KiB	88.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKZ6J9R	173.2 KiB	81.4 KiB
/_next/static/chunks/2636-1969dde127208522.js?dpl=dpl_em4...	136.0 KiB	80.8 KiB
/_next/static/chunks/7369-0f0754218170d7e9.js?dpl=dpl_em4...	109.3 KiB	52.5 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	64.2 KiB	48.2 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js	39.6 KiB	23.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/7369-0f0754218170d7e9.js?dpl=dpl_em4...	7.7 s	1.7 s	10 ms
redis.io/	1.2 s	29 ms	32 ms
Unattributable	1.1 s	79 ms	0.0 ms
cdn.amplitude.com/engagement-browser/prod/split/index.js	199 ms	188 ms	0.1 ms
/_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4...	122 ms	100 ms	19 ms
/_next/static/chunks/bf76e631-a760aa8cff633f5a.js?dpl=dpl...	101 ms	97 ms	2.8 ms
/_next/static/chunks/bf6a786c-381ced19b77084c2.js?dpl=dpl...	98 ms	84 ms	3.3 ms
www.googletagmanager.com/gtm.js?id=GTM-TKZ6J9R	88 ms	66 ms	16 ms
consent.trustarc.com/asset/notice.js/v/v1.7-8549	76 ms	48 ms	3.1 ms
/_next/static/chunks/2636-1969dde127208522.js?dpl=dpl_em4...	61 ms	51 ms	11 ms
cdn.jsdelivr.net/npm/hockeystack@latest/hockeystack.min.js	58 ms	42 ms	2.1 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	5.4 s
Script Evaluation	2.6 s
Style & Layout	1.4 s
Rendering	1.2 s
Script Parsing & Compilation	170 ms
Garbage Collection	102 ms
Parse HTML & CSS	46 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
unpkg.com/@rive-app/canvas@2.27.1/rive.wasm	488.7 KiB
/_next/static/chunks/c36f3faa-bf8431af233775b3.js?dpl=dpl...	426.6 KiB
/_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4...	282.3 KiB
redis.io/	221.2 KiB
/_next/static/chunks/1453-51dbae4c2474dde3.js?dpl=dpl_em4...	177.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKZ6J9R	173.5 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...	167.8 KiB
/_next/static/chunks/2636-1969dde127208522.js?dpl=dpl_em4...	136.2 KiB
/_next/static/chunks/2170a4aa-1514f5a56eef99b1.js?dpl=dpl...	109.9 KiB
/_next/static/chunks/7369-0f0754218170d7e9.js?dpl=dpl_em4...	109.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div.styles_container__ImQx_ > div.styles_contentWrapper__GXd4_ > div.styles_imageContainer__94pGQ > img.styles_svgImage__Hr5OU `div.styles_container__ImQx_ > div.styles_contentWrapper__GXd4_ > div.styles_imageContainer__94pGQ > img.styles_svgImage__Hr5OU`	/images/sy1jschh/production/8379f78a4082c502446af513120eb...
div.styles_container__ImQx_ > div.styles_contentWrapper__GXd4_ > div.styles_imageContainer__94pGQ > img.styles_svgImage__Hr5OU `div.styles_container__ImQx_ > div.styles_contentWrapper__GXd4_ > div.styles_imageContainer__94pGQ > img.styles_svgImage__Hr5OU`	/images/sy1jschh/production/8379f78a4082c502446af513120eb...

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

●Max Potential First Input Delay 120 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 110 ms

●Avoid large layout shifts 5 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NO YES `div.prefPanel > div > div.cookiecat > div.switch`
NO YES `div.prefPanel > div > div.cookiecat > div.switch`
NO YES `div.prefPanel > div > div.cookiecat > div.switch`

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.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.styles_container__JJpaD > ul > li.styles_buttons__60Y5z > button.styles_button__YDNft `nav.styles_container__JJpaD > ul > li.styles_buttons__60Y5z > button.styles_button__YDNft`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l `div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l`

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.

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
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
Privacy Policy `div > div.footer > div.left > a#privacyPolicyAnchor`
Powered by: `div.wrapper > div > div.footer > div.right`

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.__variable_bd0331 > div#pop-div203557732196449359 > div#pop-div3010819179435927773 > div#pop-frame029726429865171 `body.__variable_bd0331 > div#pop-div203557732196449359 > div#pop-div3010819179435927773 > div#pop-frame029726429865171`

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Think fast. Build faster. `section.style_section__Qbg1z > div.styles_container__ImQx_ > div.styles_title__PZyMD > h3.styles_text__Pngqw`
Required Cookies `div.cookiecat > div > span.gwt-InlineHTML > h3`

These are opportunities to improve keyboard navigation in your application.

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
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
NO `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
YES `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
NO `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
YES `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
NO `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
YES `div > div.cookiecat > div.switch > span.gwt-InlineHTML`

○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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA input fields have accessible names

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○`<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
/_next/static/chunks/7369-0f0754218170d7e9.js?dpl=dpl_em4... line 18, col 5800	`Amplitude Engagement Logger [Error]: User must specify at least a user_id or device_id`
cloud.redis.io/api/v1/csrf	`Failed to load resource: the server responded with a status of 401 ()`
redis.io/monitoring?o=1111372&p=4511056586473472&r=us	`Failed to load resource: the server responded with a status of 404 ()`
redis.io/monitoring?o=1111372&p=4511056586473472&r=us	`Failed to load resource: the server responded with a status of 404 ()`
redis.io/monitoring?o=1111372&p=4511056586473472&r=us	`Failed to load resource: the server responded with a status of 404 ()`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
/_next/static/chunks/c36f3faa-bf8431af233775b3.js?dpl=dpl...
/_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4...
/_next/static/chunks/1453-51dbae4c2474dde3.js?dpl=dpl_em4...
/next-integrations/actions/amplitude-plugins/f12a4347e108...	/next-integrations/actions/amplitude-plugins/f12a4347e108...
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js.map
cdn.jsdelivr.net/npm/hockeystack@latest/hockeystack.min.js	/sm/9e4aff1ede2bab9784e8c490947bf758aee81038343662c8b4444...

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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
redis.io/cloud/	Learn more
redis.io/software/	Learn more

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l `div.footer > div.left > a#privacyPolicyAnchor > img.inline-e3jf3l`

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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`