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

36

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.usda.gov/sites/default/files/2025-01/3%20second%20farmer%20video-1080.mp498.0 s7.0 MiB
/themes/custom/usda_uswds/assets/uswds/fonts/merriweather...665.0 s646.5 KiB
/sites/default/files/styles/carousel_item/public/potusa-h...539939.0 s685.6 KiB
/themes/custom/usda_uswds/assets/uswds/fonts/public-sans/...256.0 s50.5 KiB
www.usda.gov/sites/default/files/homepage-hero-full.jpeg539452.0 s388.9 KiB
/sites/default/files/js/js_trlpG1xZezkam6B12ppL8d9xQZD4sR...1.0 s42.6 KiB
/sites/default/files/js/js_JhdF-G1FwcAjzuILRZ8vXh5IKJrlmq...114.0 s33.7 KiB
/themes/custom/usda_uswds/assets/uswds/fonts/source-sans-...361.0 s19.9 KiB
/themes/custom/usda_uswds/assets/uswds/fonts/source-sans-...800.0 s20.1 KiB
/sites/default/files/styles/carousel_item/public/55092873...541205.0 s145.1 KiB
www.usda.gov/sites/default/files/freedom250.png539059.0 s133.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/sites/default/files/styles/carousel_item/public/lawfare-...539678.0 s131.6 KiB
/sites/default/files/styles/carousel_item/public/dow-usda...539649.0 s111.9 KiB
/sites/default/files/css/css_M8pHcp96AasrxXbdzYTN3AWBbuDS...539059.0 s91.9 KiB
/sites/default/files/styles/component_teaser_640_x_480/pu...540497.0 s79.5 KiB
/Universal-Federated-Analytics-Min.js?agency=USDA&sp=look...0.0 ms9.4 KiB
/sites/default/files/styles/component_teaser_640_x_480/pu...541199.0 s69.3 KiB
/sites/default/files/styles/component_teaser_640_x_480/pu...539345.0 s56.8 KiB
/sites/default/files/styles/component_teaser_640_x_480/pu...539726.0 s43.2 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js0.0 ms4.5 KiB
/modules/contrib/ckeditor_accordion/js/accordion.frontend...392.0 s1.6 KiB
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/usda-logo-white.svg140.0 s1.3 KiB
www.usda.gov/themes/custom/usda_uswds/img/usda-symbol.svg324.0 s1.1 KiB
www.usda.gov/modules/contrib/google_tag/js/gtag.js?tdaspc425.0 s1.0 KiB
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/flickr.svg219.0 s952 B
www.usda.gov/modules/contrib/google_tag/js/gtm.js?tdaspc460.0 s968 B
www.usda.gov/themes/custom/usda_uswds/img/blue-orb.svg65.0 s674 B
www.usda.gov/themes/custom/usda_uswds/img/x-twitter.svg553.0 s672 B
/sites/default/files/js/js_siRSm4DXjuPrDfzYOgq1FsuCS-qC9F...900.0 s661 B
www.google-analytics.com/plugins/ua/linkid.js3600.0 s722 B
www.usda.gov/themes/custom/usda_uswds/img/x.svg672.0 s597 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/youtube.svg446.0 s561 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/instagram.svg256.0 s520 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/linkedin.svg191.0 s414 B
www.usda.gov/themes/custom/usda_uswds/img/icon-dot-gov.svg219.0 s407 B
/themes/custom/usda_uswds/assets/uswds/img/angle-arrow-do...653.0 s409 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/rss.svg136.0 s351 B
/sites/default/files/css/css_1DvtF8HGUs_DUIBQ4qbIgMjDMTm_...539212.0 s2.6 KiB
www.usda.gov/themes/custom/usda_uswds/img/icon-https.svg794.0 s355 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/facebook.svg112.0 s320 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/footer-email.svg236.0 s270 B
www.usda.gov/themes/custom/usda_uswds/img/right-arrow-brown.svg504.0 s274 B
www.usda.gov/themes/custom/usda_uswds/assets/uswds/img/usa-icons/expand_more.svg446.0 s171 B
www.usda.gov/themes/custom/usda_uswds/img/favicons/flag-favicon-57.png539402.0 s918 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:12.933 source:map[type:text value:[unattributed]]] map[reflowTime:44.247 source:map[column:278 line:92 type:source-location url:https://www.google-analytics.com/analytics.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
farm animals div.col-2 > a > div.image > img
/sites/default/files/styles/carousel_item/public/potusa-h...685.5 KiB668.5 KiB
div.field > div > div.field > img div.field > div > div.field > img
www.usda.gov/sites/default/files/homepage-hero-full.jpeg388.9 KiB326.6 KiB
America's 250th Anniversary div#usda-announce > div.announce__media > a > img
www.usda.gov/sites/default/files/freedom250.png133.0 KiB132.9 KiB
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
/sites/default/files/styles/component_teaser_640_x_480/pu...79.4 KiB64.3 KiB
research and science div.tablet:grid-col > a > div.image > img
/sites/default/files/styles/component_teaser_640_x_480/pu...69.3 KiB54.2 KiB
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
/sites/default/files/styles/component_teaser_640_x_480/pu...56.7 KiB41.6 KiB
cow in a snow storm div.tablet:grid-col > a > div.image > img
/sites/default/files/styles/component_teaser_640_x_480/pu...43.2 KiB30.1 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-1-IMG
nodeLabel: div.field > div > div.field > img
path: 1,HTML,1,BODY,2,DIV,8,MAIN,0,DIV,1,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.field > div > div.field > img
snippet: <img src="/sites/default/files/homepage-hero-full.jpeg" width="2000" height="1333" loading="lazy">

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s
URLTime Spent
usda.gov/1.0 s
www.usda.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

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: 600 ms 86.7 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_M8pHcp96AasrxXbdzYTN3AWBbuDS...91.5 KiB86.7 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Script Evaluation2.7 s
Other1.7 s
Style & Layout615 ms
Script Parsing & Compilation492 ms
Parse HTML & CSS180 ms
Rendering131 ms
Garbage Collection122 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
USDA Logo div.usa-navbar > div.usa-logo > a.usda-logo > img.usda-logo-img
www.usda.gov/themes/custom/usda_uswds/img/usda-symbol.svg
food safety recalls div.paragraph > a > div.image > img
Forest Service logo div.paragraph > a > div.image > img
Eat Real Food div.paragraph > a > div.image > img
div.paragraph > a > div.image > img div.paragraph > a > div.image > img

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 48 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 3 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 100 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
○INP breakdown
○Avoid large layout shifts
91

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.field > div > div.field > img div.field > div > div.field > img
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
div.paragraph > a > div.image > img div.paragraph > a > div.image > img

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.grid-container > div.grid-row > div.tablet:grid-col > a div.grid-container > div.grid-row > div.tablet:grid-col > a
div.grid-container > div.grid-row > div.tablet:grid-col > a div.grid-container > div.grid-row > div.tablet:grid-col > a
div.col-4 > div.footer-social-wrapper > div.footer-social-set > a.usa-link-rss div.col-4 > div.footer-social-wrapper > div.footer-social-set > a.usa-link-rss

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.

○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
●Input buttons have discernible text.
●`[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
●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
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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
○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.
○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
69

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.field > div > div.field > img div.field > div > div.field > img
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
div.tablet:grid-col > a > div.image > img div.tablet:grid-col > a > div.image > img
div.paragraph > a > div.image > img div.paragraph > a > div.image > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
●Page has successful HTTP status code
●Links are crawlable
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback