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.

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:2.703 source:map[type:text value:[unattributed]]]]

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.

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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
static.parastorage.com/unpkg-semver/fedops-logger@5/fedops-logger.bundle.min.js	1800.0 s	19.6 KiB
a.mailmunch.co/app/v1/site.js	172800.0 s	8.8 KiB
a.mailmunch.co/app/v1/styles.css	172800.0 s	2.7 KiB
/wix_widget_load?wix_v2=1&v=2026.04.28d&ie8=0&instance=f8...	0.0 ms	548 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
HAL logo with a globe and text, representing the company. `div > div#comp-liyv8ujl > div.apPOZK > img#img_comp-liyv8ujl`	/media/e362b7_89552196883a4e4c9e5a03714b640556~mv2.png/v1...	9.3 KiB	7.1 KiB
Honda `div > div#comp-liyubkh6 > div.apPOZK > img#img_comp-liyubkh6`	/media/e362b7_7cbbd954fa5c40539b6258e22a156087~mv2.png/v1...	7.8 KiB	5.3 KiB
Ashok Layland `div > div#comp-liyuhq2f > div.apPOZK > img#img_comp-liyuhq2f`	/media/e362b7_81062e86d3d440be9b165e17810ef203~mv2.png/v1...	10.2 KiB	5.3 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s

URL	Time Spent
www.multitek.in/	1.5 s

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
Unattributable	3.1 s	1.3 s	0.0 ms
www.multitek.in/	1.9 s	697 ms	83 ms
static.parastorage.com/unpkg/react@18.3.1/umd/react.production.min.js	1.0 s	933 ms	2.3 ms
www.googletagmanager.com/gtag/js?id=AW-11321254433	822 ms	659 ms	83 ms
/services/wix-thunderbolt/dist/group_5.79994512.chunk.min.js	429 ms	274 ms	5.8 ms
www.googletagmanager.com/gtag/js?id=G-8750JB8W05	418 ms	333 ms	82 ms
www.googletagmanager.com/gtm.js?id=GTM-KJPXS95	368 ms	301 ms	61 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	310 ms	251 ms	57 ms
/services/wix-thunderbolt/dist/thunderbolt-commons.cd47ac...	307 ms	242 ms	26 ms
widget.privy.com/assets/widget.js	301 ms	221 ms	73 ms
/services/wix-thunderbolt/dist/group_2.c60c4730.chunk.min.js	297 ms	271 ms	25 ms
static.parastorage.com/unpkg/requirejs-bolt@2.3.6/requirejs.min.js	292 ms	286 ms	2.8 ms
/services/tag-manager-client/1.1075.0/siteTags.bundle.min.js	254 ms	236 ms	1.9 ms
/services/wix-thunderbolt/dist/group_6.5f7b0030.chunk.min.js	164 ms	58 ms	39 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	143 ms	134 ms	6.9 ms
static.parastorage.com/services/wix-thunderbolt/dist/main.34f6665a.bundle.min.js	135 ms	76 ms	34 ms
/services/wix-thunderbolt/dist/animations.5f622044.chunk....	126 ms	123 ms	2.5 ms
www.googletagmanager.com/gtag/js?id=AW-11321254433&cx=c&gtm=4e6ae1h1	125 ms	39 ms	85 ms
/services/editor-elements-library/dist/thunderbolt/htmlpa...	108 ms	91 ms	7.8 ms
ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js	103 ms	81 ms	14 ms
/services/wix-thunderbolt/dist/thunderbolt-components-reg...	87 ms	67 ms	8.2 ms
/services/cookie-consent-banner-for-uou/1.865.0//app.bund...	86 ms	68 ms	16 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	84 ms	73 ms	7.1 ms
/services/profile-card-tpa-ooi/1.2966.0/ProfileCardViewer...	79 ms	17 ms	57 ms
static.parastorage.com/unpkg/lodash@4.18.1/lodash.min.js	71 ms	54 ms	15 ms
static.parastorage.com/unpkg/react-dom@18.3.1/umd/react-dom.production.min.js	63 ms	28 ms	33 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	63 ms	53 ms	5.3 ms
/services/wix-thunderbolt/dist/routerFetch.0667279b.chunk...	56 ms	48 ms	8.1 ms
browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.min.js	56 ms	28 ms	19 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	53 ms	39 ms	13 ms
/services/wix-thunderbolt/dist/group_4.e486b681.chunk.min.js	50 ms	42 ms	7.6 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	8.1 s
Other	2.4 s
Script Parsing & Compilation	1.1 s
Style & Layout	523 ms
Parse HTML & CSS	357 ms
Garbage Collection	189 ms
Rendering	119 ms

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 WebSocket cannot enter back/forward cache.	Pending browser support
The page did not finish loading before navigating away.	Not actionable

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: 10 ms 603.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=AW-11321254433&cx=c&gtm=4e6ae1h1	165.6 KiB	116.2 KiB
widget.privy.com/assets/widget.js	145.1 KiB	83.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KJPXS95	131.9 KiB	68.0 KiB
www.googletagmanager.com/gtag/js?id=G-8750JB8W05	167.8 KiB	65.7 KiB
www.googletagmanager.com/gtag/js?id=AW-11321254433	165.6 KiB	60.0 KiB
/services/editor-elements-library/dist/thunderbolt/rb_wix...	67.9 KiB	43.8 KiB
/services/profile-card-tpa-ooi/1.2966.0/ProfileCardViewer...	56.0 KiB	36.9 KiB
/services/wix-thunderbolt/dist/group_6.5f7b0030.chunk.min.js	55.9 KiB	34.3 KiB
browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.min.js	39.9 KiB	27.2 KiB
/services/wix-thunderbolt/dist/motion.c8984600.chunk.min.js	28.9 KiB	24.5 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.34f6665a.bundle.min.js	56.4 KiB	22.5 KiB
ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js	32.7 KiB	21.2 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.multitek.in/	211.7 KiB
www.googletagmanager.com/gtag/js?id=G-8750JB8W05	168.1 KiB
www.googletagmanager.com/gtag/js?id=AW-11321254433&cx=c&gtm=4e6ae1h1	165.6 KiB
www.googletagmanager.com/gtag/js?id=AW-11321254433	165.6 KiB
widget.privy.com/assets/widget.js	145.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KJPXS95	131.9 KiB
static.parastorage.com/services/chat-widget/1.2763.0/chat-widget.min.css	92.6 KiB
static.parastorage.com/services/chat-widget/1.2763.0/chat-widget.bundle.min.js	92.4 KiB
/services/ecom-platform-viewer-script/1.169.0/webworker/e...	89.1 KiB
/pages/pages/thunderbolt?appDefinitionIdToSiteRevision=%7...	75.3 KiB

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

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 605 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 250 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Video Title Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1de1`
Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1dl`
Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1dq`
Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1dv`
Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1dz`
Your Video Title Video Player `div#comp-l4tls1dc > div > div > div#comp-l4tls1e3`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

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
`p.font_8 > span.wixui-rich-text__text > span.color_41 > a.wixui-rich-text__text`

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.

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Links are distinguishable without relying on color.

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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

○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

○Identical links have the same purpose.

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

100

Best Practices

●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

●Serves images with appropriate resolution

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