Skip to content
https://nebraska.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.

44

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
www.nebraska.gov/assets/js/main.js0.0 ms346.8 KiB
www.nebraska.gov/assets/css/main.min.css0.0 ms185.7 KiB
www.nebraska.gov/assets/css/flat-ui.css0.0 ms156.1 KiB
www.nebraska.gov/assets/css/framework.css0.0 ms118.8 KiB
www.nebraska.gov/assets/img/ne-seal.png0.0 ms103.4 KiB
www.nebraska.gov/assets/fonts/roboto/Roboto-Italic.woff0.0 ms92.8 KiB
www.nebraska.gov/assets/js/lib/jquery.js0.0 ms87.8 KiB
www.nebraska.gov/assets/fonts/roboto/Roboto-Regular.woff0.0 ms87.8 KiB
www.nebraska.gov/assets/fonts/roboto/Roboto-Bold.woff0.0 ms87.5 KiB
www.nebraska.gov/assets/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.10.0 ms69.4 KiB
www.nebraska.gov/assets/fonts/montserrat/Montserrat-SemiBold.woff0.0 ms32.8 KiB
www.nebraska.gov/assets/css/cat-style.css0.0 ms29.0 KiB
www.nebraska.gov/assets/fonts/montserrat/Montserrat-Regular.woff0.0 ms24.6 KiB
www.nebraska.gov/assets/fonts/montserrat/Montserrat-Light.woff0.0 ms24.3 KiB
www.nebraska.gov/assets/img/fallback-xs.jpg0.0 ms20.8 KiB
www.nebraska.gov/assets/js/lib/jquery-migrate-3.1.0.js0.0 ms19.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
www.nebraska.gov/assets/img/icons/ne-slogan-logo.png0.0 ms14.2 KiB
www.nebraska.gov/assets/img/ne-mini-logo.png0.0 ms8.5 KiB
www.nebraska.gov/site/js/fix-google-cse-ids.js0.0 ms6.2 KiB
www.nebraska.gov/assets/css/accessibility-fixes.css0.0 ms5.5 KiB
www.nebraska.gov/site/js/chart-data.js0.0 ms4.3 KiB
www.nebraska.gov/assets/img/official-ne-gov-website.png0.0 ms3.7 KiB
cse.google.com/cse.js?mob=1&cx=003873714344695240192:4d7aj4srcp40.0 ms3.6 KiB
www.nebraska.gov/assets/img/icons/hands.svg0.0 ms2.6 KiB
www.nebraska.gov/assets/img/icons/building.svg0.0 ms2.6 KiB
www.nebraska.gov/site/js/fix-search-button-labels.js0.0 ms2.4 KiB
www.nebraska.gov/assets/img/icons/hammer.svg0.0 ms2.1 KiB
www.nebraska.gov/assets/img/icons/scale.svg0.0 ms2.0 KiB
www.nebraska.gov/assets/img/icons/computer.svg0.0 ms1.2 KiB
www.nebraska.gov/assets/img/icons/key.svg0.0 ms1.2 KiB
www.nebraska.gov/assets/img/icons/right-chevron.svg0.0 ms1.2 KiB
www.google.com/cse/static/style/look/v6/default.css3000.0 s1.2 KiB
www.nebraska.gov/assets/img/icons/menu.svg0.0 ms978 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.

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:1038.1370009765626 label:Time to first byte subpart:timeToFirstByte] map[duration:1443.2969990234376 label:Resource load delay subpart:resourceLoadDelay] map[duration:157.734 label:Resource load duration subpart:resourceLoadDuration] map[duration:24.88 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-SECTION
nodeLabel: Good Life. Great Opportunity.
path: 1,HTML,1,BODY,3,MAIN,0,SECTION
selector: body.home > main#content > section.home-header
snippet: <section class="home-header">

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-0-SECTION
nodeLabel: Good Life. Great Opportunity.
path: 1,HTML,1,BODY,3,MAIN,0,SECTION
selector: body.home > main#content > section.home-header
snippet: <section class="home-header">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.nebraska.gov/http/1.1
www.nebraska.gov/assets/css/framework.csshttp/1.1
www.nebraska.gov/assets/css/flat-ui.csshttp/1.1
www.nebraska.gov/assets/css/cat-style.csshttp/1.1
www.nebraska.gov/assets/css/main.min.csshttp/1.1
www.nebraska.gov/assets/css/accessibility-fixes.csshttp/1.1
www.nebraska.gov/assets/js/lib/jquery.jshttp/1.1
www.nebraska.gov/assets/js/lib/jquery-migrate-3.1.0.jshttp/1.1
www.nebraska.gov/assets/js/main.jshttp/1.1
www.nebraska.gov/manifest.jsonhttp/1.1
www.nebraska.gov/site/js/chart-data.jshttp/1.1
www.nebraska.gov/site/js/fix-google-cse-ids.jshttp/1.1
www.nebraska.gov/site/js/fix-search-button-labels.jshttp/1.1
www.nebraska.gov/assets/img/icons/menu.svghttp/1.1
www.nebraska.gov/assets/img/ne-mini-logo.pnghttp/1.1
www.nebraska.gov/assets/img/fallback-xs.jpghttp/1.1
www.nebraska.gov/assets/img/icons/scale.svghttp/1.1
www.nebraska.gov/assets/img/icons/right-chevron.svghttp/1.1
www.nebraska.gov/assets/img/icons/computer.svghttp/1.1
www.nebraska.gov/assets/img/icons/building.svghttp/1.1
www.nebraska.gov/assets/img/icons/key.svghttp/1.1
www.nebraska.gov/assets/img/icons/hammer.svghttp/1.1
www.nebraska.gov/assets/img/icons/hands.svghttp/1.1
www.nebraska.gov/assets/img/ne-seal.pnghttp/1.1
www.nebraska.gov/assets/img/icons/ne-slogan-logo.pnghttp/1.1
www.nebraska.gov/assets/img/official-ne-gov-website.pnghttp/1.1
www.nebraska.gov/assets/fonts/roboto/Roboto-Regular.woffhttp/1.1
www.nebraska.gov/assets/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.1http/1.1
www.nebraska.gov/assets/fonts/montserrat/Montserrat-SemiBold.woffhttp/1.1
www.nebraska.gov/assets/fonts/roboto/Roboto-Bold.woffhttp/1.1
www.nebraska.gov/assets/fonts/roboto/Roboto-Italic.woffhttp/1.1
www.nebraska.gov/assets/fonts/montserrat/Montserrat-Light.woffhttp/1.1
www.nebraska.gov/assets/fonts/montserrat/Montserrat-Regular.woffhttp/1.1
www.nebraska.gov/datastore/agency_contact/abe.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ago.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/aoc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/apa.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/atp.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/belf.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/bog.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/bop.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ccpe.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/das.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/dhhs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/dmv.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/dol.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ea.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/edn.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/fcro.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/gap.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/lcc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/lottery.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/mvilb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nac.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nadc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nato.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbbe.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbd.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbels.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbla.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbop.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nbpa.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncbvi.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncdhh.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncia.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncio.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncir.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncpa.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ncs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nda.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndbc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndbf.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndcs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nde.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nded.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndee.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndidb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndoa.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndoi.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndot.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ndr.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/neatp.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/neb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/necc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nema.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nent.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/neoc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/net.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nfo.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nfs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ngpc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ngsb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ngwb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nic.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nitc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nlc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nlac.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nng.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nog.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nogcc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/npers.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nppc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nprb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nrc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nrec.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nrpab.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nrrs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsac.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nscs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsf.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nshs.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsp.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsrb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsrc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nsto.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/ntc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nul.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nvc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nvr.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/nwb.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/occ.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/psc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/sed.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/sfm.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/sor.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/sos.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/sso.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/terc.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/un.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/va.jsonhttp/1.1
www.nebraska.gov/datastore/agency_contact/wcc.jsonhttp/1.1
www.nebraska.gov/calendar/rss.xmlhttp/1.1
www.nebraska.gov/favicon-32x32.pnghttp/1.1

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
value: No additional origins are good candidates for preconnecting

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.main-footer > div.row > div.col-xs-12 > div#goodlife-logo div.main-footer > div.row > div.col-xs-12 > div#goodlife-logo
www.nebraska.gov/assets/img/icons/ne-slogan-logo.png13.8 KiB10.0 KiB

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.1 s
URLTime Spent
nebraska.gov/1.1 s
www.nebraska.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 CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 520 ms 48.3 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.

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
Other1.5 s
Script Evaluation1.3 s
Style & Layout690 ms
Script Parsing & Compilation341 ms
Rendering310 ms
Parse HTML & CSS90 ms

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,297 KiB
●User Timing marks and measures 7 user timings
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 120 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
87

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#header > nav#navigation > div.navbar-header > button.navbar-toggle header#header > nav#navigation > div.navbar-header > button.navbar-toggle

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.

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
3.0 div#stat1 > div.stats > div.stats-center > div.counter-value
20 div#stat2 > div.stats > div.stats-center > div.counter-value

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact Us Awards Site Map Policies Seleccionar idioma▼ div.main-footer > div.row > div.col-xs-6 > ul
Powered by Tyler Technologies PO Box 3395 Omaha, NE 68103 USA © 2026 State of N… div.main-footer > div.row > div.col-xs-12 > ul.branding

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 have a discernible name
●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
●Identical links have the same purpose.
○`[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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to create chart: can't acquire context from the given item
Uncaught TypeError: Cannot set properties of null (setting 'innerHTML')
●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
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
GOVERNMENT div.no-row > ul > li.h4 > a
BUSINESS div.no-row > ul > li.h4 > a
EMPLOYMENT div.no-row > ul > li.h4 > a
EDUCATION div.no-row > ul > li.h4 > a
ATTRACTIONS div.no-row > ul > li.h4 > a

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
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback