usawire.com — Website Report

Enable HTTP Strict Transport Security to force HTTPS connections.

# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }

Server responded in 4.7s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance.

Your page loads 66 external JavaScript files. Each requires a network request. Bundle scripts and defer non-critical ones to improve load time.

64 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Add a Referrer-Policy header to control information leakage.

# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }

Add a Permissions-Policy header to control browser feature access.

# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }

Form inputs should have associated labels or aria-label attributes so screen readers can identify them.

Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.

Your HTML is 286KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

Loading 38 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.

5 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.

<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.

<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
  <h1>Page Title</h1>
  <p>Your primary content here...</p>
</main>

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>

Found 14 HTML comments. Remove unnecessary comments in production to reduce file size.