Lighthouse Mobile

· 0 checks — Mobile 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:1.479 source:map[column:20680 line:1 type:source-location url:https://wsv3cdn.audioeye.com/static-scripts/m/audioeye-scanner-esm/v11.2.36/audioeye-scanner-esm.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:40.823 source:map[column:24 line:15 type:source-location url:https://www.rescueairtx.com/common/usc/p/site-header.js urlProvider:network]] map[reflowTime:19.334 source:map[column:28 line:253 type:source-location url:https://www.rescueairtx.com/common/usc/p/site-header.js urlProvider:network]] map[reflowTime:49.284 source:map[type:text value:[unattributed]]] map[reflowTime:0.551 source:map[column:55 line:866 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-NN5D6GVE1H&cx=c&gtm=4e6992 urlProvider:network]] map[reflowTime:0.758 source:map[column:278 line:92 type:source-location url:https://www.google-analytics.com/analytics.js urlProvider:network]] map[reflowTime:1.317 source:map[column:3223 line:95 type:source-location url:https://wsv3cdn.audioeye.com/static-scripts/m/audioeye-scanner-esm/v11.2.36/audioeye-scanner-esm.js urlProvider:network]] map[reflowTime:0.162 source:map[column:6437 line:95 type:source-location url:https://wsv3cdn.audioeye.com/static-scripts/m/audioeye-scanner-esm/v11.2.36/audioeye-scanner-esm.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.

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

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
/signals/config/1221616505987980?v=2.9.398&r=stable&domai...	1200.0 s	135.8 KiB
stpaymentspciprod.blob.core.windows.net/webfields/1.0.52/webfields.js	0.0 ms	113.7 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	107.6 KiB
tag.unifyintent.com/v1/8rde8enSh7tog5RvC8MTk6/script.js	0.0 ms	30.3 KiB
/signals/config/1516053348513816?v=2.9.398&r=stable&domai...	1200.0 s	22.4 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
c.amazon-adsystem.com/aat/amzn.js	0.0 ms	11.4 KiB
wsv3cdn.audioeye.com/bootstrap.js?h=74112e1863a57ed19db66148a4e059aa	3600.0 s	12.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	20.6 KiB
collector-52421.us.tvsquared.com/tv2track.js	600.0 s	8.7 KiB
snap.licdn.com/li.lms-analytics/insight.old.min.js	86400.0 s	18.5 KiB
/v2/scripts/loader.js?h=74112e1863a57ed19db66148a4e059aa&...	60.0 s	7.0 KiB
embed.scheduler.servicetitan.com/scheduler-v1.js	300.0 s	7.0 KiB
analytics.scorpion.co/sa.js	0.0 ms	5.2 KiB
assets.calendly.com/assets/external/widget.js	300.0 s	4.9 KiB
cdn.tapad.app/js/dcs-xhr.js	3600.0 s	5.8 KiB
cdn01.basis.net/assets/up.js?um=1	0.0 ms	3.5 KiB
app.avoca.ai/chat-widget.js	86400.0 s	8.6 KiB
p.jmlp.app/sdk.js	14400.0 s	3.5 KiB
searchlight.partners/photon/photon-3p.js	0.0 ms	2.3 KiB
static.speetra.com/embed-pulsemweb-gsd.js	0.0 ms	1.6 KiB
px.premion.com/pixel.js?pxid=683d637ffdf708baa0e99725	0.0 ms	1.0 KiB
/collect?v=2&fmt=js&pid=6961516&time=1789087138115&url=ht...	0.0 ms	911 B
wsmcdn.audioeye.com/aem.js	120.0 s	675 B
/static-scripts/sites/74112e1863a57ed19db66148a4e059aa/ac...	60.0 s	369 B
/photon/service/pageload?i=d5722060-9427-4fd5-a89c-edbdb6...	0.0 ms	352 B
/tv2track.php?action_name=Heating%20%26%20Air%20Condition...	0.0 ms	276 B
/pixel?advertiserId=98374858-5549-4a30-85d5-06979636f27a&...	0.0 ms	148 B
/pixel?advertiserId=98374858-5549-4a30-85d5-06979636f27a&...	0.0 ms	22 B
/pixel?advertiserId=98374858-5549-4a30-85d5-06979636f27a&...	0.0 ms	20 B
/pixel?advertiserId=98374858-5549-4a30-85d5-06979636f27a&...	0.0 ms	20 B

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.

	URL	Resource Size	Est Savings
ul > li > div > video.full `ul > li > div > video.full`	/images/video-thumbnails/Screenshot-2023-06-09-at-12.16.4...	104.4 KiB	93.7 KiB
Rescue Air and Plumbing `div > div.flx > a.blk > img.dk-lg`	www.rescueairtx.com/images/brand/logo-dark.2402121012198.png	11.3 KiB	10.0 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

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

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.

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
/static-scripts/m/audioeye-scanner-esm/v11.2.36/audioeye-...	6.0 s	5.6 s	2.1 ms
www.rescueairtx.com/	1.8 s	69 ms	14 ms
Unattributable	1.2 s	83 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-NN5D6GVE1H&cx=c&gtm=4e6992	330 ms	261 ms	65 ms
connect.facebook.net/en_US/fbevents.js	302 ms	256 ms	38 ms
www.rescueairtx.com/common/usc/p/site-header.js	273 ms	30 ms	1.4 ms
/signals/config/1221616505987980?v=2.9.398&r=stable&domai...	266 ms	215 ms	36 ms
www.googletagmanager.com/gtm.js?id=GTM-P6NDVS9	265 ms	222 ms	33 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-09-08/startup.bundle.js	170 ms	126 ms	33 ms
/signals/config/1516053348513816?v=2.9.398&r=stable&domai...	108 ms	96 ms	11 ms
cdn.tapad.app/js/dcs-xhr.js	100 ms	69 ms	11 ms
www.google-analytics.com/analytics.js	97 ms	83 ms	6.5 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-09-08/compliance.bundle.js	90 ms	75 ms	4.7 ms
collector-52421.us.tvsquared.com/tv2track.js	81 ms	53 ms	1.8 ms
www.rescueairtx.com/cms/includes/0kmxd7x240l.2509161620371.js	60 ms	32 ms	1.7 ms
analytics.scorpion.co/sa.js	54 ms	49 ms	1.8 ms
p.jmlp.app/sdk.js	54 ms	43 ms	4.5 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	7.5 s
Other	2.2 s
Style & Layout	1.0 s
Script Parsing & Compilation	292 ms
Rendering	287 ms
Garbage Collection	127 ms
Parse HTML & CSS	106 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.6 KiB

URL	Transfer Size	Est Savings
www.rescueairtx.com/common/usc/p/poly.js	6.5 KiB	2.8 KiB
avoca.ai/chat-widget.js	8.3 KiB	2.8 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 10.8 KiB

URL	Transfer Size	Est Savings
www.rescueairtx.com/cms/includes/r5nrkaalj9d.2505230522090.css	17.7 KiB	10.8 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 309.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-NN5D6GVE1H&cx=c&gtm=4e6992	163.4 KiB	71.4 KiB
wsv3cdn.audioeye.com/static-scripts/v2/2026-09-08/startup.bundle.js	117.2 KiB	64.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-P6NDVS9	139.1 KiB	64.5 KiB
/static-scripts/m/audioeye-scanner-esm/v11.2.36/audioeye-...	105.3 KiB	37.0 KiB
/signals/config/1221616505987980?v=2.9.398&r=stable&domai...	135.6 KiB	36.1 KiB
connect.facebook.net/en_US/fbevents.js	107.5 KiB	35.4 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
www.rescueairtx.com/media/updated_banner(1080p).mp4	10.3 MiB
scheduler.servicetitan.com/_next/static/chunks/pages/_app-373747df3abf2470.js	261.2 KiB
app.avoca.ai/_next/static/immutable/chunks/41vss2l5xr3hu.js	183.7 KiB
www.googletagmanager.com/gtag/js?id=G-735HEPTKE0	176.6 KiB
www.googletagmanager.com/gtag/js?id=G-RREV0CM2VY&cx=c&gtm=4e6992	171.3 KiB
scheduler.servicetitan.com/_next/static/css/7730eee3896c4590.css	170.8 KiB
www.googletagmanager.com/gtag/js?id=G-NN5D6GVE1H&cx=c&gtm=4e6992	163.4 KiB
scheduler.servicetitan.com/_next/static/chunks/786-902c0ca7dfc51976.js	157.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-P6NDVS9	139.3 KiB
/signals/config/1221616505987980?v=2.9.398&r=stable&domai...	135.8 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
div.flx-at-1280 > div.two-thirds > picture.half > img.static-map `div.flx-at-1280 > div.two-thirds > picture.half > img.static-map`
Image `li.bg-bx > div.pd_v > div.flx > img.third`	www.rescueairtx.com/images/values/free-estimates.2103261819119.png
Image `li.bg-bx > div.pd_v > div.flx > img.third`	www.rescueairtx.com/images/values/upfront-pricing.2103261819126.png
Image `li.bg-bx > div.pd_v > div.flx > img.third`	www.rescueairtx.com/images/values/same-day.2103261819122.png
Rescue Air and Plumbing `div.flx-at-1280 > div.third > a.blk > img.lt-lg`	www.rescueairtx.com/images/brand/logo-light.2402121012199.png
Rescue Air and Plumbing `div > div.flx > a.blk > img.dk-lg`	www.rescueairtx.com/images/brand/logo-dark.2402121012198.png
Internet Marketing Experts `div.mn_ > div.mrg_tp > a.sd-lg > img.ta_`

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

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 125 animated elements found

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 490 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 280 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About Us Air Conditioning Heating Indoor Air Quality Plumbing Products Ser… `div.flx > nav.nv > nav#MblHeaderMobileNav > ul`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `nav#MblHeaderMobileNav > ul > li.selected > a.ato`
About Us `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Air Conditioning `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Heating `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Indoor Air Quality `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Plumbing `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Products `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Service Areas `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
View Exclusive Offers `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Get a Free Quote `nav#MblHeaderMobileNav > ul > li.flx > a.ato`
Contact Us `nav#MblHeaderMobileNav > ul > li.flx > a.ato`

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#HeaderZone > form#Form_HeaderS1 > div#HeaderS1 > a `header#HeaderZone > form#Form_HeaderS1 > div#HeaderS1 > a`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Main Menu `div#HeaderS1 > div > div.flx > div.mnu-btn`
Open child menu of About Us `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Air Conditioning `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Heating `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Indoor Air Quality `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Plumbing `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Products `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`
Open child menu of Service Areas `nav#MblHeaderMobileNav > ul > li.flx > span.el-tab`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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#chat-widget > div > div > button#btn-trigger-chat `div#chat-widget > div > div > button#btn-trigger-chat`

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#HeaderS1 > div > div.flx > a#HeaderS1_3 `div#HeaderS1 > div > div.flx > a#HeaderS1_3`

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
Call Us Today! `ul.third > li > div#FooterV1Tagline > span.fnt_t-6`
Map & Directions `li > div.flx-at-1280 > div.mrg_tp-20 > a`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `nav.nv > nav#MblHeaderMobileNav > ul > li.selected`
About Us `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Air Conditioning `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Heating `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Indoor Air Quality `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Plumbing `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Products `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Service Areas `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
View Exclusive Offers `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Get a Free Quote `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`
Contact Us `nav.nv > nav#MblHeaderMobileNav > ul > li.flx`

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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA `tooltip` elements have accessible names

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields 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

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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

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

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
/accounts/111/tags/ZmVFSU1/events?referrer_url=&page_url=...	`Failed to load resource: the server responded with a status of 400 ()`
/accounts/111/tags/ZmVFSU1/events?referrer_url=&page_url=...	`Failed to load resource: the server responded with a status of 400 ()`
/accounts/111/tags/ZmVFSU1/events?referrer_url=&page_url=...	`Failed to load resource: the server responded with a status of 400 ()`
/accounts/111/tags/ZmVFSU1/events?referrer_url=&page_url=...	`Failed to load resource: the server responded with a status of 400 ()`
www.rescueairtx.com/ line 2197, col 178	`TypeError: Failed to construct 'URL': Invalid URL at https://www.rescueairtx.com/:2198:179 at https://www.rescueairtx.com/:2198:615`

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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

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.vid-bg > ul.flx > li > a.vid-btn`

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

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`