Body EM

Content is not blocked for zoom/scale

The `[user-scalable="no"]` parameter is not present in the `<meta name="viewport">` element and the `[maximum-scale]` parameter is not less than 2.Source: Lighthouse - Learn more

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Source: Lighthouse - Learn more

Uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Source: Lighthouse - Learn more

Color Contrast is satisfactory

Low-contrast text is difficult or impossible for many users to read. Background and foreground colors should have enough contrast ratio to guarantee readability. Source: Lighthouse - Learn more

Failing Elements

Impact	Snippet	Target	Failure Summary
serious	<span class="orange-text">EM</span>	.orange-text	Fix any of the following: Element has insufficient color contrast of 2.43 (foreground color: #f9890f, background color: #ffffff, font size: 46.3pt, font weight: normal). Expected contrast ratio of 3:1
serious	<span class="headingLine ampersand aos-init aos-animate" data-aos="heading-in" data-aos-delay="250"> &amp; </span>	.ampersand	Fix any of the following: Element has insufficient color contrast of 2.43 (foreground color: #f9890f, background color: #ffffff, font size: 46.3pt, font weight: normal). Expected contrast ratio of 3:1
serious	<a href="https://lenus.io/bodyem/legal-terms?locale=en-GB" target="_blank"> Terms and Conditions</a>	.wpbf-inner-footer-left > a[target="_blank"]:nth-child(1)	Fix any of the following: Element has insufficient color contrast of 2.43 (foreground color: #f9890f, background color: #ffffff, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1
serious	<a href="https://lenus.io/bodyem/data-policy?locale=en-GB" target="_blank">Privacy Policy</a>	a[target="_blank"]:nth-child(2)	Fix any of the following: Element has insufficient color contrast of 2.43 (foreground color: #f9890f, background color: #ffffff, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1
serious	<a href="https://www.lenus.io" target="_blank">Lenus.io</a>	a[href$="www.lenus.io"]	Fix any of the following: Element has insufficient color contrast of 2.43 (foreground color: #f9890f, background color: #ffffff, font size: 10.5pt, font weight: normal). Expected contrast ratio of 4.5:1
...

Key and appropriate information is provided and is easy to find on the product page e.g. APR, key benefits, etc

Fails if information is missing or hard to find.

Relevant product/service details are concise and use bullet points to make it easy for the user to skim and scan the content for understanding

Fails if content is laid out in text form and large paragraphs requiring the user to seek out the information themselves by reading large bodies of text.

Phone numbers are clickable to make callsNot applicable

Fails if missing tap to call functionality.

Links never open new browser tabs unless clearly indicated or users can back arrow to the previous page

Fails if opening new browser tabs without warning the user in advance that this will happen.

Access to instant, responsive support (web chat or phone) within office hours is available at any point

Fails if missing or hard to find contact options. Contact options should align with regional expectations.

Optional fields are clearly optional

Fails if it is not clear that optional fields are optional, i.e. They do not say 'optional' or they do not follow the pattern of no asterisk for optional, while compulsory fields do.

The most appropriate keyboard for the input type is provided first

Fails if most helpful keyboard not provided, i.e. input types text, tel, email, password, capitalization when appropiate, etc.

The website supports autofill for all form fields and the fields are tagged for the appropriate information from autofill

Fails if fields are not tagged for efficient browser-based autofill, making users enter data that is already known either by the website or the OS. Not filling a standard field or filling fields with the wrong content, i.e. puts house number and street name into the same field when there are separate fields for each.

All mistakes made in forms are clearly highlighted in real time, and instructions for correct completion are provided in real time

Fails if mistakes and guidance for correct completion are not highlighted in real time and/or error messages are ambiguous or unfriendly.

Within a form, users can navigate back and forth between steps/pages without losing previously inputted information

Fails if a user backtracks and previously entered data is lost.

Avoids Application Cache

Application Cache is deprecated. Source: Lighthouse - Learn more

Avoids WebSQL DB

Web SQL is deprecated. Consider using IndexedDB instead. Source: Lighthouse - Learn more

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Source: Lighthouse

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Source: Lighthouse - Learn more

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Source: Lighthouse - Learn more

Allows to paste into password input fields

The main reason why password pasting improves security is because it helps to reduce password overload. Source: Lighthouse - Learn more

Registers a Service Worker

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Source: Lighthouse - Learn more

Responds with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Source: Lighthouse - Learn more

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Source: Lighthouse - Learn more

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Source: Lighthouse - Learn more

Uses HTTP/2 for its own resources

HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Source: Lighthouse - Learn more

Uses passive listeners to improve scrolling performance

Mark your touch and wheel event listeners as `passive` to improve your page's scroll performance. Source: Lighthouse - Learn more

Avoid using document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Source: Lighthouse - Learn more

Manifest's short_name won't be truncated when displayed on homescreen

Make your app's short_name fewer than 12 characters to ensure that it's not truncated on homescreens. Source: Lighthouse - Learn more

Configured for a custom splash screen

A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint. Source: Lighthouse - Learn more

User can be prompted to Install the Web App

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Source: Lighthouse - Learn more