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.

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	105.0 KiB
/signals/config/804607192460995?v=2.9.379&r=stable&domain...	1200.0 s	63.8 KiB
widgets.leadconnectorhq.com/chat-widget/p-5ff9a208.entry.js	14400.0 s	50.6 KiB
widgets.leadconnectorhq.com/chat-widget/p-BmGdPlUL.js	14400.0 s	24.7 KiB
widgets.leadconnectorhq.com/chat-widget/assets/defaultAvatar.png	14400.0 s	22.4 KiB
widgets.leadconnectorhq.com/chat-widget/p-Do7bswAW.js	14400.0 s	15.5 KiB
widgets.leadconnectorhq.com/chat-widget/p-Bck6bG0u.js	14400.0 s	7.7 KiB
widgets.leadconnectorhq.com/chat-widget/p-CbVA63cT.js	14400.0 s	3.2 KiB
services.leadconnectorhq.com/appengine/cors/js/user-session.js	14400.0 s	3.1 KiB
/tr/?id=804607192460995&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	18 B

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:44.308 source:map[column:6218 line:3083 type:source-location url:https://www.openheartmediaco.com/ urlProvider:network]]]

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-0-VIDEO

nodeLabel: ohm promo FINAL-1.mp4

path: 1,HTML,1,BODY,78,DIV,1,DIV,2,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,3,MAIN,1,SECTION,0,DIV,1,DIV,0,WIX-VIDEO,0,VIDEO

selector: div#bgLayers_comp-lz6pblof > div#bgMedia_comp-lz6pblof > wix-video#videoContainer_comp-lz6pblof > video#comp-lz6pblof_video

snippet: <video id="comp-lz6pblof_video" class="X9nqm0" crossorigin="anonymous" aria-label="ohm promo FINAL-1.mp4" playsinline="" preload="auto" muted="" loop="" autoplay="" src="https://video.wixstatic.com/video/a890dd_2299b2d19e48462a8285f3d216cba8ea/…" style="height: 100%; width: 100%; object-fit: cover;">

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

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
widgets.leadconnectorhq.com/loader.js	4.8 KiB	831 ms

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
Image of a laptop with the Sun & Shield website on the laptop `div > wow-image#img-comp-mfcsrrcj > picture > img`	/media/92ff08_4ea8aaf9f609448195004a7a8bab300d~mv2.png/v1...	34.1 KiB	23.0 KiB
Avatar `div#lc_text-widget > div.lc_text-widget--prompt > div.lc_text-widget_prompt--msg-bubble > img.lc_text-widget_prompt--avatar`	widgets.leadconnectorhq.com/chat-widget/assets/defaultAvatar.png	21.8 KiB	21.6 KiB
image of two phones with Nitro Pro & Adnourmas posts on the screens `div > wow-image#img-comp-mfct1qli > picture > img`	/media/92ff08_d885a2373b8142679ee566a31db6a7d9~mv2.png/v1...	21.8 KiB	14.7 KiB
Image of a laptop with data on the screen `div > wow-image#img-comp-mfcsn0ez > picture > img`	/media/92ff08_e4643885dbdd47ffa2cb270dffdb704b~mv2.png/v1...	18.7 KiB	12.6 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

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: 900 ms 247.3 KiB

URL	Transfer Size	Est Savings
/services/wix-thunderbolt/dist/group_6.84400d58.chunk.min.js	65.6 KiB	40.4 KiB
connect.facebook.net/en_US/fbevents.js	104.9 KiB	35.9 KiB
/services/form-app/1.2927.0/client-viewer/form-app-wix-ri...	31.8 KiB	31.7 KiB
browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.min.js	39.9 KiB	28.2 KiB
/services/wix-thunderbolt/dist/motion.a51fa0ca.chunk.min.js	29.0 KiB	23.8 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.0c90abca.bundle.min.js	56.1 KiB	22.5 KiB
widgets.leadconnectorhq.com/chat-widget/p-5ff9a208.entry.js	50.1 KiB	22.4 KiB
/signals/config/804607192460995?v=2.9.379&r=stable&domain...	63.7 KiB	22.3 KiB
/services/wix-thunderbolt/dist/thunderbolt-commons.2de71c...	42.4 KiB	20.0 KiB

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	1.8 s	661 ms	0.0 ms
www.openheartmediaco.com/	1.2 s	247 ms	36 ms
static.parastorage.com/unpkg/react@18.3.1/umd/react.production.min.js	409 ms	395 ms	0.8 ms
connect.facebook.net/en_US/fbevents.js	378 ms	310 ms	26 ms
widgets.leadconnectorhq.com/chat-widget/p-Do7bswAW.js	189 ms	140 ms	0.1 ms
/services/wix-thunderbolt/dist/group_6.84400d58.chunk.min.js	166 ms	49 ms	17 ms
static.parastorage.com/services/wix-thunderbolt/dist/main.0c90abca.bundle.min.js	147 ms	112 ms	25 ms
/signals/config/804607192460995?v=2.9.379&r=stable&domain...	140 ms	121 ms	18 ms
static.parastorage.com/unpkg/react-dom@18.3.1/umd/react-dom.production.min.js	120 ms	37 ms	9.0 ms
/services/wix-thunderbolt/dist/group_2.52faece0.chunk.min.js	119 ms	114 ms	4.4 ms
/services/wix-thunderbolt/dist/thunderbolt-commons.2de71c...	96 ms	67 ms	17 ms
/services/editor-elements-library/dist/thunderbolt/rb_wix...	81 ms	65 ms	8.0 ms
/services/wix-thunderbolt/dist/routerFetch.c9420889.chunk...	68 ms	33 ms	34 ms
/services/wix-thunderbolt/dist/animations.d94f0463.chunk....	52 ms	51 ms	1.1 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	3.0 s
Other	1.6 s
Style & Layout	469 ms
Script Parsing & Compilation	334 ms
Parse HTML & CSS	174 ms
Rendering	103 ms
Garbage Collection	93 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 83.5 KiB

URL	Transfer Size	Est Savings
@font-face { font-display: swap; font-family: wf_dde043c9cc214f9bbc15a2e74; … } …	50.7 KiB	31.5 KiB
.sWmh0WA{position:relative;width:100%} …	31.3 KiB	24.6 KiB
html.ios { --ion-default-font: -apple-system, BlinkMacSystemFont, "Helvetica Neue", "Roboto", sans-s… } …	17.5 KiB	16.8 KiB
.StylableButton2545352419__root{-archetype:box;cursor:pointer;box-sizing:border-box; … } …	11.2 KiB	10.6 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
/video/a890dd_2299b2d19e48462a8285f3d216cba8ea/480p/mp4/f...	3.6 MiB
www.openheartmediaco.com/	233.2 KiB
connect.facebook.net/en_US/fbevents.js	105.0 KiB
/pages/pages/thunderbolt?appDefinitionIdToSiteRevision=%7...	88.6 KiB
static.parastorage.com/services/form-app/1.2927.0/viewerScript.bundle.min.js	70.5 KiB
/services/wix-thunderbolt/dist/group_6.84400d58.chunk.min.js	65.6 KiB
/signals/config/804607192460995?v=2.9.379&r=stable&domain...	63.8 KiB
/ufonts/106523_1976ef4edbf44111abd4bd57d1e3e8f4/woff2/fil...	62.7 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.0c90abca.bundle.min.js	56.3 KiB
widgets.leadconnectorhq.com/chat-widget/p-5ff9a208.entry.js	50.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.


Instagram `li#dataItem-meka134y-comp-kbgakxmn_r_comp-mek9zfqg > a.FvIvPq > wow-image#img_0_comp-kbgakxmn_r_comp-mek9zfqg > img`
LinkedIn `li#dataItem-meka134z-comp-kbgakxmn_r_comp-mek9zfqg > a.FvIvPq > wow-image#img_1_comp-kbgakxmn_r_comp-mek9zfqg > img`
Facebook `li#dataItem-meka134z1-comp-kbgakxmn_r_comp-mek9zfqg > a.FvIvPq > wow-image#img_2_comp-kbgakxmn_r_comp-mek9zfqg > img`
Youtube `li#dataItem-meka134z2-comp-kbgakxmn_r_comp-mek9zfqg > a.FvIvPq > wow-image#img_3_comp-kbgakxmn_r_comp-mek9zfqg > img`

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

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 421 user timings

●Avoid long main-thread tasks 15 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 240 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 30 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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.

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
Special Projects `section#comp-mfcsfyee > div.comp-mfcsfyee-container > div#comp-mfcsjw2a > h4.font_4`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○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 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 buttons have discernible text.

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

○Links are distinguishable without relying on color.

○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

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

○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

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
browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.min.js line 1, col 11650	`suspense rendered fallback for - comp-kbgakxea_r_comp-lxubhuix - (ExpandableMenu)`

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