https://www.pestauthority.com/sioux-falls-sd/

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.

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
fonts.gstatic.com/s/dmsans/v17/rP2Fp2ywxg089UriCZa4Hz-DJF4e8A.woff2	125 ms
fonts.gstatic.com/s/dmsans/v17/rP2Hp2ywxg089UriCZOIHTWEBlw.woff2	115 ms
fonts.gstatic.com/s/robotoslab/v36/BngMUXZYTXPIvIBgJJSb6ufN5qWr4xCC.woff2	115 ms

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
div#SmPackagesV2Packages > div.pd-cst > div.ta_ > img.m-ato `div#SmPackagesV2Packages > div.pd-cst > div.ta_ > img.m-ato`	www.pestauthority.com/assets/packages/AdvantageLogo-White.png.2604140816147.webp	13.5 KiB	7.5 KiB

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

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
www.pestauthority.com/cms/includes/x2z4a0r4qzi.2605111529366.css	31.1 KiB	563 ms
/css2?family=DM+Sans:ital,opsz,wght@0,9..40,100..1000;1,9...	1.2 KiB	870 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
wsv3cdn.audioeye.com/bootstrap.js?h=39e62a75594c980d0d23bd69876630e7	3600.0 s	9.3 KiB
/v2/scripts/loader.js?h=39e62a75594c980d0d23bd69876630e7&...	60.0 s	7.1 KiB
analytics.scorpion.co/sa.js	0.0 ms	4.9 KiB
wsmcdn.audioeye.com/aem.js	120.0 s	669 B
/static-scripts/sites/39e62a75594c980d0d23bd69876630e7/ac...	60.0 s	400 B
www.pestauthority.com/cms/svg/site/icon_light_package.24.ffffff.svg	604792.0 s	1.7 KiB
www.pestauthority.com/cms/svg/site/icon_dark_package.24.ffffff.svg	604792.0 s	1.7 KiB
www.pestauthority.com/cms/svg/site/icon_check_mark.24.ffffff.svg	604792.0 s	948 B

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

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.1.16/audioeye-...	5.0 s	4.8 s	1.6 ms
www.pestauthority.com/sioux-falls-sd/	1.5 s	40 ms	9.6 ms
Unattributable	574 ms	80 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-9NWCNB7NQB&cx=c&gtm=4e65l0h2	352 ms	251 ms	62 ms
www.googletagmanager.com/gtm.js?id=GTM-KGLQ5B6	344 ms	288 ms	43 ms
www.googletagmanager.com/gtag/js?id=G-H5GMNNZ829&cx=c&gtm=4e65l0h2	257 ms	203 ms	52 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-05-22/startup.bundle.js	186 ms	141 ms	35 ms
scorpionconnect.scorpion.co/static/js/main.3848689d.js	161 ms	144 ms	12 ms
wsv3cdn.audioeye.com/static-scripts/v2/2026-05-22/compliance.bundle.js	76 ms	66 ms	5.2 ms
www.pestauthority.com/cms/includes/h07aqls6m8p.2604270852235.js	65 ms	34 ms	2.4 ms
scorpionconnect.scorpion.co/static/js/2425.8e1f63cb.chunk.js	59 ms	55 ms	1.0 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	6.2 s
Style & Layout	1.2 s
Other	726 ms
Rendering	245 ms
Script Parsing & Compilation	239 ms
Garbage Collection	97 ms
Parse HTML & CSS	69 ms

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

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-9NWCNB7NQB&cx=c&gtm=4e65l0h2	176.0 KiB	71.5 KiB
wsv3cdn.audioeye.com/static-scripts/v2/2026-05-22/startup.bundle.js	125.3 KiB	69.6 KiB
www.googletagmanager.com/gtag/js?id=G-H5GMNNZ829&cx=c&gtm=4e65l0h2	157.5 KiB	68.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KGLQ5B6	156.2 KiB	54.3 KiB
/static-scripts/m/audioeye-scanner-esm/v11.1.16/audioeye-...	85.9 KiB	33.0 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
Pest Authority of Sioux Falls, SD `div.flx > div.flx > a.blk > img.lt-lg`	www.pestauthority.com/images/brand/Logo-version-Dark-Mode.2603040823004.svg
Pest Authority of Sioux Falls, SD `div.mn_ > div.fit > a.blk > img.dk-lg`	www.pestauthority.com/images/brand/Logo-version-Normal.2603040823014.svg
div#SmPackagesV2Packages > div.pd-cst > div.ta_ > img.m-ato `div#SmPackagesV2Packages > div.pd-cst > div.ta_ > img.m-ato`	www.pestauthority.com/assets/packages/AdvantageLogo-White.png.2604140816147.webp

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●Avoid long main-thread tasks 18 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 150 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 260 ms

●Avoid large layout shifts 2 layout shifts 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
FAQs About Us Services Industries We Serve Bundles Promotions `div.flx > div#SmLocalHeaderV1MobileNav > nav.mbl-nv > 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
FAQs `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`
About Us `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`
Services `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`
Industries We Serve `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`
Bundles `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`
Promotions `nav.mbl-nv > ul > li.bdr_bt > a.fnt_nv-pry`

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
body > main#MainZone > section#CuratedReviewsF1 > a#ReviewsAnchor `body > main#MainZone > section#CuratedReviewsF1 > a#ReviewsAnchor`

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
Map of Pest Authority of Sioux Falls, SD Services in Sioux Falls and Surroundin… `div#SmFranServiceAreasV1Locations > div > figure.map > div.imap`

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#CuratedReviewsF1Feed > div#Review-7830412 > div.mn_tn > button.blk `div#CuratedReviewsF1Feed > div#Review-7830412 > div.mn_tn > button.blk`
div#CuratedReviewsF1Feed > div#Review-7830423 > div.mn_tn > button.blk `div#CuratedReviewsF1Feed > div#Review-7830423 > div.mn_tn > button.blk`
div#CuratedReviewsF1Feed > div#Review-7830431 > div.mn_tn > button.blk `div#CuratedReviewsF1Feed > div#Review-7830431 > div.mn_tn > button.blk`
div#CuratedReviewsF1Feed > div#Review-7830421 > div.mn_tn > button.blk `div#CuratedReviewsF1Feed > div#Review-7830421 > div.mn_tn > button.blk`

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

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 `ul.ctas > li.cta-item-container > a.call-btn > strong`
Text `ul.ctas > li.cta-item-container > button.cta-button > strong.cta-label`
Email `ul.ctas > li.cta-item-container > button.cta-button > strong.cta-label`

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
FAQs `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`
About Us `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`
Services `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`
Industries We Serve `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`
Bundles `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`
Promotions `div#SmLocalHeaderV1MobileNav > nav.mbl-nv > ul > li.bdr_bt`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Read More `li.flx > blockquote.rvw-itm > div > button.lnk-stl`
Read More `li.flx > blockquote.rvw-itm > div > button.lnk-stl`
Read More `li.flx > blockquote.rvw-itm > div > button.lnk-stl`
Read More `li.flx > blockquote.rvw-itm > div > button.lnk-stl`

○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

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

●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

●No form fields have multiple labels

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

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

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

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

100

Best Practices

●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

●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

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`