Skip to content
https://impactcommerce.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

39

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.

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: div.hero-bg > div.hero-bg-inner > div.hero-bg__video > video.hero-bg__video__src
path: 1,HTML,1,BODY,6,DIV,2,DIV,0,MAIN,0,ARTICLE,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.hero-bg > div.hero-bg-inner > div.hero-bg__video > video.hero-bg__video__src
snippet: <video class="hero-bg__video__src js-lazy-load-video-src" preload="auto" autoplay="" loop="" muted="" playsinline="" webkit-playsinline="" poster="https://impactcommerce.com/wp-content/themes/impact/assets/img/transparent…" style="background-image: url(&quot;https://impactcommerce.com/wp-content/uploads/2021/…&quot;);">

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

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.

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.

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 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: 220 ms 43.0 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.

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.

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.

CategoryTime Spent
Other4.8 s
Style & Layout2.5 s
Script Evaluation2.3 s
Rendering454 ms
Script Parsing & Compilation366 ms
Parse HTML & CSS144 ms
Garbage Collection40 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 reasonFailure type
The page has an unload handler in the main frame.Actionable

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
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 14 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 180 ms
●Server Backend Latencies 720 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 320 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
91

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#coi-banner-wrapper > div#coiPage-1 > div.coi-banner__summary > button#coi-expand div#coi-banner-wrapper > div#coiPage-1 > div.coi-banner__summary > button#coi-expand

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
div.site-header-inner > div > div.site-header__item > a.logo div.site-header-inner > div > div.site-header__item > a.logo
div.grid-item-inner > div.grid-item__figure > div.grid-item__image > a div.grid-item-inner > div.grid-item__figure > div.grid-item__image > a
div.grid-item-inner > div.grid-item__figure > div.grid-item__image > a div.grid-item-inner > div.grid-item__figure > div.grid-item__image > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.content-section-inner > div.logo-container > div.logo-item > a div.content-section-inner > div.logo-container > div.logo-item > a
div.site-footer-item > ul.list-unstyled > li > a.facebook-link div.site-footer-item > ul.list-unstyled > li > a.facebook-link
div.site-footer-item > ul.list-unstyled > li > a.instagram-link div.site-footer-item > ul.list-unstyled > li > a.instagram-link
div.site-footer-item > ul.list-unstyled > li > a.linkedin-link div.site-footer-item > ul.list-unstyled > li > a.linkedin-link
div.site-footer-item > ul.list-unstyled > li > a.youtube-link div.site-footer-item > ul.list-unstyled > li > a.youtube-link

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.

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
EVERYTHING YOU NEED TO SCALE AND SUCCEED  div.content-sections > section.content-section > div.content-section-inner > h3

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●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
○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
○`<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
○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.
○Tables have different content in the summary attribute and `<caption>`.
○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.
77

Best Practices

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 / WarningSource
Unload event listeners are deprecated and will be removed.

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.

SourceDescription
Access to fetch at 'https://api.leadinfo.com/v1/identify/LI-67ADD80FBFA22' from origin 'https://impactcommerce.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 404 ()
Refused to execute script from 'https://impactcommerce.piwik.pro/containers/e7b10a3a-5356-4506-97c9-69ce1876549d.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled.

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
85

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.site-panel-wrapper > div.site-panel-header > div.site-panel-navigation > a.site-panel-arrow
div.site-panel-wrapper > div.site-panel-header > div.site-panel-navigation > a.site-panel-arrow

To appear in search results, crawlers need access to your app.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback