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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
mxtoolbox.com/public/stylesheets/webfonts/fa-brands-400.woff2	30 ms
mxtoolbox.com/public/stylesheets/webfonts/fa-duotone-900.woff2	15 ms

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
js.hs-analytics.net/analytics/1776893700000/14537821.js	300.0 s	42.3 KiB
js.usemessages.com/conversations-embed.js	600.0 s	33.0 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.1 KiB
js.hs-banner.com/v2/14537821/banner.js	300.0 s	24.1 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
js.hs-scripts.com/14537821.js	90.0 s	1.1 KiB
/v.gif?cd=0&a=24147&d=mxtoolbox.com&u=D51B8E30AAA3289B9B3...	43200.0 s	105 B

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
MX Logo `div.mx-tm-brand > div > a > img`	images.mxtoolbox.com/public/images/logo.png	7.4 KiB	4.4 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
/bundles/mx3rdPartyMinSync.js?v=oUKfU03s4Z9Hw1nBwX_yKENkb...	3.0 KiB
/public/stylesheets/bundles/mx3rdPartyPre.css?v=PC_pVAevh...	4.3 KiB
/public/stylesheets/min/mx.pre.css?serial=c230a4d699d0e23...	1.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
js.hs-analytics.net/analytics/1776893700000/14537821.js	441 ms	345 ms	8.9 ms
www.googletagmanager.com/gtag/js?id=G-YT4L4GZFH2&cx=c&gtm=4e64k0	333 ms	265 ms	42 ms
www.googletagmanager.com/gtm.js?id=GTM-WBCHSDC	261 ms	212 ms	47 ms
www.googletagmanager.com/gtag/js?id=AW-1072310887&cx=c&gtm=4e64k0	194 ms	164 ms	29 ms
Unattributable	191 ms	8.2 ms	0.0 ms
mxtoolbox.com/	178 ms	11 ms	8.2 ms
/bundles/mxClassicPreloadMin.js?v=etnLHqMI4mN3DnfEiVbnyRN...	135 ms	127 ms	2.4 ms
js.hubspot.com/web-interactives-embed.js	65 ms	54 ms	8.3 ms
cl.qualaroo.com/ki.js/61819/e3J.js	64 ms	50 ms	12 ms
js.usemessages.com/conversations-embed.js	58 ms	45 ms	8.6 ms
/bundles/mx3rdPartyMinDefer.js?v=K7K8ANEVoVmCmGAsvK00mQBA...	53 ms	39 ms	9.9 ms
www.googletagmanager.com/gtag/js?id=AW-1072310887	53 ms	22 ms	31 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.4 s
Other	267 ms
Script Parsing & Compilation	222 ms
Style & Layout	174 ms
Rendering	24 ms
Garbage Collection	24 ms
Parse HTML & CSS	17 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 10.8 KiB

URL	Transfer Size	Est Savings
/bundles/mxSharedMin.js?v=cShWU47cX7D1-5TZPz3W9AdPa356KXS...	13.4 KiB	7.3 KiB
/bundles/mxClassicPreloadMin.js?v=etnLHqMI4mN3DnfEiVbnyRN...	7.0 KiB	3.5 KiB

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: 0.0 ms 346.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=AW-1072310887	144.3 KiB	105.9 KiB
www.googletagmanager.com/gtag/js?id=G-YT4L4GZFH2&cx=c&gtm=4e64k0	179.2 KiB	66.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WBCHSDC	155.7 KiB	65.9 KiB
www.googletagmanager.com/gtag/js?id=AW-1072310887&cx=c&gtm=4e64k0	144.3 KiB	62.6 KiB
/bundles/mx3rdPartyMinDefer.js?v=K7K8ANEVoVmCmGAsvK00mQBA...	38.6 KiB	24.1 KiB
cl.qualaroo.com/ki.js/61819/e3J.js	53.7 KiB	21.7 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,037 KiB

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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
Solve Email Delivery Problems `div.divInput > div.tools_lookup_label > div.extra-info-section > a#ctl00_ContentPlaceHolder1_ucToolhandler_hlExtraButton1`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Diagnostics `div.p10 > div.tools_description > p > a`
blacklists `div.p10 > div.tools_description > p > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ABOUT MX LOOKUP `div#ctl00_ContentPlaceHolder1_pnlToolHandler > div.p10 > div.tools_description > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.divInput > div.tools_lookup_label > div > input#ctl00_ContentPlaceHolder1_ucToolhandler_txtToolInput `div.divInput > div.tools_lookup_label > div > input#ctl00_ContentPlaceHolder1_ucToolhandler_txtToolInput`

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.

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
`div.content-footer > div.footer-info > div.footer-icons > a`
div.content-footer > div.footer-info > div.footer-icons > a `div.content-footer > div.footer-info > div.footer-icons > 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.

○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-*]` attributes match their roles

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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

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

●Links have a discernible name

○`[accesskey]` values are unique

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

○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

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

○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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`<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
mx icon `div.search > div.panel-heading > h1.search > img#ctl00_ContentPlaceHolder1_ucToolhandler_imgToolIcon`	images.mxtoolbox.com/public/images/toolicons/mx.png	28 x 28	30 x 30	42 x 42

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.	/bundles/mx3rdPartyMinDefer.js?v=K7K8ANEVoVmCmGAsvK00mQBA...

●Uses HTTPS

●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

●Page has the HTML doctype

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`