Mobile 375 × 812

Desktop 1440 × 900

Score: 76 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
No Content-Security-Policy header found
3 link(s) with no accessible text
189 HTTP requests — consider bundling or reducing
Cross-Origin-Embedder-Policy header is missing
[](https://beavercheck.com/results/5d71d5eb-1e3d-a2e9-c064-8adbbf098712)<a href="https://beavercheck.com/results/5d71d5eb-1e3d-a2e9-c064-8adbbf098712"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.redis.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.redis.ioThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
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.
6.77 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.61 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.62 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.300
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
8.39 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.
24.69 s
Audit breakdown by category with detailed findings.
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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| 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.
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.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.redis.io/ | 806 ms |
| redis.io/ | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
| Element | Layout shift score |
|---|---|
Required Cookies
These cookies are necessary to enable the basic features of th… div > div.mainContent > div.gdpr > div.prefPanel | 0.169 |
Functional Cookies
These cookies allow us to analyze your use of the site to ev… div.mainContent > div.gdpr > div.prefPanel > div | 0.078 |
Required Cookies
These cookies are necessary to enable the basic features of th… div > div.mainContent > div.gdpr > div.prefPanel | 0.019 |
Privacy Policy
Powered by:
div.wrapper > div > div.footer | 0.018 |
Think fast. Build faster.
Redis for AI
We’re the fast memory layer for chatbot… body.__variable_bd0331 > main > section.style_section__Qbg1z | 0.012 |
Performance Cookies
These cookies allow us to count visits and traffic sources … div.mainContent > div.gdpr > div.prefPanel > div | 0.004 |
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.
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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /_next/static/css/a7bcc090cd00e64d.css?dpl=dpl_em4Txm4spq... | 19.9 KiB | 19.4 KiB |
| /_next/static/css/38b43148ef4cd4ee.css?dpl=dpl_em4Txm4spq... | 19.4 KiB | 18.6 KiB |
| /_next/static/css/783c2e38c0c8b2d8.css?dpl=dpl_em4Txm4spq... | 18.7 KiB | 16.5 KiB |
| /_next/static/css/39aa05b323db7ec8.css?dpl=dpl_em4Txm4spq... | 18.7 KiB | 16.2 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.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /_next/static/chunks/c36f3faa-bf8431af233775b3.js?dpl=dpl... | 426.3 KiB | 341.9 KiB |
| /_next/static/chunks/9146-646ea7851ff0b9e9.js?dpl=dpl_em4... | 281.5 KiB | 212.9 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.9 KiB |
| /_next/static/chunks/2170a4aa-1514f5a56eef99b1.js?dpl=dpl... | 109.6 KiB | 88.5 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.1 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.2 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.
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
| Category | Time Spent |
|---|---|
| Other | 8.2 s |
| Script Evaluation | 6.8 s |
| Style & Layout | 4.0 s |
| Rendering | 1.4 s |
| Script Parsing & Compilation | 580 ms |
| Garbage Collection | 283 ms |
| Parse HTML & CSS | 172 ms |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
| 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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| 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.
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.
| Failing Elements |
|---|
body.__variable_bd0331 > div#pop-div2010163364667647778 > div#pop-div308754556499126427 > div#pop-frame000344789200141582 body.__variable_bd0331 > div#pop-div2010163364667647778 > div#pop-div308754556499126427 > div#pop-frame000344789200141582 |
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.
| 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.
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.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.
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 |
|---|
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 |
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
| 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 |
Failed to load resource: the server responded with a status of 401 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
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.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| 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.
| 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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
886 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.45 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
193 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.091
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.73 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.
4.56 s
Audit breakdown by category with detailed findings.
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.
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.
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| 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.
| 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.
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.
| 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.
| 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.
| 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
| 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.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| 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.
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
| 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.
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.
| 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.
| 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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| 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.
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.
| 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.
| 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.
| 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 |
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
| 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 |
Failed to load resource: the server responded with a status of 401 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
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.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| 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.
| 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.
Send Feedback