Mobile 375 × 812

Desktop 1440 × 900

Score: 84 / 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.
Cross-Origin-Embedder-Policy header is missing
Cross-Origin-Opener-Policy header is missing
HSTS max-age is too short (15552000s, should be ≥ 31536000s)
JavaScript is 982 KB — consider code splitting or lazy loading
No DMARC record found
[](https://beavercheck.com/results/a3ab8dc5-d15a-055c-5809-c84d92f450a4)<a href="https://beavercheck.com/results/a3ab8dc5-d15a-055c-5809-c84d92f450a4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.scaleway.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.scaleway.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.
3.20 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
11.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.11 s
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.
6.23 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.
11.55 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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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 | |
|---|---|---|---|
section.full-width > div.container > div.Discover-module-scss-module__Pje5IG__illustration > img section.full-width > div.container > div.Discover-module-scss-module__Pje5IG__illustration > img | www.scaleway.com/_next/static/media/superpod-illustration.0pq9khkt7g5cx.webp | 597.7 KiB | 490.4 KiB |
article.HeroCard-module-scss-module__kq7NRW__container > div.HeroCard-module-scss-module__kq7NRW__card > div.HeroCard-module-scss-module__kq7NRW__image > img article.HeroCard-module-scss-module__kq7NRW__container > div.HeroCard-module-scss-module__kq7NRW__card > div.HeroCard-module-scss-module__kq7NRW__image > img | www-uploads.scaleway.com/European_Brand_Campaign2026_Modular_Hero_882e3e2525.png | 110.1 KiB | 94.0 KiB |
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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.scaleway.com/ | 821 ms |
| www.scaleway.com/en/ | 0.0 ms |
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.
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 |
|---|---|---|
| www.scaleway.com/_next/static/chunks/0v_ock0m1q~u2.css | 20.5 KiB | 20.3 KiB |
| www.scaleway.com/_next/static/chunks/0v0rv0ir3i-69.css | 13.7 KiB | 13.2 KiB |
| www.scaleway.com/_next/static/chunks/0lly.896e7fyt.css | 12.4 KiB | 12.2 KiB |
| www.scaleway.com/_next/static/chunks/0ygty3iqkeaqq.css | 11.6 KiB | 10.5 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 |
|---|---|---|
| www.scaleway.com/_next/static/chunks/0vosegp0~e-5h.js | 190.9 KiB | 144.5 KiB |
| www.scaleway.com/_next/static/chunks/0eakoc57m6p9_.js | 130.3 KiB | 107.0 KiB |
| www.scaleway.com/_next/static/chunks/14p6u97z6tglr.js | 103.6 KiB | 103.4 KiB |
| www.scaleway.com/_next/static/chunks/0x-6o7o0.i.e2.js | 134.7 KiB | 49.5 KiB |
| www.scaleway.com/_next/static/chunks/0h7kkxfcsy964.js | 95.4 KiB | 43.0 KiB |
| www.scaleway.com/_next/static/chunks/0apocp0s~0iy3.js | 103.5 KiB | 42.3 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 |
|---|---|---|---|
| www.scaleway.com/_next/static/chunks/0x-6o7o0.i.e2.js | 1.3 s | 1.0 s | 59 ms |
| www.scaleway.com/_next/static/chunks/turbopack-0-_rp4p6-wb18.js | 1.2 s | 924 ms | 1.6 ms |
| www.scaleway.com/en/ | 739 ms | 6.5 ms | 0.7 ms |
| Unattributable | 553 ms | 67 ms | 0.0 ms |
| www.scaleway.com/_next/static/chunks/turbopack-087~v1rr2-abx.js | 366 ms | 363 ms | 2.3 ms |
| www.scaleway.com/_next/static/chunks/0apocp0s~0iy3.js | 142 ms | 80 ms | 59 ms |
| www.scaleway.com/_next/static/chunks/0vosegp0~e-5h.js | 73 ms | 2.0 ms | 70 ms |
| www.scaleway.com/_next/static/chunks/14p6u97z6tglr.js | 51 ms | 1.1 ms | 49 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.5 s |
| Other | 1.0 s |
| Style & Layout | 491 ms |
| Script Parsing & Compilation | 430 ms |
| Rendering | 167 ms |
| Parse HTML & CSS | 86 ms |
| Garbage Collection | 41 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 |
| 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.
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 dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
| Failing Elements |
|---|
Cookie time!
Scaleway uses cookies (or similar technologies) that are necessar… div.inter_724de5d0-module__j-XtIa__variable > div#portal > div._container_2gf4i_1 > aside.undefined |
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.
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 |
|---|---|
| www.scaleway.com/en/bare-metal/ | See more |
| www.scaleway.com/en/virtual-instances/ | See more |
| www.scaleway.com/en/vpc/ | See more |
| www.scaleway.com/en/cloud-storage-solutions/ | See more |
| www.scaleway.com/en/containers/ | See more |
| www.scaleway.com/en/gpu-instances/ | See more |
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.
646 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.19 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
96 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.
1.42 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.
2.29 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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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 | |
|---|---|---|---|
section.full-width > div.container > div.Discover-module-scss-module__Pje5IG__illustration > img section.full-width > div.container > div.Discover-module-scss-module__Pje5IG__illustration > img | www.scaleway.com/_next/static/media/superpod-illustration.0pq9khkt7g5cx.webp | 597.7 KiB | 442.6 KiB |
main#main > section#products > div.Products-module-scss-module__qGBTCG__background > img main#main > section#products > div.Products-module-scss-module__qGBTCG__background > img | www.scaleway.com/_next/static/media/hp-product-illustration.0r4j_x-44kz4f.webp | 230.7 KiB | 146.5 KiB |
article.HeroCard-module-scss-module__kq7NRW__container > div.HeroCard-module-scss-module__kq7NRW__card > div.HeroCard-module-scss-module__kq7NRW__image > img article.HeroCard-module-scss-module__kq7NRW__container > div.HeroCard-module-scss-module__kq7NRW__card > div.HeroCard-module-scss-module__kq7NRW__image > img | www-uploads.scaleway.com/European_Brand_Campaign2026_Modular_Hero_882e3e2525.png | 110.1 KiB | 101.6 KiB |
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 |
|---|---|---|
| www.scaleway.com/_next/static/chunks/0v_ock0m1q~u2.css | 20.5 KiB | 20.3 KiB |
| www.scaleway.com/_next/static/chunks/0v0rv0ir3i-69.css | 13.7 KiB | 13.2 KiB |
| www.scaleway.com/_next/static/chunks/0lly.896e7fyt.css | 12.4 KiB | 12.0 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 |
|---|---|---|
| www.scaleway.com/_next/static/chunks/0vosegp0~e-5h.js | 190.9 KiB | 144.5 KiB |
| www.scaleway.com/_next/static/chunks/0eakoc57m6p9_.js | 130.3 KiB | 107.0 KiB |
| www.scaleway.com/_next/static/chunks/14p6u97z6tglr.js | 103.6 KiB | 103.4 KiB |
| www.scaleway.com/_next/static/chunks/0x-6o7o0.i.e2.js | 134.7 KiB | 47.3 KiB |
| www.scaleway.com/_next/static/chunks/0h7kkxfcsy964.js | 95.4 KiB | 43.0 KiB |
| www.scaleway.com/_next/static/chunks/0apocp0s~0iy3.js | 103.5 KiB | 42.3 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 |
| 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.scaleway.com/ | 246 ms |
| www.scaleway.com/en/ | 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.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
| Failing Elements |
|---|
Cookie time!
Scaleway uses cookies (or similar technologies) that are necessar… div.inter_724de5d0-module__j-XtIa__variable > div#portal > div._container_2gf4i_1 > aside.undefined |
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.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
| Failing Elements |
|---|
FRANÇAIS
FR nav.Header-module-scss-module__tB8mKq__topBarNavigation > ul.Header-module-scss-module__tB8mKq__language > li > a |
ITALIANO
IT nav.Header-module-scss-module__tB8mKq__topBarNavigation > ul.Header-module-scss-module__tB8mKq__language > li > a |
These items highlight common accessibility best practices.
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 |
|---|---|
| www.scaleway.com/en/bare-metal/ | See more |
| www.scaleway.com/en/virtual-instances/ | See more |
| www.scaleway.com/en/vpc/ | See more |
| www.scaleway.com/en/cloud-storage-solutions/ | See more |
| www.scaleway.com/en/containers/ | See more |
| www.scaleway.com/en/gpu-instances/ | See more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback