Nighthawks

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>新入荷</span>	.full-width > .wpb_row.row-inner > .half-internal-gutter.column_parent.col-lg-12 > .animate_when_almost_visible.alpha-anim.start_animation > .uncoltable > .uncell.no-block-padding > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h2 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 15.8pt, font weight: bold). Expected contrast ratio of 3:1
serious	<span>ブログ</span>	.no-top-padding.single-bottom-padding.single-h-padding > .wpb_row.row-inner > .half-internal-gutter.column_parent.col-lg-12 > .animate_when_almost_visible.alpha-anim.start_animation > .uncoltable > .uncell.no-block-padding > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h2 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 15.8pt, font weight: bold). Expected contrast ratio of 3:1
serious	<span>ニュースレター</span>	.vc_custom_1606946330098 > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h4 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 11.3pt, font weight: bold). Expected contrast ratio of 4.5:1
serious	<span>Nighthawks</span>	.vc_custom_1607032232532 > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h4 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 11.3pt, font weight: bold). Expected contrast ratio of 4.5:1
serious	<span>インフォメーション</span>	.col-md-clear.col-sm-clear.col-lg-3:nth-child(3) > .uncol.style-light > .uncoltable > .uncell.no-block-padding > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h4 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 11.3pt, font weight: bold). Expected contrast ratio of 4.5:1
serious	<span>フォローする</span>	.col-md-clear.col-sm-clear.col-lg-3:nth-child(4) > .uncol.style-light > .uncoltable > .uncell.no-block-padding > .uncont > .vc_custom_heading_wrap.headers > .heading-text.el-text > h4 > span	Fix any of the following: Element has insufficient color contrast of 1.95 (foreground color: #bab9b9, background color: #ffffff, font size: 11.3pt, font weight: bold). Expected contrast ratio of 4.5:1
...

Autocomplete is used to suggest popular searches (but can be ignored)

Fails if no autocomplete or if the user is not allowed to ignore the autocomplete.

Filtering is available and prominent on search results or category listing pages

Fails if filtering is appropriate but not provided or if sorting is prioritized over filtering in the visual hierarchy.

The product details follow a set pattern making it easier to compare, e.g. bullet points with tech specs

Fails if different product description information formatting from one page to another.

Key and appropriate information is provided and easy to find on the product page

Fails if any key information is missing or hard to find, i.e. delivery dates, shipping costs, returns policy plus all product pertinent info like size, colour, quantity, etc.

All product images are zoomable, without blur

Fails if product images are blurry at full zoom.

Carousels are generally avoided (but they are acceptable if they are well implemented)

Fails if any of the following are seen: carousels auto-rotate, text is not legible, swipe is not supported, next images do not load within 1 second of swipe.

There is a choice to convert without creating an account, i.e. Guest checkout

Fails if no guest checkout.

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.

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