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.

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:46.319 source:map[column:1131 line:1245 type:source-location url:https://www.sarasotarvrepair.com/ urlProvider:network]] map[reflowTime:45.546 source:map[type:text value:[unattributed]]]]

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

value: No additional origins are good candidates for preconnecting

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

Diagnostics

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.2 s	546 ms	0.0 ms
static.parastorage.com/unpkg/react@18.3.1/umd/react.production.min.js	698 ms	664 ms	0.7 ms
www.sarasotarvrepair.com/	649 ms	180 ms	27 ms
static.parastorage.com/services/wix-thunderbolt/dist/main.947b9813.bundle.min.js	109 ms	89 ms	9.9 ms
/services/wix-thunderbolt/dist/group_2.e9625588.chunk.min.js	98 ms	95 ms	3.1 ms
/services/wix-thunderbolt/dist/thunderbolt-commons.846b31...	85 ms	26 ms	9.2 ms
/services/wix-thunderbolt/dist/interactions.a313703f.chun...	59 ms	51 ms	7.7 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	2.0 s
Other	862 ms
Style & Layout	275 ms
Script Parsing & Compilation	181 ms
Parse HTML & CSS	77 ms
Garbage Collection	63 ms
Rendering	43 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 53.0 KiB

URL	Transfer Size	Est Savings
/* VSM_CSS */ @font-face {font-family: 'ibm-plex-sans...	27.2 KiB	15.1 KiB
._internalContainerRoot_ikbgu_1{position:relative;width:100%;height:100%;--borderTopWidth: 0px;--bo…	16.5 KiB	14.4 KiB
._internalContainerRoot_ikbgu_1{position:relative;width:100%;height:100%;--borderTopWidth: 0px;--bo…	14.9 KiB	13.2 KiB
/* VSM_CSS */ @font-face {font-family: 'din-next-w01-...	12.2 KiB	10.3 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.

Estimated savings: 0.0 ms 181.9 KiB

URL	Transfer Size	Est Savings
/services/wix-thunderbolt/dist/group_6.7a697b57.chunk.min.js	56.0 KiB	54.5 KiB
/services/wix-thunderbolt/dist/interactions.a313703f.chun...	36.8 KiB	28.6 KiB
/services/wix-thunderbolt/dist/motion.da8fd990.chunk.min.js	29.1 KiB	28.4 KiB
browser.sentry-cdn.com/7.120.3/bundle.tracing.es5.min.js	39.9 KiB	28.2 KiB
static.parastorage.com/services/wix-thunderbolt/dist/main.947b9813.bundle.min.js	55.1 KiB	21.9 KiB
/services/wix-thunderbolt/dist/thunderbolt-commons.846b31...	42.0 KiB	20.4 KiB

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

●Time to Interactive 2.1 s

●Max Potential First Input Delay 90 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 571 user timings

●Avoid long main-thread tasks 5 long tasks found

●Avoid non-composited animations 1 animated element 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 310 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 20 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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
Chassis & Mechanical Repair `div#comp-mpq2iu19 > div#comp-mpq2iu1a4 > div#comp-mpq2iu21 > h5`
The "Single Axle" Save `div#comp-mpq41ai9 > div#comp-mpq41aia4 > div#comp-mpq41ain > h5`
SARASOTA RV REPAIR `div#comp-kbgakxmn_r_comp-mpq2j2q5 > div#comp-kbgakxmn_r_comp-mpq2j2qa1 > div#comp-kbgakxmn_r_comp-mpq4fcat > h5`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●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

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`
/services/wix-thunderbolt/dist/group_3.ee39bdf0.chunk.min.js	`App not found for script Script not identified, errorId: 404C`

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