Mobile 375 × 812

Desktop 1440 × 900

Score: 84 / 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.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Lean and efficient — low environmental impact per visit.
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.
5 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Certificate expires soon (21 days remaining)
Security gaps expose your site and users to attacks, eroding trust.
Cookie '2f4d6fdc46bcd694b9e7af987293628a' has no SameSite attribute
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 piwik.proxmox.com lacks integrity attribute
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
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/467f3705-863b-4764-b766-0b8a6b2937d7)<a href="https://beavercheck.com/results/467f3705-863b-4764-b766-0b8a6b2937d7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fproxmox.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fproxmox.comThis 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 audience reach.
5 barrier(s) likely increasing bounce by ~14%.
Page loads in 2.7s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 206ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
£263 investment → £303/month returns + GBP 18,050,000 risk avoided
£263
4h · 5 findings
£303 /mo
~£3,634 / year
GBP 18,050,000
if kept compliant
£150 — in quick wins — start here for the fastest payback
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.
3.5 developer hours at £75/hr
Based on United Kingdom rates (£75/hr)
Start here for the best return on investment
£1,504,167 / month at risk
~£18,050,001 / year if left unfixed
£18,050,000
+5 more
£0.12 /mo
1888.3 MB/mo × 0.063 GBP/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 1 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.
2.41 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.71 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5 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.
2.73 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.71 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.
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.
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| proxmox.com/media/templates/site/cassiopeia/css/template.min.css?f62601 | 38.1 KiB | 35.4 KiB |
| proxmox.com/media/system/css/joomla-fontawesome.min.css?f62601 | 26.8 KiB | 26.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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| proxmox.com/media/plg_n3tcookieconsent/js/cookieconsent.js?f62601 | 17.9 KiB | 9.8 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 | |
|---|---|
Proxmox div.menu-container > div.menu-logo > a > img.logo | /images/proxmox/Proxmox_logo_standard_hex_400px.png |
Proxmox div#offcanvas-navbar387 > div.offcanvas-header > a > img.logo | /images/proxmox/Proxmox_logo_standard_hex_400px.png |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| proxmox.com/ | 752 ms |
| proxmox.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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.menu-headers > div.menu-search > div.dropdown > button.btn div.menu-headers > div.menu-search > div.dropdown > button.btn |
div.menu-headers > div.offcanvas-menu > nav > button.btn div.menu-headers > div.offcanvas-menu > nav > button.btn |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Get support div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Find a partner div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
See training courses div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Read the docs div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Read success stories div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Get involved div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Start contributing div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Proxmox Datacenter Manager 1.0 div.grid-4-col > div.box-shadow > p > a |
Proxmox Backup Server 4.1 div.grid-4-col > div.box-shadow > p > a |
Proxmox VE 9.1 available div.grid-4-col > div.box-shadow > p > a |
Proxmox Mail Gateway 9.0 div.grid-4-col > div.box-shadow > p > a |
See all news div.grid-4-col > div.box-shadow > p.mt-auto > a.button-default |
View customers div.grid-2-col > div.partner-description > p > a.button-secondary |
Contact us div.wide > div.wide-content > p > a.button-primary |
Subscribe div.grid-child > div.mod-listmonk-subscriber > form.form-validate > button.btn |
Customize settings div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
Privacy policy div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
Reject all div#cm > div#c-inr > div#c-bns > button#c-s-bn |
Accept all div#cm > div#c-inr > div#c-bns > button#c-p-bn |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
NEW: Version 9.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
NEW: Version 4.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
NEW: Version 1.0 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| proxmox.com/en/products/proxmox-virtual-environment/overview | Learn more |
| proxmox.com/en/products/proxmox-backup-server/overview | Learn more |
| proxmox.com/en/products/proxmox-datacenter-manager/overview | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Customize settings div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
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.
605 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
892 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.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
923 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.
892 ms
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.
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.
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| proxmox.com/media/templates/site/cassiopeia/css/template.min.css?f62601 | 38.1 KiB | 35.3 KiB |
| proxmox.com/media/system/css/joomla-fontawesome.min.css?f62601 | 26.8 KiB | 26.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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| proxmox.com/media/plg_n3tcookieconsent/js/cookieconsent.js?f62601 | 17.9 KiB | 9.8 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 | |
|---|---|
Proxmox div.grid-child > div.menu-logo > a > img.logo | /images/proxmox/Proxmox_logo_standard_hex_400px.png |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| proxmox.com/ | 202 ms |
| proxmox.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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.menu-headers > div.menu-search > div.dropdown > button.btn div.menu-headers > div.menu-search > div.dropdown > button.btn |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary |
Get support div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Find a partner div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
See training courses div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Read the docs div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Read success stories div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Get involved div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Start contributing div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary |
Proxmox Datacenter Manager 1.0 div.grid-4-col > div.box-shadow > p > a |
Proxmox Backup Server 4.1 div.grid-4-col > div.box-shadow > p > a |
Proxmox VE 9.1 available div.grid-4-col > div.box-shadow > p > a |
Proxmox Mail Gateway 9.0 div.grid-4-col > div.box-shadow > p > a |
See all news div.grid-4-col > div.box-shadow > p.mt-auto > a.button-default |
View customers div.grid-2-col > div.partner-description > p > a.button-secondary |
Contact us div.wide > div.wide-content > p > a.button-primary |
Subscribe div.grid-child > div.mod-listmonk-subscriber > form.form-validate > button.btn |
Customize settings div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
Privacy policy div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
Reject all div#cm > div#c-inr > div#c-bns > button#c-s-bn |
Accept all div#cm > div#c-inr > div#c-bns > button#c-p-bn |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
NEW: Version 9.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
NEW: Version 4.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
NEW: Version 1.0 div > div.grid-3-col > div.box-shadow > h5.new-version-tag |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| proxmox.com/en/products/proxmox-virtual-environment/overview | Learn more |
| proxmox.com/en/products/proxmox-backup-server/overview | Learn more |
| proxmox.com/en/products/proxmox-datacenter-manager/overview | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
Customize settings div#c-inr > div#c-inr-i > div#c-txt > a.cc-link |
To appear in search results, crawlers need access to your app.
Send Feedback