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.

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.

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.

URL	Protocol
www.va.gov/	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/web-components.css	http/1.1
/generated/web-components.entry.js	http/1.1
/generated/sourcesanspro-bold-webfont.woff2	http/1.1
/generated/sourcesanspro-regular-webfont.woff2	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/bitter-bold.woff2	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/style.css	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/assets/content-build.css	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/static-pages.css	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/vendor.entry.js	http/1.1
/generated/static-pages.entry.js	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/tiny-usa-flag.png	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/icon-dot-gov.svg	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/icon-https.svg	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/arrow-right-white.svg	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/header-logo.png	http/1.1
/content.www.va.gov/img/styles/crop_square/public/news_pr...	http/1.1
/generated/node_modules_department-of-veterans-affairs_co...	http/1.1
/generated/vendors-node_modules_department-of-veterans-af...	http/1.1
/generated/node_modules_department-of-veterans-affairs_co...	http/1.1
/generated/node_modules_department-of-veterans-affairs_co...	http/1.1
www.va.gov/generated/announcements-widget.entry.js	http/1.1
www.va.gov/data/cms/vamc-ehr.json	http/1.1
www.va.gov/generated/maintenance-banner-widget.entry.js	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/img/plus-white.svg	http/1.1
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/img/vcl-logo.png	http/1.1
www.va.gov/generated/vet-center-hours-widget.entry.js	http/1.1
/generated/vendors-node_modules_mapbox_mapbox-sdk_index_j...	http/1.1
www.va.gov/generated/facility-detail.entry.js	http/1.1
/generated/vendors-node_modules_department-of-veterans-af...	http/1.1
/generated/src_applications_static-pages_homepage_Homepag...	http/1.1
www.va.gov/img/homepage/va-logo-white.png	http/1.1
www.va.gov/img/tiny-usa-flag.png	http/1.1
www.va.gov/img/sprite.svg#medical_services	http/1.1
/generated/node_modules_department-of-veterans-affairs_co...	http/1.1
/generated/vendors-node_modules_department-of-veterans-af...	http/1.1
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/img/design/icons/favicon.ico	http/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

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

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
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/style.css	91.7 KiB	1.5 s
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/static-pages.css	2.9 KiB	854 ms
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/web-components.css	3.6 KiB	854 ms
s3-us-gov-west-1.amazonaws.com/content.www.va.gov/assets/content-build.css	6.3 KiB	864 ms

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
resource.digital.voice.va.gov/wdcvoice/2/onsite/generic1773344517037.js	0.0 ms	371.6 KiB
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=VA	0.0 ms	9.5 KiB
siteimproveanalytics.com/js/siteanalyze_6319010.js	86400.0 s	14.1 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js	0.0 ms	4.5 KiB

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
VA logo and Seal, U.S. Department of Veterans Affairs `div.footer-inner > div.usa-grid > a > img.vads-u-height--auto`	www.va.gov/img/homepage/va-logo-white.png	14.2 KiB	9.3 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

URL	Time Spent
va.gov/	1.1 s
www.va.gov/	0.0 ms

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

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: 170 ms 88.1 KiB

URL	Transfer Size	Est Savings
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/style.css	91.3 KiB	88.1 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: 280 ms 842.5 KiB

URL	Transfer Size	Est Savings
/generated/static-pages.entry.js	535.0 KiB	236.4 KiB
resource.digital.voice.va.gov/wdcvoice/2/onsite/generic1773344517037.js	371.2 KiB	216.2 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e6562	146.9 KiB	106.2 KiB
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/vendor.entry.js	197.4 KiB	82.4 KiB
www.googletagmanager.com/gtag/js?id=G-YPB3FD0PQ9&cx=c&gtm=4e6562	143.8 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L	146.9 KiB	61.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-WFJWBD	148.2 KiB	48.5 KiB
/generated/web-components.entry.js	69.2 KiB	28.3 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
/generated/static-pages.entry.js	1.3 s	958 ms	251 ms
Unattributable	577 ms	42 ms	0.0 ms
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/vendor.entry.js	462 ms	341 ms	119 ms
www.googletagmanager.com/gtm.js?id=GTM-WFJWBD	406 ms	349 ms	54 ms
www.googletagmanager.com/gtag/js?id=G-YPB3FD0PQ9&cx=c&gtm=4e6562	360 ms	316 ms	42 ms
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L	348 ms	268 ms	40 ms
/generated/web-components.entry.js	342 ms	255 ms	59 ms
www.va.gov/	239 ms	16 ms	13 ms
resource.digital.voice.va.gov/wdcvoice/2/onsite/generic1773344517037.js	112 ms	72 ms	40 ms
siteimproveanalytics.com/js/siteanalyze_6319010.js	69 ms	64 ms	4.6 ms
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e6562	68 ms	27 ms	41 ms
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js	67 ms	64 ms	1.3 ms
prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com/generated/style.css	62 ms	0.0 ms	0.0 ms

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	2.9 s
Script Parsing & Compilation	690 ms
Other	584 ms
Style & Layout	174 ms
Garbage Collection	88 ms
Parse HTML & CSS	57 ms
Rendering	54 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
U.S. flag `div.vads-u-display--flex > div.vads-u-display--flex > div.vads-u-background-color--gray-lightest > img.header-us-flag`	www.va.gov/img/tiny-usa-flag.png

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 13 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 290 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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.

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

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

100

Best Practices

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