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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.118439] map[node:map[boundingRect:map[bottom:1991 height:600 left:0 right:1350 top:1391 width:1350] lhId:page-4-DIV nodeLabel:div#app > div.uw-main-wr > div.page-home-v3 > div.lazyload-wrapper path:1,HTML,1,BODY,9,DIV,0,DIV,1,MAIN,3,DIV,1,DIV,0,DIV,2,DIV selector:div#app > div.uw-main-wr > div.page-home-v3 > div.lazyload-wrapper snippet:<div class="lazyload-wrapper "> type:node] score:0.114927] map[node:map[boundingRect:map[bottom:378 height:176 left:35 right:865 top:202 width:830] lhId:page-0-H1 nodeLabel:Next-gen web accessibility. path:1,HTML,1,BODY,9,DIV,0,DIV,1,MAIN,3,DIV,1,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,1,H1 selector:div.wrap > div.section__i > div.col > h1.section-title snippet:<h1 class="section-title"> type:node] score:0.002668] map[node:map[boundingRect:map[bottom:65 height:40 left:865 right:1310 top:25 width:445] lhId:page-1-DIV nodeLabel:Sign in Request a Demo Start Free Trial Language Select Language Select: option… path:1,HTML,1,BODY,9,DIV,0,DIV,1,MAIN,3,DIV,0,HEADER,1,DIV,2,DIV selector:div#app > header.header > div.header__i > div.header-actions snippet:<div class="header-actions"> type:node] score:0.000844 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:946 height:64 left:935 right:1075 top:882 width:140] lhId:page-32-IMG nodeLabel:Nikola Corporation logo path:1,HTML,1,BODY,9,DIV,0,DIV,1,MAIN,3,DIV,1,DIV,0,DIV,1,DIV,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,4,DIV,0,A,1,DIV,2,PICTURE,2,IMG selector:a > div.gatsby-image-wrapper > picture > img snippet:<img width="280" height="128" data-main-image="" style="object-fit: cover; opacity: 1;" sizes="(min-width: 280px) 280px, 100vw" decoding="async" loading="lazy" src="https://userway.org/static/1776234329489.397164628534/1ba57/nikola.avif" srcset="/static/1776234329489.397164628534/abae4/nikola.png 70w, /static/177623432…" alt="Nikola Corporation logo"> type:node]]] type:subitems]]]

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:9.577 source:map[column:142722 line:2 type:source-location url:https://userway.org/framework-d5756aaf228d29b881d6.js 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:5.38 source:map[column:420 line:0 type:source-location url:https://userway.org/component---src-pages-index-js-4970e5e832eae2c1ffd5.js urlProvider:network]] map[reflowTime:17.613 source:map[column:3663 line:0 type:source-location url:https://userway.org/component---src-pages-index-js-4970e5e832eae2c1ffd5.js urlProvider:network]] map[reflowTime:1.806 source:map[column:4537 line:0 type:source-location url:https://userway.org/default-ecfbff554e05b1522526.js urlProvider:network]] map[reflowTime:0.977 source:map[column:1435 line:1 type:source-location url:https://userway.org/8f10cc7f5f772f4e56c6c7d79c941fb2c43c2ede-4cc860f974c8d9592e88.js urlProvider:network]] map[reflowTime:0.16 source:map[column:155204 line:1 type:source-location url:https://userway.org/app-738d74483e5eb4ec24bb.js urlProvider:network]] map[reflowTime:37.785 source:map[type:text value:[unattributed]]] map[reflowTime:6.65 source:map[column:4087 line:0 type:source-location url:https://userway.org/80a25efd58c2fade0c7474dae763bd2faa0d3621-45ff4b25eae27e60ee9d.js urlProvider:network]] map[reflowTime:5.509 source:map[column:14434 line:1 type:source-location url:https://userway.org/Section2-56c07fb1436d954467ce.js urlProvider:network]]]

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

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
/uc.js?cbid=81afcafe-60a4-4250-81aa-d92dd2fe36d5&implemen...	1152.0 s	35.7 KiB
cdn.userway.org/widget.js	3600.0 s	1.6 KiB
cdn.userway.org/styles/2026-04-14-10-40-20/widget_base.css?v=1776163220800	864000.0 s	5.4 KiB
cdn.debugbear.com/CwAKgfflxXxd.js	14400.0 s	589 B
cdn.userway.org/frontend/stylesheets/flags.css?v=1776163220800	864000.0 s	3.0 KiB
cdn.userway.org/frontend/javascripts/languages.js?v=1776163220800	864000.0 s	2.3 KiB
cdn.userway.org/frontend/stylesheets/flags.css?v=1776163220800	864000.0 s	0 B

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
div#app > div.uw-main-wr > div.page-home-v3 > div.lazyload-wrapper `div#app > div.uw-main-wr > div.page-home-v3 > div.lazyload-wrapper`	0.115
Next-gen web accessibility. `div.wrap > div.section__i > div.col > h1.section-title`	0.003
Sign in Request a Demo Start Free Trial Language Select Language Select: option… `div#app > header.header > div.header__i > div.header-actions`	0.001

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: 40 ms 291.8 KiB

URL	Transfer Size	Est Savings
sgtm.userway.org/jmequjiw.js?st=WMW6857	172.5 KiB	76.9 KiB
userway.org/app-738d74483e5eb4ec24bb.js	140.3 KiB	60.8 KiB
cdn.amplitude.com/libs/analytics-browser-gtm-wrapper-3.11.4.js.br	40.3 KiB	32.8 KiB
/remediation/2026-04-14-10-40-20/contrast/remediation-too...	38.2 KiB	28.4 KiB
/81afcafe-60a4-4250-81aa-d92dd2fe36d5/cc.js?renew=false&r...	116.2 KiB	25.9 KiB
cdn.userway.org/widgetapp/2026-04-14-10-40-20/widget_app_base_1776163220800.js	47.1 KiB	23.1 KiB
/uc.js?cbid=81afcafe-60a4-4250-81aa-d92dd2fe36d5&implemen...	35.5 KiB	22.8 KiB
userway.org/f0e40d40b4c16607bd54ed05da8f46e12bd0a38d-ea20978fcbada3dccd30.js	43.5 KiB	21.0 KiB

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

URL	Transfer Size	Est Savings
userway.org/default.be26c3c1dc4c5c627d7a.css	16.1 KiB	15.1 KiB
#CybotCookiebotDialog ,#CybotCookiebotDialogBodyUnderlay {background:transparent; … } …	13.5 KiB	10.7 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.

	URL
Capterra logo `a > div.review-platforms__item__i > div.logo > img`	userway.org/static/capterra-2e102386dbd944674ce0e8ab45262340.svg

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

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,524 KiB

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 2 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 260 ms

●Server Backend Latencies 190 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 160 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(4.8) `div.review-platforms > div.review-platforms__i > div.review-platforms__item > a`
(4.8) `div.review-platforms > div.review-platforms__i > div.review-platforms__item > a`
(4.9) `div.review-platforms > div.review-platforms__i > div.review-platforms__item > a`
(8.8) `div.review-platforms > div.review-platforms__i > div.review-platforms__item > a`

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

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

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

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

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

○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

General

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	Map URL
sgtm.userway.org/jmequjiw.js?st=WMW6857
cdn.amplitude.com/libs/analytics-browser-gtm-2.11.10-min.js.gz	cdn.amplitude.com/libs/amplitude-gtm-min.js.map

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

100

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.

○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

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