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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
az.gov/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172800.0 s	860 B

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
background `body.html > div.anystretch > img.anystretch_bg`	az.gov/sites/default/files/postcards/GOV_large_BGBlur_DDucey.png	1.2 MiB	1.2 MiB
Locate, manage, and grow your business in Arizona, or join our highly skilled w… `div.content > div#mainpanels > div.container > div#panel2`	/sites/default/files/postcards/Hotel Monte Vista _ Steve ...	346.6 KiB	295.4 KiB
Learn more about the schools, neighborhoods, and citizen resources that elevate… `div.content > div#mainpanels > div.container > div#panel3`	/sites/default/files/postcards/Hoover Dam and Bridge _ Ro...	345.8 KiB	294.6 KiB
© 2019 State of Arizona POLICIES SITE MAP MEDIA GALLERY HELP OPTIONS Find an… `div#zone-footer-wrapper > div#zone-footer > div#footer > nav#footer-nav`	az.gov/sites/all/themes/azgov/img/azseal.png	89.0 KiB	59.7 KiB
Residents in Arizona `div#panel3 > div > div.textContent > img`	az.gov/sites/default/files/text-residents-arizona.png	20.3 KiB	17.2 KiB
div#panel2 > div > div.textContent > img `div#panel2 > div > div.textContent > img`	az.gov/sites/default/files/text-business-arizona.png	19.1 KiB	16.1 KiB
Discover Arizona `div#panel1 > div > div.textContent > img`	az.gov/sites/default/files/text-discover-arizona.png	14.6 KiB	11.6 KiB

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-7-DIV

nodeLabel: Explore our historic past, vibrant present, and promising future

path: 1,HTML,1,BODY,2,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV

selector: div.content > div#mainpanels > div.container > div#panel1

snippet: <div id="panel1" class="panel" style="background-image: url("https://az.gov/sites/default/files/postcards/PC-Thr…");">

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
www.googletagmanager.com/gtag/js?id=UA-39773230-1	115.9 KiB	1.9 s
az.gov/sites/default/files/js_injector/js_injector_1.js?tdac5i	372 B
az.gov/sites/default/files/css_injector/css_injector_6.css?tdac5i	394 B
az.gov/sites/default/files/js/js_wP_K6IzGcdCMFXbjtfKp9vuIMrVxRA8ub2i125Sv9jY.js	89.7 KiB	900 ms
az.gov/sites/default/files/js/js_TWKm9-6PK6lnTvWvkAb3sZE01kZEDuEoVWsRRP4CQw0.js	1.5 KiB
az.gov/sites/default/files/js/js_MbJ8uSt8FnczZCkuJ0IGn9WnZ54qnlCrOtJTZu-bF54.js	2.3 KiB	150 ms
az.gov/sites/default/files/js/js_MMvzk3piKlIBWcpWgwp4n53pFIdJ_fJD-hKGDJaTCrw.js	7.3 KiB	150 ms
az.gov/sites/default/files/js/js_XcU4CFOGPP6W7FpHdz0wAprMjDfMSbkpyj5pIhtHbhI.js	7.7 KiB
az.gov/sites/default/files/js/js_1kmqaL-ZHNpUzE1MbRYi4nlI_AXpH1XP9HPtnQDYngw.js	15.2 KiB	150 ms
/sites/default/files/css/css_9C2pI8G3S3GaJZasA-1m53fKjhES...	5.2 KiB	150 ms
/sites/default/files/css/css_7ETb_7hYRyvU4W25kBKil4n2jkeM...	4.8 KiB
az.gov/sites/default/files/js/js_YD9ro0PAqY25gGWrTki6TjRUG8TdokmmxjfqpNNfzVU.js	45.3 KiB	450 ms
az.gov/sites/default/files/js/js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js	2.3 KiB
/sites/default/files/css/css_7ePPi47Gn_UGkamW-vjrDHHJ2DzW...	26.1 KiB	150 ms
az.gov/sites/default/files/js/js_rSZmM_C6ErJgSf1Ywt9MyoQ7J2cAjMsn1upJN2IAhSE.js	1.7 KiB
/sites/default/files/css/css_D7wnz0rW5XL7XKHiCb6aag1sm8CC...	2.6 KiB
/sites/default/files/css/css_XfqmfUwM85fnovLSD_iTt1OrkylG...	16.3 KiB	150 ms
/sites/default/files/css/css_Ijii_GD5j5AGAMxG616MLU99fkje...	467 B
/sites/default/files/css/css_jrqdtNeDE6bm1xAhUoGvZP_T8IUq...	1.3 KiB
/sites/default/files/css/css_xE-rWrJf-fncB6ztZfd2huxqgxu4...	2.8 KiB	150 ms

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

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: 600 ms 72.2 KiB

URL	Transfer Size	Est Savings
az.gov/sites/default/files/js/js_wP_K6IzGcdCMFXbjtfKp9vuIMrVxRA8ub2i125Sv9jY.js	89.5 KiB	51.2 KiB
az.gov/sites/default/files/js/js_YD9ro0PAqY25gGWrTki6TjRUG8TdokmmxjfqpNNfzVU.js	45.1 KiB	10.9 KiB
az.gov/sites/default/files/js/js_1kmqaL-ZHNpUzE1MbRYi4nlI_AXpH1XP9HPtnQDYngw.js	15.0 KiB	7.0 KiB
az.gov/sites/default/files/js/js_XcU4CFOGPP6W7FpHdz0wAprMjDfMSbkpyj5pIhtHbhI.js	7.5 KiB	3.1 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: 450 ms 37.4 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_7ePPi47Gn_UGkamW-vjrDHHJ2DzW...	25.9 KiB	23.9 KiB
/sites/default/files/css/css_XfqmfUwM85fnovLSD_iTt1OrkylG...	16.1 KiB	13.5 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.1 s 169.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-ZZ9LGEDKEW&cx=c&gtm=4e64k0	156.8 KiB	66.8 KiB
www.googletagmanager.com/gtag/js?id=UA-39773230-1	115.5 KiB	63.3 KiB
az.gov/sites/default/files/js/js_wP_K6IzGcdCMFXbjtfKp9vuIMrVxRA8ub2i125Sv9jY.js	89.5 KiB	39.4 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/sites/default/files/postcards/Hotel Monte Vista _ Steve ...	2.6 MiB
/sites/default/files/postcards/Hoover Dam and Bridge _ Ro...	2.0 MiB
az.gov/sites/default/files/postcards/GOV_large_BGBlur_DDucey.png	1.2 MiB
/sites/default/files/postcards/Hotel Monte Vista _ Steve ...	864.9 KiB
/sites/default/files/postcards/Hoover Dam and Bridge _ Ro...	818.5 KiB
/sites/default/files/postcards/Hotel Monte Vista _ Steve ...	347.2 KiB
/sites/default/files/postcards/Hoover Dam and Bridge _ Ro...	346.4 KiB
az.gov/sites/default/files/postcards/B-n-Three-Sisters.jpg	322.2 KiB
www.googletagmanager.com/gtag/js?id=G-ZZ9LGEDKEW&cx=c&gtm=4e64k0	156.9 KiB
www.googletagmanager.com/gtag/js?id=UA-39773230-1	115.9 KiB

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
Search Icon `div.boxes-box-content > div > a.searchlink > img`	az.gov/sites/all/themes/azgov/img/icon-searchlink.png

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 40 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 190 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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
div.block-inner > div.content > div#tb-megamenu-main-menu > button.btn `div.block-inner > div.content > div#tb-megamenu-main-menu > button.btn`

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
div#boxes-box-header_links > div.boxes-box-content > div > a.showhide `div#boxes-box-header_links > div.boxes-box-content > div > a.showhide`
div#boxes-box-header_links > div.boxes-box-content > div > a.showhide `div#boxes-box-header_links > div.boxes-box-content > div > a.showhide`
div#boxes-box-header_links > div.boxes-box-content > div > a.showhide `div#boxes-box-header_links > div.boxes-box-content > div > a.showhide`

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.

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
HELP OPTIONS Find an Agency Find a Service Find an Employee Webmaster TRANSPARE… `div#block-views-footer-block-1 > div.block-inner > div.content > ul.view`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HELP OPTIONS Find an Agency Find a Service Find an Employee Webmaster `div.content > ul.view > div.view-content > li.expanded`
TRANSPARENCY AZ Checkbook OpenBooks Governor's Office Priorities `div.content > ul.view > div.view-content > li.expanded`
ALERTS 511 - Traffic (link is external) Air Quality Amber Alerts Emergency Info… `div.content > ul.view > div.view-content > li.expanded`
BUSINESS IN ARIZONA Secretary of State Arizona Corporation Commission Licensing… `div.content > ul.view > div.view-content > li.expanded`

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○Form elements have associated labels

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

○No element has a `[tabindex]` value greater than 0

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

○Identical links have the same purpose.

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

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
Search Icon `div.boxes-box-content > div > a.searchlink > img`	az.gov/sites/all/themes/azgov/img/icon-searchlink.png	24 x 20	24 x 20	36 x 30
div.boxes-box-content > div > a.showhide > img `div.boxes-box-content > div > a.showhide > img`	az.gov/sites/default/files/icon-agencies.png	24 x 20	24 x 20	36 x 30
div.boxes-box-content > div > a.showhide > img `div.boxes-box-content > div > a.showhide > img`	az.gov/sites/default/files/icon-services.png	24 x 20	24 x 20	36 x 30
div.boxes-box-content > div > a.showhide > img `div.boxes-box-content > div > a.showhide > img`	az.gov/sites/default/files/vote-icon.png	16 x 14	16 x 14	24 x 21

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

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

○robots.txt is valid

○Document has a valid `rel=canonical`