Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
a flagpoles with a dome in the background div.accent-primary > a.block > picture.block > img.block | /https://www.uschamber.com/assets/images/GettyImages-1091... | 70.4 KiB | 25.2 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.uschamber.com/dist/assets/app-D2x5F8HH.css | 58.6 KiB | 750 ms |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| uschamber.com/ | 754 ms |
| www.uschamber.com/ | 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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.uschamber.com/dist/assets/app-D2x5F8HH.css | 58.4 KiB | 54.6 KiB |
| #onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} … | 19.3 KiB | 16.9 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=AW-950327711&cx=c>m=4e64h1 | 147.9 KiB | 105.9 KiB |
| www.googletagmanager.com/gtag/js?id=G-JYLFZFS1C9&cx=c>m=4e64h1 | 175.7 KiB | 70.3 KiB |
| www.googletagmanager.com/gtag/js?id=G-V7HPP6PE41&cx=c>m=4e64h1 | 157.0 KiB | 64.7 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-K46XMWV | 168.2 KiB | 58.6 KiB |
| www.googletagmanager.com/gtag/js?id=AW-950327711 | 147.9 KiB | 54.7 KiB |
| cookie-cdn.cookiepro.com/scripttemplates/202209.2.0/otBannerSdk.js | 90.8 KiB | 49.4 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 33.7 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.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.0 s |
| Other | 2.9 s |
| Style & Layout | 1.4 s |
| Script Parsing & Compilation | 502 ms |
| Parse HTML & CSS | 374 ms |
| Garbage Collection | 127 ms |
| Rendering | 110 ms |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.queryly.com/js/queryly.v4.js | 10.1 KiB | 4.1 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
ARIA
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
Menu div.container > ul.uscc-header-primary-actions > li#MenuBurgerListItem > button.burger-btn |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Spotlight on Small Business div.flex > div.flex-col > h2.f-heading-2 > a.flex |
Economy div.flex > div.flex-col > h2.f-heading-2 > a.flex |
International div.flex > div.flex-col > h2.f-heading-2 > a.flex |
Artificial Intelligence div.flex > div.flex-col > h2.f-heading-2 > a.flex |
For the Pursuit: The U.S. Chamber Story div.relative > span.block > strong.f-heading-expressive-1 > a.hover:text-link-off |
Deep Dives on Workforce Data div.flex > div.flex-col > h2.f-heading-2 > a.flex |
The State of American Business
U.S. Chamber President and CEO Suzanne P. Clark … div.blocks > ul.grid > li > a.block |
Brought to You by American Business
America’s businesses are working together –… div.blocks > ul.grid > li > a.block |
America Works Initiative
We are calling on elected officials and the federal an… div.blocks > ul.grid > li > a.block |
Growing America's Future
Competitive, pro-growth tax policy is essential to gro… div.blocks > ul.grid > li > a.block |
Small Business
Small Business Grant Program Awards
Wednesday, April 29
09:00 AM… div.blocks > ul.grid > li > a.block |
Health Care
2026 Health Summit
Thursday, April 30
09:15 AM EDT - 05:30 PM EDT
U… div.blocks > ul.grid > li > a.block |
Security and Resilience
2026 Building Resilience Conference
Tuesday, May 05 - W… div.blocks > ul.grid > li > a.block |
Technology
Information and news for businesses about the latest advances in tec… div.blocks > ul.grid > li > a.block |
Workforce
Information on how businesses can adapt their workforce development a… div.blocks > ul.grid > li > a.block |
Health Care
Information about how to make quality health care more affordable, … div.blocks > ul.grid > li > a.block |
Best Practices
General
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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.