Skip to content
https://www.cattailsenvironmental.com

Lighthouse Mobile

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

47

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 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
/files/theme/fonts/8344e877-560d-44d4-82eb-9822766676f9.w...0.0 ms25.2 KiB
/files/theme/fonts/92b66dbd-4201-4ac2-a605-4d4ffc8705cc.w...0.0 ms24.9 KiB
/files/theme/fonts/f26faddb-86cc-4477-a253-1e1287684336.w...0.0 ms24.7 KiB
/files/theme/fonts/b28b01d9-78c5-46c6-a30d-9a62c8f407c5.t...0.0 ms23.7 KiB
/files/theme/fonts/18839597-afa8-4f0b-9abb-4a30262d0da8.t...0.0 ms23.3 KiB
/files/theme/fonts/63a74598-733c-4d0c-bd91-b01bffcd6e69.t...0.0 ms23.0 KiB
/files/theme/fonts/1e9892c0-6927-4412-9874-1b82801ba47a.w...0.0 ms20.7 KiB
/files/theme/fonts/46cf1067-688d-4aab-b0f7-bd942af6efd8.t...0.0 ms19.6 KiB
/files/theme/fonts/3f380a53-50ea-4a62-95c5-d5d8dba03ab8.w...0.0 ms19.1 KiB
/files/theme/fonts/7377dbe6-f11a-4a05-b33c-bc8ce1f60f84.w...0.0 ms18.9 KiB
/files/theme/fonts/627fbb5a-3bae-4cd9-b617-2f923e29d55e.w...0.0 ms18.7 KiB
/files/theme/fonts/2cd55546-ec00-4af9-aeca-4a3cd186da53.w...0.0 ms17.2 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
www.cattailsenvironmental.com/files/theme/plugins.js?15659696340.0 ms15.6 KiB
cdn2.editmysite.com/js/site/main-customer-accounts-site.js?buildtime=17827416411209600.0 s155.8 KiB
cdn11.editmysite.com/js/site/main.js?buildtime=17827416411209600.0 s144.7 KiB
ssl.google-analytics.com/ga.js7200.0 s17.4 KiB
www.cattailsenvironmental.com/files/main_style.css?17827649170.0 ms7.3 KiB
cdn.ywxi.net/meter/cattailsenvironmental.com/205.svg?ts=1785480494949&l=en3595.0 s7.6 KiB
cdn.trustedsite.com/js/1.js3600.0 s5.4 KiB
cdn.ywxi.net/js/1.js3600.0 s5.4 KiB
cdn2.editmysite.com/js/lang/en/stl.js?buildTime=1782741641&1209600.0 s33.9 KiB
cdn11.editmysite.com/js/jquery-1.8.3.min.js1209600.0 s33.0 KiB
cdn11.editmysite.com/css/sites.css?buildtime=17827416411209600.0 s29.5 KiB
www.cattailsenvironmental.com/files/theme/custom.js?15659696340.0 ms2.2 KiB
www.cattailsenvironmental.com/files/templateArtifacts.js?17827649170.0 ms1.8 KiB
cdn2.editmysite.com/fonts/Montserrat/bold.woff21209600.0 s13.0 KiB
cdn2.editmysite.com/fonts/Montserrat/regular.woff21209600.0 s12.9 KiB
/rpc/tmjs/cattailsenvironmental.com/visit?rand=1786018552...0.0 ms571 B
cdn.ywxi.net/app/weebly/trustmark.js?weeblySiteId=49430770036777982186400.0 s987 B
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....172794.0 s809 B
cdn11.editmysite.com/css/social-icons.css?buildtime=17827416411209600.0 s1.9 KiB
cdn11.editmysite.com/css/old/fancybox.css?buildtime=17827416411209600.0 s1.5 KiB
cdn2.editmysite.com/fonts/Montserrat/font.css?21209600.0 s738 B
cdn2.editmysite.com/fonts/Oswald/font.css?21209600.0 s585 B

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:50.238 source:map[column:9837 line:2 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.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:47.879 source:map[column:21731 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.319 source:map[column:21828 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.119 source:map[column:22058 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.099 source:map[column:22485 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.185 source:map[column:22640 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.142 source:map[column:22785 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.181 source:map[column:27247 line:14 type:source-location url:https://cdn11.editmysite.com/js/site/main.js?buildtime=1782741641 urlProvider:network]] map[reflowTime:0.313 source:map[column:76049 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.83 source:map[column:75373 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.117 source:map[column:91186 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js urlProvider:network]] map[reflowTime:0.054 source:map[column:92807 line:1 type:source-location url:https://cdn11.editmysite.com/js/jquery-1.8.3.min.js 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
div.banner-wrap > div.wsite-elements > div.wsite-section-wrap > div.wsite-section div.banner-wrap > div.wsite-elements > div.wsite-section-wrap > div.wsite-section
/uploads/5/3/6/8/53681221/background-images/1121585272.jpg131.1 KiB61.5 KiB
wide leaved cattail photo div > div.wsite-image > a.w-fancybox > img
/uploads/5/3/6/8/53681221/editor/1239140.jpg?153660735954.9 KiB23.8 KiB
Picture div > div.wsite-image > a.w-fancybox > img
/uploads/5/3/6/8/53681221/editor/certification-badge-2023...14.0 KiB10.4 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
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

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

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: 150 ms 8.1 KiB
URLTransfer SizeEst Savings
www.cattailsenvironmental.com/files/theme/plugins.js?156596963415.4 KiB8.1 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: 300 ms 28.7 KiB
URLTransfer SizeEst Savings
cdn11.editmysite.com/css/sites.css?buildtime=178274164129.0 KiB28.7 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.

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.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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
wide leaved cattail photo div > div.wsite-image > a.w-fancybox > img
/uploads/5/3/6/8/53681221/editor/1239140.jpg?1536607359
Picture div > div.wsite-image > a > img
/uploads/5/3/6/8/53681221/published/taglogo.jpg?1779131636
Picture div > div.wsite-image > a.w-fancybox > img
/uploads/5/3/6/8/53681221/editor/certification-badge-2023...
Picture div > div.wsite-image > a > img
/uploads/5/3/6/8/53681221/published/facebook-image.jpg?17...
Picture div > div.wsite-image > a > img
www.cattailsenvironmental.com/uploads/5/3/6/8/53681221/linkedin-image_orig.jpg

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 1,182 KiB
●JavaScript execution time 1.0 s
●Minimizes main-thread work 1.8 s
●Avoid long main-thread tasks 6 long tasks found
●Network Requests
●Network Round Trip Times 170 ms
●Server Backend Latencies 180 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 210 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
95

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.

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
Statement of Qualifications h2.wsite-content-title > strong > font > a
jodieburns@cattailsenvironmental.com td.wsite-multicol-col > h2.wsite-content-title > strong > font
Providing Wetlands & Environmental Consulting Services Nationwide - div.paragraph > strong > font > font
Arkansas, Oklahoma, Kansas, & Missouri div.paragraph > strong > font > font
A few WOTUS terms defined per the pre-2015 regulations, guidance documents, and… div.paragraph > em > strong > font
Recent Significant WOTUS Dates - div.wsite-section-elements > div.paragraph > strong > font

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[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 use only permitted ARIA attributes
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○Buttons have an accessible name
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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
○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.
81

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
chrome.loadTimes() is deprecated, instead use standardized API: Paint Timing.
●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 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
●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
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`

Send Feedback