Skip to content
Audit Complete

Results for https://www.wasabi.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:30 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)
C73

Site Health

Score: 73 / 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

No Content-Security-Policy header found

Security › Content Security Policy
3

9 link(s) with no accessible text

Accessibility › Link & Button Quality
4

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers
5

Cross-Origin-Opener-Policy header is missing

Security › Security Headers
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wasabi.com)](https://beavercheck.com/results/6e55ebd5-c784-7cd7-c2a2-dabc36f5498e)
<a href="https://beavercheck.com/results/6e55ebd5-c784-7cd7-c2a2-dabc36f5498e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wasabi.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wasabi.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.

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
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.

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

3.12 s

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

15.82 s

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

1.74 s

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

0.078

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

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

19.74 s

Detailed Report

Audit breakdown by category with detailed findings.

36

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.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-DIV
nodeLabel: Your Critical AI Data Just Got a Security Upgrade Introducing Covert Copy. It’…
path: 1,HTML,1,BODY,0,DIV,3,MAIN,1,DIV,0,DIV,0,DIV
selector: main#main-content > div.MuiBox-root > div.MuiBox-root > div.MuiBox-root
snippet: <div class="MuiBox-root css-1o0pkg0">

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

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
div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root
a-us.storyblok.com/f/1019449/546x547/c7c523aba0/ibm-thumbnail.jpg122.7 KiB74.1 KiB
Total cost of ownership vs Amazon S3 div.MuiBox-root > div.imageAssetContainerContained > div.MuiBox-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...30.9 KiB19.4 KiB
Dell Technologies div.MuiBox-root > div.MuiBox-root > a.MuiTypography-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...11.8 KiB6.0 KiB
Arctera div.MuiBox-root > div.MuiBox-root > a.MuiTypography-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...6.2 KiB4.6 KiB
Hanwa div.MuiBox-root > div.MuiBox-root > a.MuiTypography-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...7.2 KiB4.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: 857 ms
URLTime Spent
www.wasabi.com/857 ms
wasabi.com/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.

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 2.6 s 653.4 KiB
URLTransfer SizeEst Savings
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js551.1 KiB223.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW180.0 KiB76.1 KiB
www.googletagmanager.com/gtag/destination?id=G-JE5RX701S0&cx=c&gtm=4e6460178.0 KiB69.2 KiB
www.googletagmanager.com/gtag/js?id=AW-11367212055&cx=c&gtm=4e6460143.8 KiB62.0 KiB
www.googletagmanager.com/gtag/js?id=AW-853928254&cx=c&gtm=4e6460143.9 KiB60.6 KiB
www.googletagmanager.com/gtag/js?id=DC-8316818&cx=c&gtm=4e6460128.8 KiB60.0 KiB
www.googletagmanager.com/gtag/js?id=DC-9955201&cx=c&gtm=4e6460130.8 KiB59.8 KiB
cdn.optimizely.com/js/5552864383205376.js95.6 KiB42.5 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
wasabi.com/_next/static/chunks/framework-63d16ff2f5e08230.js1.2 s1.0 s10 ms
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js1.1 s551 ms184 ms
Unattributable549 ms21 ms0.0 ms
wasabi.com/543 ms9.4 ms0.4 ms
www.googletagmanager.com/gtag/destination?id=G-JE5RX701S0&cx=c&gtm=4e6460369 ms316 ms50 ms
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW306 ms236 ms59 ms
cdn.optimizely.com/js/5552864383205376.js300 ms269 ms25 ms
www.googletagmanager.com/gtag/js?id=AW-853928254&cx=c&gtm=4e6460186 ms155 ms30 ms
www.googletagmanager.com/gtag/js?id=AW-11367212055&cx=c&gtm=4e6460163 ms133 ms30 ms
www.googletagmanager.com/gtag/js?id=DC-9955201&cx=c&gtm=4e6460160 ms132 ms25 ms
www.googletagmanager.com/gtag/js?id=DC-8316818&cx=c&gtm=4e6460138 ms106 ms31 ms
wasabi.com/_next/static/chunks/main-b4f2ad0abb682109.js89 ms78 ms8.5 ms
www.redditstatic.com/ads/pixel.js?pixel_id=a2_imm0637pkse250 ms40 ms6.4 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 Evaluation3.1 s
Other756 ms
Style & Layout540 ms
Script Parsing & Compilation466 ms
Rendering149 ms
Garbage Collection116 ms
Parse HTML & CSS60 ms

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

URLTransfer Size
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js551.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW180.4 KiB
www.googletagmanager.com/gtag/destination?id=G-JE5RX701S0&cx=c&gtm=4e6460178.4 KiB
www.googletagmanager.com/gtag/js?id=AW-853928254&cx=c&gtm=4e6460143.9 KiB
www.googletagmanager.com/gtag/js?id=AW-11367212055&cx=c&gtm=4e6460143.8 KiB
www.googletagmanager.com/gtag/js?id=DC-9955201&cx=c&gtm=4e6460130.9 KiB
www.googletagmanager.com/gtag/js?id=DC-8316818&cx=c&gtm=4e6460128.8 KiB
a-us.storyblok.com/f/1019449/546x547/c7c523aba0/ibm-thumbnail.jpg123.3 KiB
a-us.storyblok.com/f/1019449/1861x696/00a1486302/fire-hero-bg.jpg120.4 KiB
a-us.storyblok.com/f/1019449/667x667/03c707019e/bruins-td-cover.jpg117.8 KiB

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
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 19 user timings
●Avoid long main-thread tasks 13 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 240 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 80 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
95

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
Keep your GPUs fed with Fire div.MuiBox-root > h5 > span.MuiTypography-root > b

These are opportunities to improve the legibility of your content.

Navigation

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
Introducing Covert Copy. It’s not just immutable. It’s Invisible. div.MuiBox-root > div.MuiBox-root > div.MuiBox-root > h3
Keep your GPUs fed with Fire div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root > h5

These are opportunities to improve keyboard navigation in your application.

○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
●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
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○Elements with visible text labels have matching accessible names.
○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.googletagmanager.com/gtm.js?id=GTM-PLB3PMW line 251, col 503
Uncaught [object Object]
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW line 251, col 503
Uncaught [object Object]

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.

URL
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js
●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
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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

83
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
91
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.

750 ms

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

1.43 s

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

285 ms

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

0.040

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

1.35 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.78 s

Detailed Report

Audit breakdown by category with detailed findings.

83

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.

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.

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:21.34 source:map[column:1.5873e+06 line:1 type:source-location url:https://wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js 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:13.96 source:map[column:1.499375e+06 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js urlProvider:network]] map[reflowTime:4.244 source:map[column:1.545328e+06 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js urlProvider:network]] map[reflowTime:1.017 source:map[column:1.133544e+06 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js urlProvider:network]] map[reflowTime:23.562 source:map[column:1.53872e+06 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js urlProvider:network]] map[reflowTime:0.791 source:map[column:2770 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/386-cbb407929264539f.js urlProvider:network]] map[reflowTime:0.175 source:map[column:3075 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/386-cbb407929264539f.js urlProvider:network]] map[reflowTime:0.178 source:map[column:3092 line:0 type:source-location url:https://wasabi.com/_next/static/chunks/386-cbb407929264539f.js urlProvider:network]] map[reflowTime:1.416 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-DIV
nodeLabel: Your Critical AI Data Just Got a Security Upgrade Introducing Covert Copy. It’…
path: 1,HTML,1,BODY,0,DIV,5,MAIN,1,DIV,0,DIV,0,DIV
selector: main#main-content > div.MuiBox-root > div.MuiBox-root > div.MuiBox-root
snippet: <div class="MuiBox-root css-1o0pkg0">

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

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
div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root
a-us.storyblok.com/f/1019449/546x547/c7c523aba0/ibm-thumbnail.jpg122.7 KiB74.1 KiB
Floating bubbles div.MuiBox-root > div.imageAssetContainerContained > div.MuiBox-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...55.7 KiB36.6 KiB
CSI Report div.MuiGrid-root > div.MuiStack-root > div.MuiBox-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...32.7 KiB21.8 KiB
Total cost of ownership vs Amazon S3 div.MuiBox-root > div.imageAssetContainerContained > div.MuiBox-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...30.9 KiB20.6 KiB
div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root div.MuiBox-root > div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root
a-us.storyblok.com/f/1019449/420x420/23c88a08ba/dell-cover.jpg38.7 KiB10.0 KiB
Arctera div.MuiBox-root > div.MuiBox-root > a.MuiTypography-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...6.2 KiB4.6 KiB
Hanwa div.MuiBox-root > div.MuiBox-root > a.MuiTypography-root > img
/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1...7.2 KiB4.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: 310 ms
URLTime Spent
www.wasabi.com/310 ms
wasabi.com/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.

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 60 ms 653.6 KiB
URLTransfer SizeEst Savings
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js550.9 KiB224.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW180.0 KiB76.1 KiB
www.googletagmanager.com/gtag/destination?id=G-JE5RX701S0&cx=c&gtm=4e6461h2178.0 KiB69.2 KiB
www.googletagmanager.com/gtag/js?id=DC-8316818&cx=c&gtm=4e6461h2128.8 KiB60.8 KiB
www.googletagmanager.com/gtag/js?id=AW-853928254&cx=c&gtm=4e6461h2143.9 KiB60.7 KiB
www.googletagmanager.com/gtag/js?id=DC-9955201&cx=c&gtm=4e6461h2130.8 KiB59.8 KiB
www.googletagmanager.com/gtag/js?id=AW-11367212055&cx=c&gtm=4e6461h2143.8 KiB59.7 KiB
cdn.optimizely.com/js/5552864383205376.js95.6 KiB42.5 KiB

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.0 s
Other503 ms
Style & Layout195 ms
Script Parsing & Compilation143 ms
Rendering120 ms
Garbage Collection35 ms
Parse HTML & CSS16 ms

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

URLTransfer Size
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js551.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW180.4 KiB
www.googletagmanager.com/gtag/destination?id=G-JE5RX701S0&cx=c&gtm=4e6461h2178.4 KiB
www.googletagmanager.com/gtag/js?id=AW-853928254&cx=c&gtm=4e6461h2143.9 KiB
www.googletagmanager.com/gtag/js?id=AW-11367212055&cx=c&gtm=4e6461h2143.8 KiB
www.googletagmanager.com/gtag/js?id=DC-9955201&cx=c&gtm=4e6461h2130.9 KiB
www.googletagmanager.com/gtag/js?id=DC-8316818&cx=c&gtm=4e6461h2128.8 KiB
a-us.storyblok.com/f/1019449/546x547/c7c523aba0/ibm-thumbnail.jpg123.3 KiB
a-us.storyblok.com/f/1019449/1861x696/00a1486302/fire-hero-bg.jpg120.4 KiB
a-us.storyblok.com/f/1019449/667x667/03c707019e/bruins-td-cover.jpg117.8 KiB

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
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 195 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 7 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 120 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 60 ms
●Avoid large layout shifts 7 layout shifts found
○INP breakdown
91

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
WASABI PARTNER NETWORK Managed Service Providers Resellers System Integrators … div.MuiBox-root > div.MuiContainer-root > div.MuiBox-root > div#sub-e9eac9e4-ca7b-4ecc-b318-432a83fb2921
RESOURCES Blog Wasabi TV Case Studies Analyst Reports One Pagers Data Sheets S… div.MuiBox-root > div.MuiContainer-root > div.MuiBox-root > div#sub-ac140e5f-abd9-4875-ac3d-acb5f991cd50

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
Keep your GPUs fed with Fire div.MuiBox-root > h5 > span.MuiTypography-root > b

These are opportunities to improve the legibility of your content.

Navigation

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
Introducing Covert Copy. It’s not just immutable. It’s Invisible. div.MuiBox-root > div.MuiBox-root > div.MuiBox-root > h3
Keep your GPUs fed with Fire div.MuiGrid-root > div.MuiGrid-root > div.MuiBox-root > h5

These are opportunities to improve keyboard navigation in your application.

○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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
/_next/data/L0-fa6tjP-sJVKILMqjPU/en/resources.json?refin...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/L0-fa6tjP-sJVKILMqjPU/en/resources.json?refin...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/L0-fa6tjP-sJVKILMqjPU/en/resources.json?refin...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/L0-fa6tjP-sJVKILMqjPU/en/resources.json?refin...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/L0-fa6tjP-sJVKILMqjPU/en/resources.json?refin...
Failed to load resource: the server responded with a status of 403 ()
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW line 251, col 503
Uncaught [object Object]
www.googletagmanager.com/gtm.js?id=GTM-PLB3PMW line 251, col 503
Uncaught [object Object]

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.

URL
wasabi.com/_next/static/chunks/pages/_app-8d0f6b178c065ffd.js
●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
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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback