Spain · Madrid Completed: Apr 16, 2026 18:07 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 78 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
Reasonable footprint with room for optimization.
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.
'unsafe-eval' found in script source
Security gaps expose your site and users to attacks, eroding trust.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
External script from az416426.vo.msecnd.net lacks integrity attribute
Security gaps expose your site and users to attacks, eroding trust.
No Permissions-Policy header
Permissions-Policy locks down browser APIs you don't use, shrinking the attack surface.
High impact, low effort — start here.
High impact, requires investment.
Nothing in this quadrant — good news.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/a124724a-b173-442a-b5a8-fb9063f06ee4)<a href="https://beavercheck.com/results/a124724a-b173-442a-b5a8-fb9063f06ee4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fappcenter.ms" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fappcenter.msThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~27%.
Page takes 4.4s to load
+12% bounceUsers abandon at ~3s — you're 1.9s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
2 broken link(s) on the page
+3% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$225 investment → $2,673/month returns + USD 157,500 risk avoided
$225
2h · 5 findings
$2,673 /mo
~$32,082 / year
USD 157,500
if kept compliant
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
2.3 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,504 / year if left unfixed
$157,500
+2 more
$0.35 /mo
4313.2 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 2 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
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.
4.44 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.44 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.023
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.44 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.
5.02 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| appcenter.ms/styles/mwf-west-european-default.min.css | 603.0 KiB | 3.0 s |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| az416426.vo.msecnd.net/next/ai.2.min.js | 1800.0 s | 46.3 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Semilight/latest.woff2 | 96970.0 s | 28.4 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Bold/latest.woff2 | 122904.0 s | 29.6 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Semibold/latest.woff2 | 316567.0 s | 28.9 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/normal/latest.woff2 | 406397.0 s | 33.5 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-live-analytics@2x.png | 142.6 KiB | 130.3 KiB |
Screenshot of the Visual Studio App Center crash service div#crashes > div > picture.c-image > img.x-visible-inline-block | appcenter.ms/images/app-center-diagnostics@2x.png | 126.2 KiB | 121.8 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| appcenter.ms/styles/mwf-west-european-default.min.css | 600.4 KiB | 594.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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /* Utility classes */ .ac-f-pad-top-6x.ac-f-pad-top-6x { padding-top: 24px; } … | 16.6 KiB | 8.2 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
App Center div.section-padding-h > div.x-visible-flex > picture.c-image > img.x-hidden-focus | appcenter.ms/images/app-center-hero.svg |
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-analytics-graphs.svg |
Screenshot of the Visual Studio App Center crash service div#crashes > div > picture.c-image > img.x-visible-inline-block | appcenter.ms/images/app-center-diagnostics@2x.png |
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-live-analytics@2x.png |
Microsoft div#header > div.section-padding-h > div > img.c-image | appcenter.ms/images/logo-microsoft.svg |
Twitter logo li > a > picture > img | appcenter.ms/images/logo-twitter.svg |
LinkedIn logo li > a > picture > img | appcenter.ms/images/logo-linkedin.svg |
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | az416426.vo.msecnd.net/next/ai.2.min.js line 4, col 20534 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 400 () |
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.
1.14 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.51 s
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.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.26 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.
1.51 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| az416426.vo.msecnd.net/next/ai.2.min.js | 1800.0 s | 46.3 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Semilight/latest.woff2 | 96957.0 s | 28.4 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Bold/latest.woff2 | 122891.0 s | 29.6 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/Semibold/latest.woff2 | 316554.0 s | 28.9 KiB |
| c.s-microsoft.com/static/fonts/segoe-ui/west-european/normal/latest.woff2 | 406384.0 s | 33.5 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| appcenter.ms/styles/mwf-west-european-default.min.css | 603.0 KiB | 512 ms |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-live-analytics@2x.png | 142.6 KiB | 97.5 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| appcenter.ms/styles/mwf-west-european-default.min.css | 600.4 KiB | 591.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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /* Utility classes */ .ac-f-pad-top-6x.ac-f-pad-top-6x { padding-top: 24px; } … | 16.6 KiB | 8.2 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Screenshot of the Visual Studio App Center crash service div#crashes > div > picture.c-image > img.x-visible-inline-block | appcenter.ms/images/app-center-diagnostics.png |
App Center div.section-padding-h > div.x-visible-flex > picture.c-image > img.x-hidden-focus | appcenter.ms/images/app-center-hero.svg |
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-analytics-graphs.svg |
Visual Studio App Center Analytics service screenshot div.m-feature-container > section.m-feature > picture > img | appcenter.ms/images/app-center-live-analytics@2x.png |
Microsoft div#header > div.section-padding-h > div > img.c-image | appcenter.ms/images/logo-microsoft.svg |
Twitter logo li > a > picture > img | appcenter.ms/images/logo-twitter.svg |
LinkedIn logo li > a > picture > img | appcenter.ms/images/logo-linkedin.svg |
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | az416426.vo.msecnd.net/next/ai.2.min.js line 4, col 20534 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 400 () |
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