Homepage
https://www.greensboro-nc.gov
Saved to: audits/NC-Greensboro/2026-03-30/d0cf591298/homepage
32 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 | Desktop & Mobile | |||
|
`[role]`s are not contained by their required parent element
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. |
Accessibility | WCAG 1.3.1 Level A | Desktop & Mobile | |||
|
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 & Mobile | |||
|
Document does not have a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks. |
Accessibility | Desktop & Mobile | ||||
|
Links do not have a discernible name
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. |
Accessibility | WCAG 2.4.4 Level A | Desktop & Mobile | |||
|
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure. |
Accessibility | WCAG 1.3.1 Level A | Desktop & Mobile | |||
|
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets. |
Accessibility | WCAG 2.5.8 | Desktop only | |||
|
Uses deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs. |
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 | Desktop & Mobile | ||||
|
First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric. |
Performance | Mobile only | ||||
|
Font display
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. |
Performance | Mobile only | ||||
|
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 | ||||
|
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size |
Performance | Mobile only | ||||
|
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 | ||||
|
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 | Desktop & Mobile | ||||
|
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 | ||||
|
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 | ||||
|
Links are not crawlable
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 |
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 | ||||
|
<html> element must have a lang attribute
Ensure every HTML document has a lang attribute |
Accessibility | WCAG 3.1.1 | axe-core | |||
|
All page content should be contained by landmarks
Ensure all page content is contained by landmarks |
Accessibility | axe-core |
Interior Page
https://www.greensboro-nc.gov/services/city-assistance-programs/classes-field-trips-for-schools
Saved to: audits/NC-Greensboro/2026-03-30/d0cf591298/interior
23 issues found
| Fixed | Issue | Category | WCAG | Found on | Responsibility | |
|---|---|---|---|---|---|---|
|
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets. |
Accessibility | WCAG 2.5.8 | Desktop & Mobile | |||
|
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 | Mobile only | ||||
|
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio. |
Best Practices | Desktop & Mobile | ||||
|
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 | Desktop & Mobile | ||||
|
First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric. |
Performance | Mobile only | ||||
|
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 | Mobile only | ||||
|
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size |
Performance | Desktop & Mobile | ||||
|
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 | ||||
|
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading |
Performance | Desktop only | ||||
|
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 | Desktop & Mobile | ||||
|
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 | ||||
|
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 | ||||
|
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 | ||||
|
Links are not crawlable
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 |
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 | ||||
|
<html> element must have a lang attribute
Ensure every HTML document has a lang attribute |
Accessibility | WCAG 3.1.1 | axe-core | |||
|
Document should have one main landmark
Ensure the document has a main landmark |
Accessibility | axe-core | ||||
|
All page content should be contained by landmarks
Ensure all page content is contained by landmarks |
Accessibility | axe-core |