Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:31.329 source:map[column:150 line:968 type:source-location url:https://www.haproxy.org/ urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 806 ms

URL	Time Spent
haproxy.org/	806 ms
www.haproxy.org/	0.0 ms

●Time to Interactive 2.0 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 78 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.4 s

●Avoid long main-thread tasks 1 long task found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 90 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 20 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

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.

Internationalization and localization

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.

Why this matters

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.

Names and labels

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.

Why this matters

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.

Why this matters

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

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.

Best practices

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.

Why this matters

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.

Why this matters

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.

Why this matters

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`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

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.

Why this matters

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

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

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.

Why this matters

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.

Crawling and Indexing

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

Why this matters

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`