Spain · Madrid Completed: Apr 7, 2026 20:21 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 75 / 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
HSTS header is missing
No Content-Security-Policy header found
No favicon or icon links detected
Cross-Origin-Embedder-Policy header is missing
[](https://beavercheck.com/results/f7e9d5f9-638c-e4cb-f852-2652ec9e3891)<a href="https://beavercheck.com/results/f7e9d5f9-638c-e4cb-f852-2652ec9e3891"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adidas.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adidas.comThis 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.
2.66 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.41 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
37 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.017
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.66 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.
3.41 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.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.adidas.com/WAFfailoverassets/style.css | 0.0 ms | 1.2 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.
| URL | Transfer Size |
|---|---|
| www.adidas.com/WAFfailoverassets/style.css | 1.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 |
|---|---|---|
| www.adidas.com/K5LhMx/Dm6/-8_/2jlatA/VuaYkp3wED3rYVaabi/dzojDwE/YUYi/IBYTKUEB | 169.7 KiB | 36.3 KiB |
| /K5LhMx/Dm6/-8_/2jlatA/k8aYkp3wED3r/BS8rDwE/XCU6/Ez4LaFxt... | 161.7 KiB | 33.4 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 |
|---|---|---|---|
| /K5LhMx/Dm6/-8_/2jlatA/k8aYkp3wED3r/BS8rDwE/XCU6/Ez4LaFxt... | 1.3 s | 1.2 s | 51 ms |
| www.adidas.com/K5LhMx/Dm6/-8_/2jlatA/VuaYkp3wED3rYVaabi/dzojDwE/YUYi/IBYTKUEB | 961 ms | 768 ms | 46 ms |
| Unattributable | 383 ms | 162 ms | 0.0 ms |
| www.adidas.com/ | 154 ms | 38 ms | 2.9 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 |
|---|---|
| Script Evaluation | 2.1 s |
| Other | 362 ms |
| Style & Layout | 104 ms |
| Script Parsing & Compilation | 100 ms |
| Garbage Collection | 63 ms |
| Parse HTML & CSS | 8.9 ms |
| Rendering | 5.5 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Only pages with a status code of 2XX can be cached. | Not actionable |
| 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 |
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.
| URL | Time Spent |
|---|---|
| www.adidas.com/ | 2.8 s |
| www.adidas.com/ | 0.0 ms |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
HTTP 403 - Forbidden body > main.content-wrapper > small.error |
These are opportunities to improve the legibility of your content.
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 |
|---|
What could have caused this? main.content-wrapper > div.columns > section.column > h3 |
These are opportunities to improve keyboard navigation in your application.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
To appear in search results, crawlers need access to your app.
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.
643 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
763 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
643 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
763 ms
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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.adidas.com/WAFfailoverassets/style.css | 0.0 ms | 1.2 KiB |
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
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.
| URL | Transfer Size |
|---|---|
| www.adidas.com/WAFfailoverassets/style.css | 1.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 |
|---|---|---|
| www.adidas.com/K5LhMx/Dm6/-8_/2jlatA/VuaYkp3wED3rYVaabi/dzojDwE/YUYi/IBYTKUEB | 169.6 KiB | 36.3 KiB |
| /K5LhMx/Dm6/-8_/2jlatA/k8aYkp3wED3r/BS8rDwE/XCU6/Ez4LaFxt... | 161.6 KiB | 33.4 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Only pages with a status code of 2XX can be cached. | Not actionable |
| 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 |
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.
| URL | Time Spent |
|---|---|
| www.adidas.com/ | 643 ms |
| www.adidas.com/ | 0.0 ms |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
HTTP 403 - Forbidden body > main.content-wrapper > small.error |
These are opportunities to improve the legibility of your content.
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 |
|---|
What could have caused this? main.content-wrapper > div.columns > section.column > h3 |
These are opportunities to improve keyboard navigation in your application.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
To appear in search results, crawlers need access to your app.
Send Feedback