United Stated · New York Completed: Apr 21, 2026 19:39 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 5.9 MB (5.0 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/93d286a3-a917-4d8f-87bd-464a0b876395)<a href="https://beavercheck.com/results/93d286a3-a917-4d8f-87bd-464a0b876395"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fus.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fus.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 12.1s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~27%.
Page takes 12.1s to load
+12% bounceUsers abandon at ~3s — you're 9.6s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
High main-thread blocking time
+2% bouncePage is non-interactive for 302ms after first paint
Fix: Defer third-party scripts and split large bundles
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
1 form field(s) without a label
+2% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€425 investment → €2,545/month returns + EUR 500,000 risk avoided
€425
5h · 5 findings
€2,545 /mo
~€30,542 / year
EUR 500,000
if kept compliant
€128 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€41,668 / month at risk
~€500,014 / year if left unfixed
€500,000
+2 more
€1.17 /mo
15824.7 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
2.19 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.13 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
302 ms
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.
5.29 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.
12.67 s
Audit breakdown by category with detailed findings.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
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.
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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 |
|---|---|---|
| us.org/assets/css/style.css?v=1.1.3 | 50.6 KiB | 1.1 s |
| us.org/assets/js/lib/modernizr.min.js?v=1.0 | 12.7 KiB | 631 ms |
| us.org/assets/css/bootstrap-grid.min.css | 50.5 KiB | 841 ms |
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 | |
|---|---|---|---|
aea.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/aea_us_org.png | 1.1 MiB | 1.1 MiB |
macaus.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/macaus_us_org.png | 1.0 MiB | 1.0 MiB |
cfth.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/cfth_us_org.png | 913.4 KiB | 907.9 KiB |
bemindful.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/bemindful_us_org.png | 768.2 KiB | 762.7 KiB |
eloiministries.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/eloiministries_us_org.png | 424.9 KiB | 420.8 KiB |
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img | us.org/assets/img/domain-comparison-table-mobile.png | 37.5 KiB | 29.3 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| us.org/assets/css/style.css?v=1.1.3 | 50.6 KiB | 15.9 KiB |
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 |
|---|---|---|
| us.org/assets/js/search.js?v=1.1.0 | 15.9 KiB | 7.5 KiB |
| us.org/assets/js/home.js?v=1.0.1 | 9.5 KiB | 4.6 KiB |
| us.org/assets/js/main.js?v=1.0.1 | 4.8 KiB | 2.0 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| us.org/assets/css/bootstrap-grid.min.css | 50.2 KiB | 49.6 KiB |
| us.org/assets/css/style.css?v=1.1.3 | 50.4 KiB | 31.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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-PZ7W4HK7M7&cx=c>m=4e64h1h1 | 155.5 KiB | 65.7 KiB |
| www.googletagmanager.com/gtag/js?id=G-L43H196XDL&cx=c&_slc=1 | 147.0 KiB | 65.6 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHPDQJT | 125.1 KiB | 63.3 KiB |
| us.org/assets/js/lib/jquery-3.5.1.min.js | 87.4 KiB | 59.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 minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 851 ms |
| Other | 721 ms |
| Style & Layout | 300 ms |
| Script Parsing & Compilation | 189 ms |
| Rendering | 86 ms |
| Parse HTML & CSS | 30 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img | us.org/assets/img/domain-comparison-table-mobile.png |
div.row > div.col-12 > div.home-accent__img > img.accent-img div.row > div.col-12 > div.home-accent__img > img.accent-img | us.org/assets/img/icons/oversized-icon-usorg.svg |
.US.ORG div.container > div.home-hero > div#search > img.home-logo | us.org/assets/img/logos/usorg-primary.svg |
.US.ORG div.col-12 > div.contact-info-wrapper > div.contact-info > img.contact-info-logo | us.org/assets/img/logos/usorg-primary.svg |
Unmatched Availability ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-unmatched-avail.svg |
.US.ORG div.row > div.header-logo-container > a > img.header-logo | us.org/assets/img/logos/usorg-white-single-color.svg |
.US.ORG div.site-footer__section > div.site-footer__logo > a > img.logo--footer | us.org/assets/img/logos/usorg-white-single-color.svg |
No Geographic Restrictions ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-no-restrictions.svg |
Global Trust with Local Focus ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-global-trust.svg |
A Dedicated Space for U.S.-Focused Organizations ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-dedicated-space.svg |
Ideal for All Types of Organizations ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-ideal-all-types.svg |
SEO & Public Recognition ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-seo.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.ds__form-container > div#ds__search-form > div.form__input-group > input.avail-prefix-input div.ds__form-container > div#ds__search-form > div.form__input-group > input.avail-prefix-input |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main > section.section__home-hero > div.home-hero__arrow-down > a.arrow-down__arrow main > section.section__home-hero > div.home-hero__arrow-down > a.arrow-down__arrow |
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.
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 |
|---|
MENU div.container > div.row > div.nav-container > button#mobile-nav-toggle |
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 |
|---|---|
| Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md. | www.google-analytics.com/analytics.js line 92, col 278 |
| Unload event listeners are deprecated and will be removed. | us.org/assets/js/home.js?v=1.0.1 line 275, col 11 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
886 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.09 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
11 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.088
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
886 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.
2.51 s
Audit breakdown by category with detailed findings.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
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.
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.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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 |
|---|---|---|
| us.org/assets/css/style.css?v=1.1.3 | 50.6 KiB | 503 ms |
| us.org/assets/js/lib/modernizr.min.js?v=1.0 | 12.7 KiB | 303 ms |
| us.org/assets/css/bootstrap-grid.min.css | 50.5 KiB | 303 ms |
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 | |
|---|---|---|---|
aea.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/aea_us_org.png | 1.1 MiB | 1.0 MiB |
macaus.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/macaus_us_org.png | 1.0 MiB | 1.0 MiB |
cfth.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/cfth_us_org.png | 913.4 KiB | 899.5 KiB |
bemindful.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/bemindful_us_org.png | 768.2 KiB | 754.3 KiB |
eloiministries.us.org div.home-carousel-item > div.site-preview > a.site-preview__link > img | us.org/assets/img/sites/eloiministries_us_org.png | 424.9 KiB | 414.6 KiB |
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img | us.org/assets/img/domain-comparison-table-desktop.png | 57.1 KiB | 43.3 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| us.org/assets/css/style.css?v=1.1.3 | 50.6 KiB | 15.9 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| us.org/assets/css/bootstrap-grid.min.css | 50.2 KiB | 49.1 KiB |
| us.org/assets/css/style.css?v=1.1.3 | 50.4 KiB | 23.1 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
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 |
|---|---|---|
| us.org/assets/js/search.js?v=1.1.0 | 15.9 KiB | 7.5 KiB |
| us.org/assets/js/home.js?v=1.0.1 | 9.5 KiB | 4.6 KiB |
| us.org/assets/js/main.js?v=1.0.1 | 4.8 KiB | 2.0 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-PZ7W4HK7M7&cx=c>m=4e64k0h2 | 155.4 KiB | 66.3 KiB |
| www.googletagmanager.com/gtag/js?id=G-L43H196XDL&cx=c&_slc=1 | 147.1 KiB | 65.6 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WHPDQJT | 124.9 KiB | 63.5 KiB |
| us.org/assets/js/lib/jquery-3.5.1.min.js | 87.4 KiB | 59.8 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img | us.org/assets/img/domain-comparison-table-desktop.png |
div.row > div.d-none > div.home-unlock__img > img div.row > div.d-none > div.home-unlock__img > img | us.org/assets/img/icons/usorg-mag-glass-location.svg |
.US.ORG div.container > div.home-hero > div#search > img.home-logo | us.org/assets/img/logos/usorg-primary.svg |
.US.ORG div.col-12 > div.contact-info-wrapper > div.contact-info > img.contact-info-logo | us.org/assets/img/logos/usorg-primary.svg |
Unmatched Availability ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-unmatched-avail.svg |
.US.ORG div.row > div.header-logo-container > a > img.header-logo | us.org/assets/img/logos/usorg-white-single-color.svg |
.US.ORG div.site-footer__section > div.site-footer__logo > a > img.logo--footer | us.org/assets/img/logos/usorg-white-single-color.svg |
No Geographic Restrictions ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-no-restrictions.svg |
Global Trust with Local Focus ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-global-trust.svg |
A Dedicated Space for U.S.-Focused Organizations ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-dedicated-space.svg |
Ideal for All Types of Organizations ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-ideal-all-types.svg |
SEO & Public Recognition ul.brand-why__content--list > li.brand-why > div.brand-why__image-wrapper > img.brand-why__image | us.org/assets/img/icons/icon-usorg-seo.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.ds__form-container > div#ds__search-form > div.form__input-group > input.avail-prefix-input div.ds__form-container > div#ds__search-form > div.form__input-group > input.avail-prefix-input |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main > section.section__home-hero > div.home-hero__arrow-down > a.arrow-down__arrow main > section.section__home-hero > div.home-hero__arrow-down > a.arrow-down__arrow |
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.
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 |
|---|---|
| Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md. | |
| Unload event listeners are deprecated and will be removed. | us.org/assets/js/home.js?v=1.0.1 line 275, col 11 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img section.section__home-chart > div.chart__wrapper > div.col-12 > img.chart__img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback