Skip to content
https://softwareadvice.com

Lighthouse Desktop

· 0 checks — Desktop 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.

53

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 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.129 source:map[column:197 line:962 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-M86J6KQ urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:87.484 source:map[type:text value:[unattributed]]] map[reflowTime:0.129 source:map[column:376 line:916 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-M86J6KQ urlProvider:network]]]

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.

URLResource SizeEst Savings
Hero div.mx-auto > div.flex > div.relative > img
/_next/image/?url=https%3A%2F%2Fsoftware-advice.imgix.net...90.8 KiB84.8 KiB
advisors div.mx-auto > div.flex-col > div.relative > img
/_next/image/?url=https%3A%2F%2Fsoftware-advice.imgix.net...67.9 KiB61.1 KiB
Fresha div.mx-2 > a.flex > div.relative > img
/_next/image/?url=https%3A%2F%2Fgdm-catalog-fmapi-prod.im...25.1 KiB24.9 KiB
statistic-first div.mt-8 > a.row-span-1 > div.relative > img
/_next/image/?url=https%3A%2F%2Fsoftware-advice.imgix.net...22.2 KiB17.2 KiB
NextGen Healthcare div.mx-2 > a.flex > div.relative > img
/_next/image/?url=https%3A%2F%2Fgdm-catalog-fmapi-prod.im...13.0 KiB12.9 KiB

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-IMG
nodeLabel: Hero
path: 1,HTML,1,BODY,1,DIV,0,BUYER-INTENT-SESSION,0,BUYER-INTENT-VIEW,3,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.mx-auto > div.flex > div.relative > img
snippet: <img alt="Hero" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent;width:100%;height:auto" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fsoftware-advice.imgix.net%2Fhomepage%2Fhom…" src="https://www.softwareadvice.com/_next/image/?url=https%3A%2F%2Fsoftware-adv…">

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
value: No additional origins are good candidates for preconnecting

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.

RequestCache TTLTransfer Size
edge.fullstory.com/s/fs.js3600.0 s79.8 KiB
cdn.cookielaw.org/scripttemplates/202404.1.0/otBannerSdk.js86400.0 s108.8 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
edge.fullstory.com/datalayer/v4/latest.js3600.0 s13.5 KiB
widget.trustpilot.com/trustboxes/5419b637fa0340045cd0c936/main.js86400.0 s26.0 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s11.9 KiB
rs.fullstory.com/rec/integrations?OrgId=18VAHP&isInFrame=false&isNative=false0.0 ms4.0 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js86400.0 s8.1 KiB
lead-acquisition-service.softwareadvice.com/las-form-min.js14400.0 s4.6 KiB
lead-acquisition-service.softwareadvice.com/getSaConversionTrackingData.js14400.0 s4.1 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s3.7 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.8 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.7 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.5 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.5 KiB
/_next/image/?url=https%3A%2F%2Fcdn0.capterra-static.com%...14400.0 s2.5 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.5 KiB
/_next/image/?url=https%3A%2F%2Fcdn0.capterra-static.com%...14400.0 s2.3 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.3 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.2 KiB
/_next/image/?url=https%3A%2F%2Fcdn0.capterra-static.com%...14400.0 s2.1 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.1 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s2.0 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.8 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.8 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.8 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.8 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.7 KiB
/_next/image/?url=https%3A%2F%2Fcdn0.capterra-static.com%...14400.0 s1.7 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.6 KiB
/quem?authorization=pk_bda6cbd583df8a1df204600dfd908c4e&c...0.0 ms1.1 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.6 KiB
/_next/image/?url=https%3A%2F%2Freviews.capterra.com%2Fcd...14400.0 s1.5 KiB
/_next/image/?url=https%3A%2F%2Fcdn0.capterra-static.com%...14400.0 s1.3 KiB
edge.fullstory.com/s/fs.js3600.0 s0 B
edge.fullstory.com/s/fs.js3600.0 s0 B

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 245 ms

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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation3.4 s
Other1.4 s
Script Parsing & Compilation340 ms
Style & Layout156 ms
Garbage Collection148 ms
Parse HTML & CSS104 ms
Rendering88 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 49.2 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
●User Timing marks and measures 15 user timings
●Avoid long main-thread tasks 19 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 250 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
88

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.relative > div.flex > div.flex > button.cursor-default div.relative > div.flex > div.flex > button.cursor-default

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.

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
Crystal, a software advisor in Austin, TX, since 2014 div.mx-auto > div.flex-col > div.relative > div.text-right

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About Us Vendors div.absolute > div.rounded-bl-2xl > div.w-[137px] > ul
About Us Careers Vendors Blog View All Categories buyer-intent-view > footer#page-footer > div.page-container > ul.mb-4
X footer#page-footer > div.page-container > div.mb-6 > ul.mb-6
© 2006-2026 Software Advice, Inc. User Terms Vendor Terms Community Guidelines… footer#page-footer > div.page-container > div.mb-6 > ul.flex

These are opportunities to improve the experience of reading tabular or list data using 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
●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.
●Elements use only permitted ARIA attributes
●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.
●Links have a discernible name
●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.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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
○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.
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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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
Failed to load resource: net::ERR_CONNECTION_CLOSED
Failed to load resource: the server responded with a status of 400 ()
Failed to load resource: the server responded with a status of 400 ()
Failed to load resource: the server responded with a status of 400 ()
Failed to load resource: the server responded with a status of 400 ()
Not signed in with the identity provider.
●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
92

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`

Send Feedback