Lighthouse Desktop

· 0 checks — Desktop 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
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_3_0.woff2	450 ms
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_2_0.woff2	450 ms
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_1_0.woff2	440 ms
/wp-content/themes/impact/assets/fonts/FlamaCondensed-Med...	400 ms

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:80.109 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.

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("https://impactcommerce.com/wp-content/uploads/2021/…");">

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.

URL	Transfer Size	Duration
/wp-content/themes/impact/assets/css/main-7e66b503cb.css?...	33.9 KiB	199 ms
impactcommerce.com/wp-includes/css/dist/block-library/style.min.css?ver=0c6e9b	14.6 KiB
cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js?ver=3.4.1	27.8 KiB	286 ms

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
cdn.dreamdata.cloud/scripts/analytics/next/dreamdata.min.js	1800.0 s	34.6 KiB
scripts.teamtailor-cdn.com/widgets/production/jobs.js	604800.0 s	10.2 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

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: 280 ms 452.8 KiB

URL	Transfer Size	Est Savings
cdn.ldnfrpl.com/rpl/be4cdf1b5aecf00c898b96d09e67ff493a98929e/rpl.js	174.3 KiB	155.6 KiB
/wp-content/themes/impact/assets/scripts/combined-996cf8d...	193.3 KiB	153.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TH24CKB	161.9 KiB	75.7 KiB
www.googletagmanager.com/gtag/js?id=G-RG057KK82T&cx=c&gtm=4e6581	175.2 KiB	68.3 KiB

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
Other	909 ms
Script Evaluation	561 ms
Style & Layout	416 ms
Script Parsing & Compilation	94 ms
Rendering	83 ms
Parse HTML & CSS	33 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
The page has an unload handler in the main frame.	Actionable

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 41.5 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/impact/assets/css/main-7e66b503cb.css?...	33.6 KiB	27.2 KiB
impactcommerce.com/wp-includes/css/dist/block-library/style.min.css?ver=0c6e9b	14.4 KiB	14.3 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
impactcommerce.com/wp-content/uploads/2021/12/frontpagehero.mp4	18.0 MiB
/wp-content/themes/impact/assets/scripts/combined-996cf8d...	193.6 KiB
/wp-content/uploads/2026/02/DSCF5779-Enhanced-NR-scaled-e...	176.7 KiB
www.googletagmanager.com/gtag/js?id=G-RG057KK82T&cx=c&gtm=4e6581	175.2 KiB
cdn.ldnfrpl.com/rpl/be4cdf1b5aecf00c898b96d09e67ff493a98929e/rpl.js	174.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-TH24CKB	162.2 KiB
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_3_0.woff2	49.2 KiB
/wp-content/themes/impact/assets/fonts/FlamaCondensed-Med...	42.6 KiB
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_1_0.woff2	39.3 KiB
impactcommerce.com/wp-content/themes/impact/assets/fonts/2D28C1_2_0.woff2	35.6 KiB

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.5 s

●Avoid long main-thread tasks 2 long tasks found

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

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 570 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

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

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

○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

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

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js?ver=3.4.1 line 1, col 41038

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
impactcommerce.com/	`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.`
api.leadinfo.com/v1/identify/LI-67ADD80FBFA22	`Failed to load resource: net::ERR_FAILED`
impactcommerce.piwik.pro/containers/e7b10a3a-5356-4506-97c9-69ce1876549d.js	`Failed to load resource: the server responded with a status of 404 ()`
impactcommerce.com/	`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.

URL
/wp-content/themes/impact/assets/scripts/combined-996cf8d...

●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

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.

Link destination	Link Text
tools.google.com/dlpage/gaoptout	here
www.youronlinechoices.com/uk/your-ad-choices	here

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`