Spain · Madrid Completed: Apr 21, 2026 20:58 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 74 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
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.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cookie 'served' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
13 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
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/a6977124-b5e3-4616-a2da-0ac06d9e8205)<a href="https://beavercheck.com/results/a6977124-b5e3-4616-a2da-0ac06d9e8205"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhaproxy.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fhaproxy.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~12%.
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
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, …)
14 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
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.
€280 investment → €0.02/month returns + EUR 20,500,000 risk avoided
€280
4h · 5 findings
€0.02 /mo
~€0.21 / year
EUR 20,500,000
if kept compliant
€160 — 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 €80/hr
Based on France rates (€80/hr)
Start here for the best return on investment
€1,708,333 / month at risk
~€20,500,000 / year if left unfixed
€20,500,000
+4 more
€0.02 /mo
239.5 MB/mo × 0.074 EUR/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 5 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.
1.82 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.03 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.82 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.03 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 |
|---|---|---|
| www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 0.0 ms | 14.9 KiB |
| www.haproxy.org/img/Ad_4.png | 0.0 ms | 13.6 KiB |
| www.haproxy.org/img/Ad_1.png | 0.0 ms | 10.2 KiB |
| www.haproxy.org/img/Ad_2.png | 0.0 ms | 8.2 KiB |
| www.haproxy.org/img/btn_donate_SM_eur.gif | 0.0 ms | 1.7 KiB |
| www.haproxy.org/img/btn_donate_SM_usd.gif | 0.0 ms | 1.7 KiB |
| www.haproxy.org/size.css?412x823 | 0.0 ms | 255 B |
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.
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.
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 | |
|---|---|---|---|
tbody > tr > td > img tbody > tr > td > img | www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 14.7 KiB | 12.3 KiB |
center > p > a > img center > p > a > img | www.haproxy.org/img/Ad_4.png | 13.4 KiB | 9.2 KiB |
center > p > a > img center > p > a > img | www.haproxy.org/img/Ad_1.png | 10.0 KiB | 5.9 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.
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.
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 |
|---|---|
| haproxy.org/ | 806 ms |
| www.haproxy.org/ | 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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
IPv4 tbody > tr > td > span.netw |
Your computer is not IPv6-ready tbody > tr > td > span.v6warn |
HAProxy 3.3.0 release td > p > b > font |
HAProxy 3.2.0 release td > p > b > font |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr > td > img tbody > tr > td > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
td > center > p > a td > center > p > a |
td > center > p > a td > center > p > a |
td > center > p > a td > center > p > a |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Two vulnerabilities affecting some deep parts of the QUIC parsing were reported… tbody > tr > td > ul |
It's no news that many users have been hit by the massive performance cost caus… tbody > tr > td > ul |
This stable release as usual introduces significant advancements in performance… tbody > tr > td > ul |
This LTS release improves in a lot of areas. First, many improvements were made… tbody > tr > td > ul |
contact HAProxy Technologies to hire some professional services or subscribe a … tbody > tr > td > ol |
mailing-list : haproxy@formilux.org
Read the list archives on mail-archive
Read… tbody > tr > td > ul |
irc://irc.libera.chat/%23haproxy tbody > tr > td > ul |
https://slack.haproxy.org/ tbody > tr > td > ul |
These are opportunities to improve the experience of reading tabular or list data using 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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Quick News tbody > tr > td > a |
Recent News tbody > tr > td > a |
Description tbody > tr > td > a |
Performance tbody > tr > td > a |
Reliability tbody > tr > td > a |
Security tbody > tr > td > a |
Documentation tbody > tr > td > a |
Project on GitHub tbody > tr > td > a |
Download sources / doc tbody > tr > td > a |
Packages / Images / Distros tbody > tr > td > a |
Live demo tbody > tr > td > a |
They use it! tbody > tr > td > a |
Enterprise Features tbody > tr > td > a |
Third party extensions tbody > tr > td > a |
Commercial Support tbody > tr > td > a |
Contacts tbody > tr > td > a |
External links tbody > tr > td > a |
Discussions tbody > tr > td > a |
Slack channel tbody > tr > td > a |
Mailing list tbody > tr > td > a |
Coding style tbody > tr > td > a |
Open Issues tbody > tr > td > a |
Known bugs tbody > tr > td > a |
Signing keys tbody > tr > td > a |
HATop: Ncurses Interface tbody > tr > td > a |
Herald: load feedback agent tbody > tr > td > a |
haproxystats: stats collection tbody > tr > td > a |
Alpine-based Docker images tbody > tr > td > a |
Debian-based Docker images tbody > tr > td > a |
RHEL-based Docker images tbody > tr > td > a |
Debian/Ubuntu packages tbody > tr > td > a |
Performance packages tbody > tr > td > a |
3.4-dev tbody > tr > td > a |
3.4-dev9 tbody > tr > td > a |
2026-04-15 tbody > tr > td > a |
3.3 tbody > tr > td > a |
3.3.6 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
3.2 tbody > tr > td > a |
3.2.15 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
3.0 tbody > tr > td > a |
3.0.19 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
2.8 tbody > tr > td > a |
2.8.20 tbody > tr > td > a |
2026-03-20 tbody > tr > td > a |
2.6 tbody > tr > td > a |
2.6.25 tbody > tr > td > a |
2026-03-20 tbody > tr > td > a |
2.4 tbody > tr > td > a |
2.4.31 tbody > tr > td > a |
2026-03-09 tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Branch Release date End of life Latest version Changelog Links
3.4-dev ~2026-Q2… td > a > p > table |
dev 3.3 3.2 3.1 3.0 2.9 2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.9 1.8 1.7 1.6 1.… td > a > p > table |
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
tbody > tr > td > img tbody > tr > td > img | www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 83 x 60 (1.38) | 254 x 60 (4.23) |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
tr > td > a > img tr > td > a > img | whos.amung.us/cwidget/62nl1k3va5id/069ed8fff200.png | 81 x 29 | 81 x 29 | 122 x 44 |
td > center > a > img td > center > a > img | www.haproxy.org/img/btn_donate_SM_eur.gif | 74 x 21 | 74 x 21 | 111 x 32 |
td > center > a > img td > center > a > img | www.haproxy.org/img/btn_donate_SM_usd.gif | 74 x 21 | 74 x 21 | 111 x 32 |
tbody > tr > td > img tbody > tr > td > img | www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 83 x 60 | 254 x 60 | 125 x 90 |
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|
| /cgi-bin/webscr?cmd=_donations&business=w%401wt%2eeu&lc=F... | Click here |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr > td > img tbody > tr > td > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
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 |
|---|
Hide/Show unmaintained tbody > tr > td > a |
Hide/Show older ones ... tr > td > p > a |
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.
618 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
837 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.166
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
618 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.
837 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 0.0 ms | 15.0 KiB |
| www.haproxy.org/img/Ad_4.png | 0.0 ms | 13.6 KiB |
| www.haproxy.org/img/Ad_1.png | 0.0 ms | 10.3 KiB |
| www.haproxy.org/img/Ad_2.png | 0.0 ms | 8.3 KiB |
| www.haproxy.org/img/btn_donate_SM_eur.gif | 0.0 ms | 1.8 KiB |
| www.haproxy.org/img/btn_donate_SM_usd.gif | 0.0 ms | 1.7 KiB |
| www.haproxy.org/size.css?1350x940 | 0.0 ms | 255 B |
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.
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.
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 | |
|---|---|---|---|
tbody > tr > td > img tbody > tr > td > img | www.haproxy.org/img/HAProxyCommunityEdition_60px.png | 14.7 KiB | 12.2 KiB |
center > p > a > img center > p > a > img | www.haproxy.org/img/Ad_4.png | 13.4 KiB | 9.2 KiB |
center > p > a > img center > p > a > img | www.haproxy.org/img/Ad_1.png | 10.0 KiB | 5.9 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.
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.
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 |
|---|---|
| haproxy.org/ | 238 ms |
| www.haproxy.org/ | 0.0 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Branch Release date End of life Latest version Changelog Links
3.4-dev ~2026-Q2… td > a > p > table | 0.166 |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
QUIC+UDP tbody > tr > td > span.xprt |
IPv6 tbody > tr > td > span.netw |
HAProxy 3.3.0 release td > p > b > font |
HAProxy 3.2.0 release td > p > b > font |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr > td > img tbody > tr > td > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
td > center > p > a td > center > p > a |
td > center > p > a td > center > p > a |
td > center > p > a td > center > p > a |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Two vulnerabilities affecting some deep parts of the QUIC parsing were reported… tbody > tr > td > ul |
It's no news that many users have been hit by the massive performance cost caus… tbody > tr > td > ul |
This stable release as usual introduces significant advancements in performance… tbody > tr > td > ul |
This LTS release improves in a lot of areas. First, many improvements were made… tbody > tr > td > ul |
contact HAProxy Technologies to hire some professional services or subscribe a … tbody > tr > td > ol |
mailing-list : haproxy@formilux.org
Read the list archives on mail-archive
Read… tbody > tr > td > ul |
irc://irc.libera.chat/%23haproxy tbody > tr > td > ul |
https://slack.haproxy.org/ tbody > tr > td > ul |
These are opportunities to improve the experience of reading tabular or list data using 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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Quick News tbody > tr > td > a |
Recent News tbody > tr > td > a |
Description tbody > tr > td > a |
Performance tbody > tr > td > a |
Reliability tbody > tr > td > a |
Security tbody > tr > td > a |
Documentation tbody > tr > td > a |
Project on GitHub tbody > tr > td > a |
Download sources / doc tbody > tr > td > a |
Packages / Images / Distros tbody > tr > td > a |
Live demo tbody > tr > td > a |
They use it! tbody > tr > td > a |
Enterprise Features tbody > tr > td > a |
Third party extensions tbody > tr > td > a |
Commercial Support tbody > tr > td > a |
Contacts tbody > tr > td > a |
External links tbody > tr > td > a |
Discussions tbody > tr > td > a |
Slack channel tbody > tr > td > a |
Mailing list tbody > tr > td > a |
Coding style tbody > tr > td > a |
Open Issues tbody > tr > td > a |
Known bugs tbody > tr > td > a |
Signing keys tbody > tr > td > a |
HATop: Ncurses Interface tbody > tr > td > a |
Herald: load feedback agent tbody > tr > td > a |
RHEL-based Docker images tbody > tr > td > a |
Debian/Ubuntu packages tbody > tr > td > a |
Performance packages tbody > tr > td > a |
3.4-dev tbody > tr > td > a |
3.4-dev9 tbody > tr > td > a |
2026-04-15 tbody > tr > td > a |
3.3 tbody > tr > td > a |
3.3.6 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
3.2 tbody > tr > td > a |
3.2.15 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
3.0 tbody > tr > td > a |
3.0.19 tbody > tr > td > a |
2026-03-19 tbody > tr > td > a |
2.8 tbody > tr > td > a |
2.8.20 tbody > tr > td > a |
2026-03-20 tbody > tr > td > a |
2.6 tbody > tr > td > a |
2.6.25 tbody > tr > td > a |
2026-03-20 tbody > tr > td > a |
2.4 tbody > tr > td > a |
2.4.31 tbody > tr > td > a |
2026-03-09 tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Dir tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
Web tbody > tr > td > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Branch Release date End of life Latest version Changelog Links
3.4-dev ~2026-Q2… td > a > p > table |
dev 3.3 3.2 3.1 3.0 2.9 2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.9 1.8 1.7 1.6 1.… td > a > p > table |
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|
| /cgi-bin/webscr?cmd=_donations&business=w%401wt%2eeu&lc=F... | Click here |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr > td > img tbody > tr > td > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
center > p > a > img center > p > a > img |
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 |
|---|
Hide/Show unmaintained tbody > tr > td > a |
Hide/Show older ones ... tr > td > p > a |
To appear in search results, crawlers need access to your app.
Send Feedback