Skip to content
https://www.henrycountyva.gov

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.

23

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.28971794013611396] map[node:map[boundingRect:map[bottom:944 height:620 left:0 right:412 top:324 width:412] lhId:page-4-DIV nodeLabel:div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS path:1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,1,DIV,3,DIV selector:div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS snippet:<div data-cprole="structuralContainer" id="bannerContainerTS" class="noOverflowTS"> type:node] score:0.2137575523396892 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/muli/v34/7Auwp_0qiz-afTLGLQjUwkQ.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/muli/v34/7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVw1qBrzI.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:944 height:620 left:0 right:412 top:324 width:412] lhId:page-4-DIV nodeLabel:div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS path:1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,1,DIV,3,DIV selector:div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS snippet:<div data-cprole="structuralContainer" id="bannerContainerTS" class="noOverflowTS"> type:node] score:0.07596038779642472]]

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.

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:39.336 source:map[column:302 line:29 type:source-location url:https://www.henrycountyva.gov/Assets/Mystique/Shared/Scripts/webfontloader/webfont.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:35.329 source:map[column:543 line:21 type:source-location url:https://www.henrycountyva.gov/Assets/Mystique/Shared/Scripts/webfontloader/webfont.js urlProvider:network]] map[reflowTime:4.007 source:map[column:31 line:24 type:source-location url:https://www.henrycountyva.gov/Assets/Mystique/Shared/Scripts/webfontloader/webfont.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#bannerContainerTS2 > div#banner2 > div#bannerDivbanner2 > img.bannerObject div#bannerContainerTS2 > div#banner2 > div#bannerDivbanner2 > img.bannerObject
www.henrycountyva.gov/ImageRepository/Document?documentID=81586.6 KiB156.9 KiB
div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
www.henrycountyva.gov/ImageRepository/Document?documentID=66231.5 KiB49.9 KiB
Notify Me Icon td > p > a > img.fr-dib
www.henrycountyva.gov/ImageRepository/Document?documentId=69313.8 KiB13.2 KiB
Home Page div.siteWrap3 > div#bannerLogoTS > a#bannerLogoTS-58 > img.bannerObject
www.henrycountyva.gov/ImageRepository/Document?documentID=677.9 KiB6.3 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:635.68 label:Time to first byte subpart:timeToFirstByte] map[duration:1730.966 label:Resource load delay subpart:resourceLoadDelay] map[duration:137.48500003051757 label:Resource load duration subpart:resourceLoadDuration] map[duration:22.03499996948242 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-IMG
nodeLabel: div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,1,DIV,3,DIV,0,DIV,2,DIV,0,IMG
selector: div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
snippet: <img class="bannerObject" width="412px" style="position: absolute; left: 0px; margin: 0px; width: 1948.57px; z-index: 3;" src="/ImageRepository/Document?documentID=66" data-is-delayed="false" alt="">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
path: 1,HTML,1,BODY,16,DIV,0,DIV,1,DIV,1,DIV,3,DIV,0,DIV,2,DIV,0,IMG
selector: div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
snippet: <img class="bannerObject" width="412px" style="position: absolute; left: 0px; margin: 0px; width: 1948.57px; z-index: 3;" src="/ImageRepository/Document?documentID=66" data-is-delayed="false" alt="">

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

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.

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.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS
0.214
div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS div#inner-wrap > div#bodyWrapper > div#bodyContainerTS > div#bannerContainerTS
0.076

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.

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

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.

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: 310 ms 98.2 KiB
URLTransfer SizeEst Savings
www.henrycountyva.gov/-2140275272.css58.0 KiB54.5 KiB
www.henrycountyva.gov/-1051354151.css47.8 KiB43.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.

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.

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.

CategoryTime Spent
Script Evaluation3.1 s
Style & Layout1.7 s
Other780 ms
Script Parsing & Compilation235 ms
Rendering220 ms
Parse HTML & CSS114 ms

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
The page has an unload handler in the main frame.Actionable
The page has an unload handler in a sub frame.Actionable
An iframe on the page started a navigation that did not complete.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
a white van ol.semanticList > li.widgetItem > a > img.media
www.henrycountyva.gov/ImageRepository/Document?documentID=1796
people race through a pit full of mud ol.semanticList > li.widgetItem > a > img.media
www.henrycountyva.gov/ImageRepository/Document?documentID=1710
Notify Me Icon td > p > a > img.fr-dib
www.henrycountyva.gov/ImageRepository/Document?documentId=693
News Placeholder ol.semanticList > li.widgetItem > a > img.media
www.henrycountyva.gov/ImageRepository/Document?documentID=87
News Placeholder ol.semanticList > li.widgetItem > a > img.media
www.henrycountyva.gov/ImageRepository/Document?documentID=87
Henry County Home Page ol.pageStyles > li.InfoAdvanced > p > img.fr-dib
www.henrycountyva.gov/ImageRepository/Document?documentId=80
Search section#widgetPreviewSearch > div.widgetBody > a#btnSearchIcon > img.imageHover
www.henrycountyva.gov/ImageRepository/Document?documentID=69
Facebook ul.semanticList > li.widgetItem > a.widgetDesc > img.graphicButtonLink
www.henrycountyva.gov/ImageRepository/Document?documentID=40
Twitter ul.semanticList > li.widgetItem > a.widgetDesc > img.graphicButtonLink
www.henrycountyva.gov/ImageRepository/Document?documentID=42
Instagram ul.semanticList > li.widgetItem > a.widgetDesc > img.graphicButtonLink
www.henrycountyva.gov/ImageRepository/Document?documentID=41
YouTube ul.semanticList > li.widgetItem > a.widgetDesc > img.graphicButtonLink
www.henrycountyva.gov/ImageRepository/Document?documentID=43
Linkedin ul.semanticList > li.widgetItem > a.widgetDesc > img.graphicButtonLink
www.henrycountyva.gov/ImageRepository/Document?documentID=44
everbrige tr > td > a > img.fr-dib
www.henrycountyva.gov/ImageRepository/Document?documentId=1616
a map with red shading indicating areas of the county with internet access ol.semanticList > li.widgetItem > a > img.media
data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
a group photo of an award presentation ol.semanticList > li.widgetItem > a > img.media
data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
a flyer with a retro movie poster design advertising upcoming movies to be show… ol.semanticList > li.widgetItem > a > img.media
data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
people race through a pit full of mud ol.semanticList > li.widgetItem > a > img.media
data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7

More information about the performance of your application. These numbers don't directly affect the Performance score.

Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoid long main-thread tasks 8 long tasks found
Network Requests
Network Round Trip Times 130 ms
Server Backend Latencies 380 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 370 ms
INP breakdown
User Timing marks and measures
Avoid non-composited animations
85

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
Menu div#outer-wrap > div#inner-wrap > div#divToolbars > a#nav-open-btn

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Government Departments Doing Business How Do I... div#mainNavHolderMobile > nav#mainNav > div#rwd-menu > ol#mainNavMenu

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#customHtmlbf779f56-ba2c-40ab-9635-fd5228c1e89d > div > div.facebook-container > iframe div#customHtmlbf779f56-ba2c-40ab-9635-fd5228c1e89d > div > div.facebook-container > iframe

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
Menu div#outer-wrap > div#inner-wrap > div#divToolbars > a#nav-open-btn

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Emergency Alerts tbody > tr > td > h3.subhead2
Smith River Fest Returns August 22 for 18th Year ol.semanticList > li.widgetItem > div.text > h4#newsFlashItemHeader136
AUGUST 2026 div.calendarInnerWrapper > div.miniCalendar > h3.miniCalendarHeader > span#miniCalendarHeaderf56a0008-c040-4a85-8dde-816410c264a9

These are opportunities to improve keyboard navigation in your application.

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]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
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>`).
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.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Uses ARIA roles only on compatible elements
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
No form fields have multiple labels
`<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.
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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
77

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject div#bannerContainerTS > div#banner1 > div#bannerDivbanner1 > img.bannerObject
www.henrycountyva.gov/ImageRepository/Document?documentID=65412 x 700 (0.59)2200 x 700 (3.14)

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
Unload event listeners are deprecated and will be removed.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
28Sitemap: /sitemap.xmlInvalid sitemap URL

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
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback