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.

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.

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
td > p > a > img.bookImage `td > p > a > img.bookImage`	www.ssllabs.com/images/bulletproof-cover.png	35.7 KiB	29.6 KiB
SSL Labs logo `div#header > div#logo > a > img`	www.ssllabs.com/images/qualys-ssl-labs-logo.png	20.7 KiB	17.1 KiB
HOW WELL DO YOU KNOW SSL? If you want to learn more about the technology that p… `body > div#page > div.mainPhoto`	www.ssllabs.com/images/main-background.jpg	59.8 KiB	9.7 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-2-DIV

nodeLabel: HOW WELL DO YOU KNOW SSL? If you want to learn more about the technology that p…

path: 1,HTML,1,BODY,11,DIV,2,DIV

selector: body > div#page > div.mainPhoto

snippet: <div class="mainPhoto">

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

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.google-analytics.com/analytics.js	7200.0 s	20.9 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.ssllabs.com/includes/main.css	2.3 KiB
www.ssllabs.com/includes/ssllabs.css	1.1 KiB	150 ms

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s

URL	Time Spent
ssllabs.com/	1.2 s
www.ssllabs.com/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s 195.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-P0XTZ1H52W&cx=c&_slc=1	147.6 KiB	65.4 KiB
www.googletagmanager.com/gtag/js?id=G-0R8KL6N67R&cx=c&gtm=4e64h1	155.6 KiB	65.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-MPWDSJ	137.4 KiB	64.5 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

Why this matters

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
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 599 KiB

●User Timing marks and measures 12 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 5 long tasks found

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

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○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.

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
td > p > a > img.bookImage `td > p > a > img.bookImage`
td > h2 > a > img `td > h2 > a > img`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td > iframe#news-iframe `tbody > tr > td > iframe#news-iframe`

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
tr > td > p > a `tr > td > p > a`
tr > td > h2 > a `tr > td > h2 > 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.

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.

Best practices

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.

○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>`

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●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

○`[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

○`<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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

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

○`<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.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

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
td > h2 > a > img `td > h2 > a > img`	www.ssllabs.com/images/rss-icon-16.png	16 x 16	16 x 16	24 x 24

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.

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.googletagmanager.com/gtag/js?id=G-0R8KL6N67R&cx=c&gtm=4e64h1 line 223, col 390	Connecting to 'https://region1.google-analytics.com/g/collect?v=2&tid=G-0R8KL6N67R&gtm=45je64h1v9101422353z871004553za20gzb71004553zd71004553&_p=1776811343729&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&are=1&cid=1524311715.1776811344&frm=0&pscdl=noapi&rcb=5&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&_s=1&tag_exp=0~115938465~115938468~117266400~118463262&sid=1776811344&sct=1&seg=0&dl=https%3A%2F%2Fwww.ssllabs.com%2F&dt=Qualys%20SSL%20Labs&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=1090' violates the following Content Security Policy directive: "default-src 'self' ssllabs.com *.ssllabs.com www.qualys.com https://www.google-analytics.com/ https://www.googletagmanager.com/ https://stats.g.doubleclick.net https://www.google.com/ https://cdn.bizible.com https://serve.albacross.com https://collect.albacross.com https://tagmanager.google.com https://js.driftt.com". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.
www.googletagmanager.com/gtag/js?id=G-P0XTZ1H52W&cx=c&_slc=1 line 193, col 390	Connecting to 'https://region1.google-analytics.com/g/collect?v=2&tid=G-P0XTZ1H52W&gtm=45je64h1v9126291901za20g&_p=1776811343729&gcd=13l3l3l2l3l1&npa=1&dma_cps=a&dma=1&_eu=ABAI&are=1&cid=1524311715.1776811344&frm=0&pscdl=noapi&rcb=17&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&_s=1&tag_exp=0~115938465~115938468~117266400&dl=https%3A%2F%2Fwww.ssllabs.com%2F&dt=Qualys%20SSL%20Labs&sid=1776811344&sct=1&seg=0&_tu=wAQ&en=page_view&_fv=1&_ss=1&_ee=1&gap.uat=0~115616985~115938465~115938468~117266401&tfd=1281' violates the following Content Security Policy directive: "default-src 'self' ssllabs.com *.ssllabs.com www.qualys.com https://www.google-analytics.com/ https://www.googletagmanager.com/ https://stats.g.doubleclick.net https://www.google.com/ https://cdn.bizible.com https://serve.albacross.com https://collect.albacross.com https://tagmanager.google.com https://js.driftt.com". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.
www.googletagmanager.com/gtag/js?id=G-0R8KL6N67R&cx=c&gtm=4e64h1 line 223, col 390	Fetch API cannot load https://region1.google-analytics.com/g/collect?v=2&tid=G-0R8KL6N67R&gtm=45je64h1v9101422353z871004553za20gzb71004553zd71004553&_p=1776811343729&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&are=1&cid=1524311715.1776811344&frm=0&pscdl=noapi&rcb=5&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&_s=1&tag_exp=0~115938465~115938468~117266400~118463262&sid=1776811344&sct=1&seg=0&dl=https%3A%2F%2Fwww.ssllabs.com%2F&dt=Qualys%20SSL%20Labs&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=1090. Refused to connect because it violates the document's Content Security Policy.
www.googletagmanager.com/gtag/js?id=G-P0XTZ1H52W&cx=c&_slc=1 line 193, col 390	Fetch API cannot load https://region1.google-analytics.com/g/collect?v=2&tid=G-P0XTZ1H52W&gtm=45je64h1v9126291901za20g&_p=1776811343729&gcd=13l3l3l2l3l1&npa=1&dma_cps=a&dma=1&_eu=ABAI&are=1&cid=1524311715.1776811344&frm=0&pscdl=noapi&rcb=17&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&_s=1&tag_exp=0~115938465~115938468~117266400&dl=https%3A%2F%2Fwww.ssllabs.com%2F&dt=Qualys%20SSL%20Labs&sid=1776811344&sct=1&seg=0&_tu=wAQ&en=page_view&_fv=1&_ss=1&_ee=1&gap.uat=0~115616985~115938465~115938468~117266401&tfd=1281. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Displays images with correct aspect ratio

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○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

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
td > p > a > img.bookImage `td > p > a > img.bookImage`
td > h2 > a > img `td > h2 > a > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`