Homepage
https://ks-overlandpark.civicplus.pro/
Saved to: audits/KS-Overland Park/2026-03-30/f243b7c473/homepage
29 issues found
| Fixed | Issue | Category | WCAG | Found on | Responsibility | |
|---|---|---|---|---|---|---|
|
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements. |
Accessibility | WCAG 4.1.2 Level A | Mobile only | |||
|
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute. |
Accessibility | WCAG 1.1.1 Level A | Desktop only | |||
|
Uses deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs. |
Best Practices | Desktop & Mobile | ||||
|
Browser errors were logged to the console
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 |
Best Practices | Desktop & Mobile | ||||
|
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio. |
Best Practices | Desktop & Mobile | ||||
|
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images. |
Best Practices | Mobile only | ||||
|
Missing source maps for large first-party JavaScript
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. |
Best Practices | Desktop & Mobile | ||||
|
Reduce JavaScript execution time
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. |
Performance | Desktop & Mobile | ||||
|
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. Learn more about caching. |
Performance | Mobile only | ||||
|
Layout shift culprits
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. |
Performance | Desktop & Mobile | ||||
|
Forced reflow
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. |
Performance | Desktop & Mobile | ||||
|
Time to Interactive
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. |
Performance | Mobile only | ||||
|
Largest Contentful Paint
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric |
Performance | Mobile only | ||||
|
Avoid large layout shifts
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 |
Performance | Desktop & Mobile | ||||
|
LCP breakdown
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays. |
Performance | Desktop & Mobile | ||||
|
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading |
Performance | Desktop & Mobile | ||||
|
Legacy JavaScript
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 |
Performance | Mobile only | ||||
|
Minimize main-thread work
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 |
Performance | Desktop & Mobile | ||||
|
Max Potential First Input Delay
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. |
Performance | Mobile only | ||||
|
Network dependency tree
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. |
Performance | Desktop & Mobile | ||||
|
Render blocking requests
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. |
Performance | Desktop & Mobile | ||||
|
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric. |
Performance | Desktop & Mobile | ||||
|
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript. |
Performance | Desktop & Mobile | ||||
|
Reduce unused CSS
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. |
Performance | Desktop & Mobile | ||||
|
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript. |
Performance | Desktop & Mobile | ||||
|
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives. |
SEO | Desktop & Mobile | ||||
|
Links do not have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible. |
SEO | Desktop & Mobile | ||||
|
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description. |
SEO | Desktop & Mobile | ||||
|
All page content should be contained by landmarks
Ensure all page content is contained by landmarks |
Accessibility | axe-core |