Spain · Madrid Completed: Apr 7, 2026 20:34 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.
Page weighs 14.1 MB (8.4 MB transferred)
3 control(s) without accessible label
5 button(s) with no accessible text
141 HTTP requests — consider bundling or reducing
Cross-Origin-Embedder-Policy header is missing
[](https://beavercheck.com/results/03fd05c9-af88-1771-b294-cfa89cd3286a)<a href="https://beavercheck.com/results/03fd05c9-af88-1771-b294-cfa89cd3286a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sanity.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.sanity.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.
1.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.71 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4.53 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.138
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.80 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.
20.28 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.
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 | |
|---|---|---|---|
main#main > section#mirror-how-your-content-operations-team-works > section.relative > img.absolute main#main > section#mirror-how-your-content-operations-team-works > section.relative > img.absolute | /images/3do82whm/next/76f27ca1c25673432844fee3406f693bfd5... | 160.7 KiB | 83.8 KiB |
section.flex > div.grid-new-vars > div.relative > img.absolute section.flex > div.grid-new-vars > div.relative > img.absolute | /images/3do82whm/next/5306c1d623c7fa616697ddfa0644c8bfb3e... | 150.0 KiB | 40.7 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.
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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.gstatic.com/eureka/clank/146/cast_sender.js | 86400.0 s | 13.4 KiB |
| /mcg01upIV2FaAzJuGBGdZAO01ZjPPoSk01JV01aemgWEyvU/thumbnai... | 604800.0 s | 9.5 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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 |
|---|---|
Structure powers intelligence
The back-end built for AI content operations. Po… body > div.flex > main#main | 0.138 |
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/chunks/0rdqygsn7u67v.css?dpl=dpl_7XhRSfxibp... | 15.7 KiB | 14.7 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.
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/0uz1gb6x4i~gy.js?dpl=dpl_7XhRSfxibpa... | 10.3 s | 7.6 s | 46 ms |
| www.sanity.io/ | 1.9 s | 36 ms | 74 ms |
| Unattributable | 1.0 s | 45 ms | 0.0 ms |
| /_next/static/chunks/167ci08t2mfto.js?dpl=dpl_7XhRSfxibpa... | 867 ms | 461 ms | 110 ms |
| cmp.osano.com/16CLWDTCcnYWI2HHP/e53d2bde-32d5-45a1-ab1a-16b98951bfe3/osano.js | 850 ms | 717 ms | 94 ms |
| www.googletagmanager.com/gtm.js?id=GTM-N3ZSHCP | 325 ms | 262 ms | 59 ms |
| www.googletagmanager.com/gtag/destination?id=AW-16634576538&cx=c>m=4e6461h2 | 310 ms | 219 ms | 38 ms |
| www.googletagmanager.com/gtag/js?id=G-K7J41TW619&cx=c>m=4e6461h2 | 245 ms | 191 ms | 46 ms |
| /_next/static/chunks/0sqt.ygt3kqko.js?dpl=dpl_7XhRSfxibpa... | 51 ms | 0.9 ms | 50 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 | 9.6 s |
| Other | 2.8 s |
| Style & Layout | 1.9 s |
| Script Parsing & Compilation | 831 ms |
| Rendering | 657 ms |
| Parse HTML & CSS | 355 ms |
| Garbage Collection | 216 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.
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 |
|---|
header.Navbar-module__QBEfrG__header > nav.relative > div.Navbar-module__QBEfrG__rightMenu > button._button_z6aw1_3 header.Navbar-module__QBEfrG__header > nav.relative > div.Navbar-module__QBEfrG__rightMenu > button._button_z6aw1_3 |
div.relative > div.relative > div.absolute > button.flex div.relative > div.relative > div.absolute > button.flex |
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.
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.
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.
447 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.65 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
754 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.048
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.90 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.95 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 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.flex > div.grid-new-vars > div.relative > img.absolute section.flex > div.grid-new-vars > div.relative > img.absolute | /images/3do82whm/next/5306c1d623c7fa616697ddfa0644c8bfb3e... | 150.0 KiB | 52.4 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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.gstatic.com/eureka/clank/146/cast_sender.js | 86400.0 s | 13.4 KiB |
| /mcg01upIV2FaAzJuGBGdZAO01ZjPPoSk01JV01aemgWEyvU/thumbnai... | 604800.0 s | 9.5 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.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
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/0uz1gb6x4i~gy.js?dpl=dpl_7XhRSfxibpa... | 2.9 s | 2.2 s | 12 ms |
| www.sanity.io/ | 432 ms | 19 ms | 25 ms |
| Unattributable | 311 ms | 13 ms | 0.0 ms |
| /_next/static/chunks/167ci08t2mfto.js?dpl=dpl_7XhRSfxibpa... | 303 ms | 164 ms | 26 ms |
| cmp.osano.com/16CLWDTCcnYWI2HHP/e53d2bde-32d5-45a1-ab1a-16b98951bfe3/osano.js | 235 ms | 200 ms | 27 ms |
| www.googletagmanager.com/gtm.js?id=GTM-N3ZSHCP | 138 ms | 99 ms | 16 ms |
| www.googletagmanager.com/gtag/destination?id=AW-16634576538&cx=c>m=4e6460 | 72 ms | 61 ms | 10 ms |
| www.googletagmanager.com/gtag/js?id=G-K7J41TW619&cx=c>m=4e6460 | 65 ms | 52 ms | 11 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.8 s |
| Other | 762 ms |
| Style & Layout | 451 ms |
| Script Parsing & Compilation | 215 ms |
| Rendering | 146 ms |
| Parse HTML & CSS | 113 ms |
| Garbage Collection | 62 ms |
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/chunks/0rdqygsn7u67v.css?dpl=dpl_7XhRSfxibp... | 15.7 KiB | 14.7 KiB |
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.
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 |
|---|
div.relative > div.relative > div.absolute > button.flex div.relative > div.relative > div.absolute > button.flex |
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.
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.
Send Feedback