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.

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
/nc/styles/site_page_main_image/public/images/2026-03/spr...	0.0 ms	457.7 KiB
/nc/styles/article_card/public/images/2021-11/hiking fami...	0.0 ms	225.2 KiB
/nc/styles/article_card/public/images/2025-09/welcome-to-...	0.0 ms	156.4 KiB
/nc/images/2025-03/NC-Capital-Dusk.jpg?VersionId=Mrb.15De...	0.0 ms	135.6 KiB
files.nc.gov/nc/images/2021-11/nc_flag.jpg	0.0 ms	132.7 KiB
/nc/styles/article_card/public/images/2026-01/america-250...	0.0 ms	121.1 KiB
/nc/images/2021-11/about_band_bg.jpg?VersionId=UyHhqXHl.0...	0.0 ms	47.4 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
files.nc.gov/nc/ncgov_250X75_2.png?VersionId=AOYQRfbcGNZoeheprjcrNNpqiO9gfLsJ	0.0 ms	6.2 KiB
www.nc.gov/core/assets/vendor/jquery/jquery.min.js?v=3.7.1	1209600.0 s	30.3 KiB
www.nc.gov/core/misc/ajax.js?v=10.6.3	1209600.0 s	17.1 KiB
static.addtoany.com/menu/page.js	86400.0 s	2.2 KiB
files.nc.gov/nc/images/2021-09/arrow-90deg-right.png	0.0 ms	721 B
www.nc.gov/core/misc/drupal.js?v=10.6.3	1209600.0 s	6.6 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/resizable-min.js?v=10.6.3	1209600.0 s	6.1 KiB
www.nc.gov/core/misc/position.js?v=10.6.3	1209600.0 s	6.1 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/draggable-min.js?v=10.6.3	1209600.0 s	5.3 KiB
www.nc.gov/modules/contrib/linkpurpose/library/js/linkpurpose.min.js?td91kj	1209600.0 s	4.9 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/dialog-min.js?v=10.6.3	1209600.0 s	4.4 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widget-min.js?v=10.6.3	1209600.0 s	3.7 KiB
www.nc.gov/core/misc/dialog/dialog.ajax.js?v=10.6.3	1209600.0 s	3.5 KiB
www.nc.gov/core/misc/displace.js?v=10.6.3	1209600.0 s	3.1 KiB
www.nc.gov/core/assets/vendor/tabbable/index.umd.min.js?v=6.3.0	1209600.0 s	3.0 KiB
www.nc.gov/core/misc/message.js?v=10.6.3	1209600.0 s	2.9 KiB
www.nc.gov/modules/contrib/linkpurpose/js/linkpurpose-drupal.js?td91kj	1209600.0 s	2.8 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/button-min.js?v=10.6.3	1209600.0 s	2.5 KiB
www.nc.gov/modules/contrib/google_analytics/js/google_analytics.js?v=10.6.3	1209600.0 s	2.4 KiB
www.nc.gov/core/assets/vendor/tua-body-scroll-lock/tua-bsl.umd.min.js?v=10.6.3	1209600.0 s	2.4 KiB
www.nc.gov/core/misc/progress.js?v=10.6.3	1209600.0 s	2.2 KiB
www.nc.gov/core/misc/announce.js?v=10.6.3	1209600.0 s	2.2 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/controlgroup-min.js?v=10.6.3	1209600.0 s	2.2 KiB
www.nc.gov/core/misc/dialog/dialog.position.js?v=10.6.3	1209600.0 s	2.1 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/checkboxradio-min.js?v=10.6.3	1209600.0 s	2.0 KiB
www.nc.gov/themes/custom/nc_barrio/src/js/modules/nc.fileicons.js?v=1	1209600.0 s	1.9 KiB
www.nc.gov/core/misc/dialog/dialog.js?v=10.6.3	1209600.0 s	1.8 KiB
www.nc.gov/modules/contrib/webform/js/webform.dialog.js?v=10.6.3	1209600.0 s	1.7 KiB
/modules/contrib/clientside_validation/clientside_validat...	1209600.0 s	1.7 KiB
www.nc.gov/modules/custom/nc_bootstrap/js/portal-search.js?v=1.7	1209600.0 s	1.6 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/widgets/mouse-min.js?v=10.6.3	1209600.0 s	1.6 KiB
www.nc.gov/themes/custom/nc_barrio/js/modules/nc.analytics.js?v=1.87	1209600.0 s	1.6 KiB
www.nc.gov/core/assets/vendor/loadjs/loadjs.min.js?v=4.3.0	1209600.0 s	1.6 KiB
www.nc.gov/core/misc/drupal.init.js?v=10.6.3	1209600.0 s	1.5 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/focusable-min.js?v=10.6.3	1209600.0 s	1.4 KiB
www.nc.gov/themes/custom/nc_barrio/js/modules/nc.search.js?v=1.87	1209600.0 s	1.4 KiB
www.nc.gov/core/misc/dialog/dialog.jquery-ui.js?v=10.6.3	1209600.0 s	1.4 KiB
www.nc.gov/core/modules/ckeditor5/js/ckeditor5.dialog.fix.js?v=10.6.3	1209600.0 s	1.4 KiB
www.nc.gov/themes/custom/nc_barrio/js/modules/textEditorDatatables.js?v=1.9	1209600.0 s	1.3 KiB
www.nc.gov/core/assets/vendor/once/once.min.js?v=1.0.1	1209600.0 s	1.3 KiB
www.nc.gov/themes/custom/nc_barrio/js/global.js?v=1.87	1209600.0 s	1.3 KiB
www.nc.gov/modules/custom/ncalert/js/ncalerts.js?v=16	1209600.0 s	1.3 KiB
/modules/custom/nc_table_accessibility/js/default_table_h...	1209600.0 s	1.3 KiB
www.nc.gov/modules/contrib/webform/js/webform.drupal.dialog.js?v=10.6.3	1209600.0 s	1.3 KiB
www.nc.gov/themes/custom/nc_barrio/js/modules/nc.gtranslate.js?v=1.5	1209600.0 s	1.2 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/scroll-parent-min.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/labels-min.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/core/misc/drupalSettingsLoader.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/core/misc/debounce.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/themes/contrib/bootstrap_barrio/js/messages.js?td91kj	1209600.0 s	1.2 KiB
www.nc.gov/modules/custom/nc_breadcrumb/js/nc_breadcrumb.js?td91kj	1209600.0 s	1.2 KiB
www.nc.gov/themes/contrib/bootstrap_barrio/js/barrio.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/disable-selection-min.js?v=10.6.3	1209600.0 s	1.2 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/jquery-patch-min.js?v=10.6.3	1209600.0 s	1.1 KiB
/modules/contrib/clientside_validation/clientside_validat...	1209600.0 s	1.1 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/unique-id-min.js?v=10.6.3	1209600.0 s	1.1 KiB
www.nc.gov/core/misc/dialog/dialog-deprecation.js?v=10.6.3	1209600.0 s	1.1 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/keycode-min.js?v=10.6.3	1209600.0 s	1.0 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/form-reset-mixin-min.js?v=10.6.3	1209600.0 s	1.0 KiB
www.nc.gov/core/misc/jquery.tabbable.shim.js?v=10.6.3	1209600.0 s	1.0 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/plugin-min.js?v=10.6.3	1209600.0 s	1.0 KiB
www.nc.gov/themes/custom/nc_barrio/css/icons/search-white.svg	1209600.0 s	1.0 KiB
www.nc.gov/core/assets/vendor/jquery.ui/ui/data-min.js?v=10.6.3	1209600.0 s	1003 B
www.nc.gov/themes/custom/nc_barrio/components/spotlight/spotlight.js?td91kj	1209600.0 s	983 B
www.nc.gov/modules/contrib/addtoany/js/addtoany.js?v=10.6.3	1209600.0 s	891 B
www.nc.gov/core/assets/vendor/jquery.ui/ui/version-min.js?v=10.6.3	1209600.0 s	743 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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/sourcesans3/v19/nwpMtKy2OAdR1K-IwhWudF-R3woqZ-LYxnV18A.woff2	55 ms
fonts.gstatic.com/s/sourcesans3/v19/nwpStKy2OAdR1K-IwhWudF-R3w8aZejf5Hc.woff2	35 ms
fonts.gstatic.com/s/sourcesans3/v19/nwpStKy2OAdR1K-IwhWudF-R3wsaZejf5HdF8Q.woff2	30 ms
fonts.gstatic.com/s/sourcesans3/v19/nwpStKy2OAdR1K-IwhWudF-R3wAaZejf5HdF8Q.woff2	30 ms
/npm/bootstrap-icons@1.5.0/font/fonts/bootstrap-icons.wof...	5.0 ms

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:71.302 source:map[column:390 line:159 type:source-location url:https://www.nc.gov/ruxitagentjs_ICA7NVfqrux_10333260303165926.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:23.57 source:map[column:368 line:299 type:source-location url:https://www.nc.gov/ruxitagentjs_ICA7NVfqrux_10333260303165926.js urlProvider:network]] map[reflowTime:47.732 source:map[column:387 line:288 type:source-location url:https://www.nc.gov/ruxitagentjs_ICA7NVfqrux_10333260303165926.js urlProvider:network]] map[reflowTime:0.535 source:map[column:49615 line:1 type:source-location url:https://www.nc.gov/core/assets/vendor/jquery/jquery.min.js?v=3.7.1 urlProvider:network]] map[reflowTime:0.308 source:map[column:50335 line:1 type:source-location url:https://www.nc.gov/core/assets/vendor/jquery/jquery.min.js?v=3.7.1 urlProvider:network]] map[reflowTime:0.156 source:map[column:50393 line:1 type:source-location url:https://www.nc.gov/core/assets/vendor/jquery/jquery.min.js?v=3.7.1 urlProvider:network]] map[reflowTime:0.141 source:map[column:50457 line:1 type:source-location url:https://www.nc.gov/core/assets/vendor/jquery/jquery.min.js?v=3.7.1 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.

	URL	Resource Size	Est Savings
div.paragraph > div.article_card > a > img `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2021-11/hiking fami...	224.5 KiB	208.6 KiB
Welcome to North Carolina sign between bushes `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2025-09/welcome-to-...	155.7 KiB	139.8 KiB
North Carolina State Capitol in Raleigh at dusk in late winter/early spring. `div.field > div > div.field > img`	/nc/images/2025-03/NC-Capital-Dusk.jpg?VersionId=Mrb.15De...	134.9 KiB	118.6 KiB
North Carolina flag `div.paragraph > div.clearfix > p > img.circle`	files.nc.gov/nc/images/2021-11/nc_flag.jpg	132.1 KiB	112.7 KiB
Halifax Resolves reenactment with men and women wearing colonial clothing in a … `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2026-01/america-250...	120.5 KiB	107.2 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

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
/css2?family=Source+Sans+3:ital,wght@0,200..900;1,200..90...	813 B	868 ms
fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@700&display=swap	897 B	179 ms
/sites/default/files/css/css_PL_Iye-brijxjf92SI08k8dudrnB...	94.9 KiB	1.3 s
cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css	25.1 KiB	1.1 s
/sites/default/files/css/css_XMPNvRiR0X3mue3SsggllvQ2daZR...	78.0 KiB	1.8 s
www.nc.gov/ruxitagentjs_ICA7NVfqrux_10333260303165926.js	78.8 KiB	333 ms
/sites/default/files/css/css_sqSD8hK_RX1dBLNSHl6LZ19a_YuY...	41.0 KiB	500 ms
cdn.jsdelivr.net/npm/bootstrap-icons@1.5.0/font/bootstrap-icons.css	8.2 KiB	150 ms
/sites/default/files/css/css_xHXt5uQb9mfd9Re0miy7mHeZT5do...	26.5 KiB	500 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s

URL	Time Spent
nc.gov/	1.0 s
www.nc.gov/	0.0 ms

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: 180 ms 19.5 KiB

URL	Transfer Size	Est Savings
www.nc.gov/core/misc/ajax.js?v=10.6.3	16.6 KiB	11.6 KiB
www.nc.gov/core/misc/drupal.js?v=10.6.3	6.1 KiB	4.8 KiB
www.nc.gov/core/misc/position.js?v=10.6.3	5.5 KiB	3.0 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: 1.6 s 212.0 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_PL_Iye-brijxjf92SI08k8dudrnB...	94.3 KiB	86.2 KiB
/sites/default/files/css/css_XMPNvRiR0X3mue3SsggllvQ2daZR...	77.4 KiB	68.8 KiB
/sites/default/files/css/css_sqSD8hK_RX1dBLNSHl6LZ19a_YuY...	40.4 KiB	31.2 KiB
/sites/default/files/css/css_xHXt5uQb9mfd9Re0miy7mHeZT5do...	26.0 KiB	25.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.

Estimated savings: 1.9 s 336.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=UA-47173823-1&cx=c&gtm=4e64k0	115.3 KiB	89.9 KiB
www.googletagmanager.com/gtag/js?id=G-G6JR0TC8JZ&cx=c&gtm=4e64k0	157.1 KiB	65.8 KiB
www.googletagmanager.com/gtag/js?id=UA-47173823-1	116.4 KiB	65.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDNPMRD	116.8 KiB	63.1 KiB
www.nc.gov/ruxitagentjs_ICA7NVfqrux_10333260303165926.js	78.3 KiB	31.6 KiB
static.addtoany.com/menu/modules/core.ydpp7jcu.js	25.7 KiB	21.0 KiB

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	978 ms
Style & Layout	528 ms
Other	415 ms
Script Parsing & Compilation	206 ms
Parse HTML & CSS	178 ms
Rendering	20 ms
Garbage Collection	9.0 ms

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
North Carolina flag `div.paragraph > div.clearfix > p > img.circle`	files.nc.gov/nc/images/2021-11/nc_flag.jpg
Welcome to North Carolina sign between bushes `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2025-09/welcome-to-...
Halifax Resolves reenactment with men and women wearing colonial clothing in a … `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2026-01/america-250...
div.paragraph > div.article_card > a > img `div.paragraph > div.article_card > a > img`	/nc/styles/article_card/public/images/2021-11/hiking fami...
Home `div#navbar-main > section.nc_header > a.navbar-brand > img.img-fluid`	files.nc.gov/nc/ncgov_250X75_2.png?VersionId=AOYQRfbcGNZoeheprjcrNNpqiO9gfLsJ
The Great Seal of the State of North Carolina `div.clearfix > div.footer-logo__img > div.field > img.no-image-style`

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 2,658 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 12 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 20 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

100

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.

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 about protecting your personal information `div#fc4494db2108dcc5ab54d55998b4b5aafb8035927fa130fd78480489b6ff35f0 > div.message > p > a.alert-link`

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

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

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

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

○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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

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

○Identical links have the same purpose.

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

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Home `div#navbar-main > section.nc_header > a.navbar-brand > img.img-fluid`	files.nc.gov/nc/ncgov_250X75_2.png?VersionId=AOYQRfbcGNZoeheprjcrNNpqiO9gfLsJ	225 x 68	250 x 75	338 x 102

●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

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