C — https://www.usa.gov | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 image-only link(s) without alt text

Accessibility › Link & Button Quality

3 button(s) with no accessible text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.usa.gov)](https://beavercheck.com/results/81967bed-c99a-45d7-9446-13089ff127a1)

HTML

<a href="https://beavercheck.com/results/81967bed-c99a-45d7-9446-13089ff127a1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.usa.gov" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.usa.gov

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.79 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.69 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.60 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.31 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

9.13 s

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.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	1800.0 s	89.2 KiB
/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAi...	1800.0 s	57.7 KiB
/s3/files/styles/max_480w/public/2023-02/Homepage_Banner....	900.0 s	40.3 KiB
/themes/custom/usagov/fonts/merriweather/Latin-Merriweath...	900.0 s	21.3 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.5 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.5 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.4 KiB
www.usa.gov/themes/custom/usagov/images/topics/ICONS_Reimagined_Benefits.svg	900.0 s	19.6 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	16.5 KiB
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=GSA&subagency=TTS	0.0 ms	9.4 KiB
www.usa.gov/themes/custom/usagov/images/USAGov_Logo_80px.png	900.0 s	10.0 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js	0.0 ms	4.5 KiB
siteimproveanalytics.com/js/siteanalyze_51567.js	86400.0 s	9.4 KiB
www.usa.gov/themes/custom/usagov/images/Icon_Back_to_Top_Blue.png	900.0 s	2.7 KiB
www.usa.gov/themes/custom/usagov/scripts/modifyMobileNav.js	900.0 s	1.6 KiB
/sites/default/files/css/css_cOhfci6idzC267zPPyoqqdpdbqTo...	1800.0 s	1.6 KiB
www.usa.gov/themes/custom/usagov/scripts/newFooter.js	900.0 s	1.3 KiB
www.usa.gov/themes/custom/usagov/assets/img/icon-dot-gov.svg	900.0 s	1.3 KiB
www.usa.gov/themes/custom/usagov/images/Reimagined_Jump_to_Arrow.svg	900.0 s	1.2 KiB
www.usa.gov/themes/custom/usagov/assets/img/icon-https.svg	900.0 s	1.2 KiB
www.usa.gov/themes/custom/usagov/components/searchbar/images/search--dark.svg	900.0 s	992 B
www.usa.gov/themes/custom/usagov/images/favicon-57.png	900.0 s	984 B
/modules/contrib/uswds_ckeditor_integration/js/aftermarke...	900.0 s	968 B
www.usa.gov/themes/custom/usagov/images/Button_header_open_mobile-menu.svg	900.0 s	955 B
www.usa.gov/themes/custom/usagov/assets/img/usa-icons/close.svg	900.0 s	719 B
www.usa.gov/themes/custom/usagov/assets/img/usa-icons/navigate_next.svg	900.0 s	664 B
www.usa.gov/themes/custom/usagov/assets/img/usa-icons/expand_more.svg	900.0 s	662 B
script.crazyegg.com/pages/scripts/0007/9651.js	86400.0 s	197 B
/a?v=3&t=l&pid=854216005&rv=6411&tag_exp=0~115938465~1159...	0.0 ms	11 B

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.

URL	Est Savings
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	35 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	30 ms
/themes/custom/usagov/fonts/merriweather/Latin-Merriweath...	30 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	30 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	25 ms

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

lhId: page-0-DIV

nodeLabel: div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div

path: 1,HTML,1,BODY,6,MAIN,0,DIV,0,DIV,1,DIV,0,DIV

selector: div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div

snippet: <div class="banner-div">

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.

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

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.

URL	Transfer Size	Duration
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	89.2 KiB	493 ms
/sites/default/files/css/css_cOhfci6idzC267zPPyoqqdpdbqTo...	1.6 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div `div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div`	/s3/files/styles/max_480w/public/2023-02/Homepage_Banner....	39.8 KiB	16.1 KiB
USAGov Logo `div#extended-logo > em.usa-logo-text > a > img`	www.usa.gov/themes/custom/usagov/images/USAGov_Logo_80px.png	9.6 KiB	5.9 KiB

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

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.

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.

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.

Estimated savings: 450 ms 86.5 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	88.8 KiB	86.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.

Estimated savings: 2.0 s 381.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e6411	145.5 KiB	104.5 KiB
www.googletagmanager.com/gtag/js?id=G-GXFTMLX26S&cx=c&gtm=4e6411	151.0 KiB	62.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-THHB6TNL&gtm=4e6411	122.5 KiB	62.1 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L	146.1 KiB	61.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W8LW6DB	136.8 KiB	56.3 KiB
/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAi...	57.2 KiB	34.8 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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.googletagmanager.com/gtm.js?id=GTM-W8LW6DB	670 ms	564 ms	81 ms
Unattributable	569 ms	16 ms	0.0 ms
www.usa.gov/	512 ms	22 ms	7.8 ms
www.googletagmanager.com/gtag/js?id=G-GXFTMLX26S&cx=c&gtm=4e6411	486 ms	405 ms	78 ms
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L	427 ms	338 ms	84 ms
www.googletagmanager.com/gtm.js?id=GTM-THHB6TNL&gtm=4e6411	319 ms	233 ms	69 ms
/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAi...	256 ms	182 ms	37 ms
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js	214 ms	193 ms	3.4 ms
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	138 ms	0.0 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e6411	126 ms	51 ms	74 ms
siteimproveanalytics.com/js/siteanalyze_51567.js	90 ms	75 ms	4.8 ms
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=GSA&subagency=TTS	82 ms	71 ms	8.1 ms
www.usa.gov/themes/custom/usagov/scripts/modifyMobileNav.js	64 ms	5.0 ms	0.8 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

Category	Time Spent
Script Evaluation	2.2 s
Other	601 ms
Style & Layout	500 ms
Script Parsing & Compilation	451 ms
Parse HTML & CSS	159 ms
Garbage Collection	65 ms
Rendering	52 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
div.main-grid > div.benefits-block-bg > div.benefits-block > img `div.main-grid > div.benefits-block-bg > div.benefits-block > img`	www.usa.gov/themes/custom/usagov/images/topics/ICONS_Reimagined_Benefits.svg

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,099 KiB

●User Timing marks and measures 115 user timings

●Avoid long main-thread tasks 17 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 20 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 30 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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.

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.

Failing Elements
USAGov Contact Center `div > div#footer-phone > div.mobile-lg:grid-col-auto > h4.usa-footer__logo-heading`

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

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

●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

○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

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

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

○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

●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

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

474 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

747 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

101 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.029

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

668 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.96 s

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.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
/s3/files/styles/max_1280w/public/2023-02/Homepage_Banner...	900.0 s	184.0 KiB
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	1800.0 s	89.2 KiB
/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAi...	1800.0 s	57.7 KiB
/themes/custom/usagov/fonts/merriweather/Latin-Merriweath...	900.0 s	21.3 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.5 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.5 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	20.4 KiB
www.usa.gov/themes/custom/usagov/images/topics/ICONS_Reimagined_Benefits.svg	900.0 s	19.6 KiB
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	900.0 s	16.5 KiB
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=GSA&subagency=TTS	0.0 ms	9.4 KiB
www.usa.gov/themes/custom/usagov/images/USAGov_Logo_80px.png	900.0 s	10.0 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js	0.0 ms	4.5 KiB
siteimproveanalytics.com/js/siteanalyze_51567.js	86400.0 s	9.4 KiB
www.usa.gov/themes/custom/usagov/images/Icon_Back_to_Top_Blue.png	900.0 s	2.7 KiB
www.usa.gov/themes/custom/usagov/scripts/modifyMobileNav.js	900.0 s	1.6 KiB
/sites/default/files/css/css_cOhfci6idzC267zPPyoqqdpdbqTo...	1800.0 s	1.6 KiB
www.usa.gov/themes/custom/usagov/scripts/newFooter.js	900.0 s	1.3 KiB
www.usa.gov/themes/custom/usagov/assets/img/icon-dot-gov.svg	900.0 s	1.3 KiB
www.usa.gov/themes/custom/usagov/images/Reimagined_Jump_to_Arrow.svg	900.0 s	1.2 KiB
www.usa.gov/themes/custom/usagov/assets/img/icon-https.svg	900.0 s	1.2 KiB
www.usa.gov/themes/custom/usagov/components/searchbar/images/search--dark.svg	900.0 s	995 B
www.usa.gov/themes/custom/usagov/images/favicon-57.png	900.0 s	985 B
/modules/contrib/uswds_ckeditor_integration/js/aftermarke...	900.0 s	971 B
www.usa.gov/themes/custom/usagov/assets/img/usa-icons/close.svg	900.0 s	720 B
www.usa.gov/themes/custom/usagov/assets/img/usa-icons/expand_more.svg	900.0 s	664 B
script.crazyegg.com/pages/scripts/0007/9651.js	86400.0 s	230 B
/a?v=3&t=l&pid=1454948565&rv=6411&tag_exp=0~115616985~115...	0.0 ms	11 B

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.

URL	Est Savings
/themes/custom/usagov/fonts/merriweather/Latin-Merriweath...	50 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	50 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	45 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	45 ms
/themes/custom/usagov/fonts/source-sans-pro/sourcesanspro...	45 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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:48.02 source:map[type:text value:[unattributed]]] map[reflowTime:1.782 source:map[column:87698 line:14 type:source-location url:https://www.usa.gov/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAiJ5nZAYvm8UyfU.js?scope=footer&delta=0&language=en&theme=usagov&include=eJx1i0EOwjAMBD9Emz9wQ-IPlpsYE0jsynGL2tcTUThy3JnZqEYhap1VSLyNS0PWdRgaocX7hHY6SOCiE5ah-Vay8I8W3LerYjrzpSLTF4PrDIJrZvSsApVkCf8VPFo_vlKD-KSUXQ2yOLF9knAojFEt9T3eTLuV9AYiJkrD urlProvider:network]] map[reflowTime:0.096 source:map[column:60004 line:14 type:source-location url:https://www.usa.gov/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAiJ5nZAYvm8UyfU.js?scope=footer&delta=0&language=en&theme=usagov&include=eJx1i0EOwjAMBD9Emz9wQ-IPlpsYE0jsynGL2tcTUThy3JnZqEYhap1VSLyNS0PWdRgaocX7hHY6SOCiE5ah-Vay8I8W3LerYjrzpSLTF4PrDIJrZvSsApVkCf8VPFo_vlKD-KSUXQ2yOLF9knAojFEt9T3eTLuV9AYiJkrD urlProvider:network]] map[reflowTime:0.092 source:map[column:66355 line:14 type:source-location url:https://www.usa.gov/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAiJ5nZAYvm8UyfU.js?scope=footer&delta=0&language=en&theme=usagov&include=eJx1i0EOwjAMBD9Emz9wQ-IPlpsYE0jsynGL2tcTUThy3JnZqEYhap1VSLyNS0PWdRgaocX7hHY6SOCiE5ah-Vay8I8W3LerYjrzpSLTF4PrDIJrZvSsApVkCf8VPFo_vlKD-KSUXQ2yOLF9knAojFEt9T3eTLuV9AYiJkrD 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

	URL	Resource Size	Est Savings
div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div `div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div`	/s3/files/styles/max_1280w/public/2023-02/Homepage_Banner...	183.4 KiB	15.2 KiB
USAGov Logo `div#extended-logo > em.usa-logo-text > a > img`	www.usa.gov/themes/custom/usagov/images/USAGov_Logo_80px.png	9.6 KiB	5.9 KiB

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

lhId: page-0-DIV

nodeLabel: div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div

path: 1,HTML,1,BODY,6,MAIN,0,DIV,0,DIV,1,DIV,0,DIV

selector: div#block-usagov-content > div.main-grid > div.banner-wrapper > div.banner-div

snippet: <div class="banner-div">

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.

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.

URL	Transfer Size	Duration
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	89.2 KiB	164 ms
/sites/default/files/css/css_cOhfci6idzC267zPPyoqqdpdbqTo...	1.6 KiB

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

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.

Estimated savings: 50 ms 85.3 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_RS0lu12kxAKVlYtiIn6qpAq__Bev...	88.8 KiB	85.3 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.

Estimated savings: 40 ms 382.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e6411	145.5 KiB	104.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-THHB6TNL&gtm=4e6411	122.5 KiB	64.7 KiB
www.googletagmanager.com/gtag/js?id=G-GXFTMLX26S&cx=c&gtm=4e6411	151.0 KiB	62.4 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L	145.5 KiB	61.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W8LW6DB	136.8 KiB	54.4 KiB
/sites/default/files/js/js_zKYkgcCe8nw2Ew0MHhQW_VNFJZmUAi...	57.2 KiB	34.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
div.main-grid > div.benefits-block-bg > div.benefits-block > img `div.main-grid > div.benefits-block-bg > div.benefits-block > img`	www.usa.gov/themes/custom/usagov/images/topics/ICONS_Reimagined_Benefits.svg

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

●Time to Interactive 2.0 s

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,239 KiB

●User Timing marks and measures 180 user timings

●JavaScript execution time 0.5 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 5 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

100

Accessibility

○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

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

●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

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

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

○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

●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

100

SEO

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

Results for https://www.usa.gov

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Keyboard Shortcuts