This website audit report analyzes https://NSA.GOV across 12 critical dimensions with actionable recommendations.
https://NSA.GOV
42Poorout of 100
Website Audit Report
National Security Agency | Central Security Service
August 18, 2026 at 7:33 AM EDT 176ms response HTTPS Secure
Executive Summary
https://NSA.GOV scores 42/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 785 words, 7 images, and 1 schema blocks. Data confidence: 85%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
176ms
Response Time
785
Word Count
7
Images
129
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Meta description may be truncated (286 chars)
2[SEO] Heading hierarchy gaps: h2 → h5 (skips h3)
3[SEO] Missing canonical URL
4[SEO] No Open Graph tags found
5[SEO] No Twitter Card tags found
6[SEO] 24 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
7[SEO] Title and H1 share no keywords — misaligned topic signals
8[SEO] High dofollow external link count (26) — excessive link equity leakage
9[SEO] Primary keyword "national security agency" not found in H1
10[SEO] Primary keyword missing from first paragraph
Top Recommendations
1[Impact: High | Effort: Low] Trim your meta description to under 160 characters to prevent truncation
2[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3[Impact: High | Effort: Low] Add a <link rel="canonical"> tag pointing to the preferred version of this page
4[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
5[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
6[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
7[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
8[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
10[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
11[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
12[Impact: High | Effort: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
Detailed Category Analysis
Key Findings
1Title tag is 51 characters — within optimal 50–60 range (Google 2025-2026)
2Single H1 tag present: "Generating foreign intelligence insights.
Applying cybersecu…"
3HTML lang attribute set to "en-US"
4Favicon present
5103 internal links help establish site architecture
626 external links provide reference signals
7Content length of 785 words is adequate
8129 total links — within recommended range
9URL length (20 chars) is within optimal range
10No redirect chain — direct URL resolution
11Healthy internal link ratio: 80% of links are internal
12Good anchor text diversity: 69% unique anchor texts
13Primary keyword not in URL — acceptable for homepage/root URLs
14Optimal keyword density: "national security agency" at 1.9% (5 occurrences)
15Moderate entity presence: National Security Agency, United States, Search Search
Issues Found
1Meta description may be truncated (286 chars)
2Heading hierarchy gaps: h2 → h5 (skips h3)
3Missing canonical URL
4No Open Graph tags found
5No Twitter Card tags found
624 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
7Title and H1 share no keywords — misaligned topic signals
8High dofollow external link count (26) — excessive link equity leakage
9Primary keyword "national security agency" not found in H1
10Primary keyword missing from first paragraph
11Weak E-E-A-T signals (1 indicators)
12Very high internal link density (131.2/1k words) — may appear spammy
13No social sharing buttons/widgets detected
14Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Trim your meta description to under 160 characters to prevent truncation
2Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3Add a <link rel="canonical"> tag pointing to the preferred version of this page
4Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
5Add Twitter Card meta tags for better social media previews
6Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
7Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
8Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9Include your primary keyword in the H1 heading for strongest on-page SEO signal
10Include your primary keyword naturally in the first paragraph to establish topical relevance early
11Include your primary keyword in the URL slug for improved crawlability and click-through rates
12Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
13Link to a Contact page — essential trust signal for E-E-A-T and local SEO
14Reduce internal link density — excessive linking dilutes individual link value
15Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
16Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
17Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
18SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Excellent server response time: 176ms
2Lean HTML document: 99KB
30 async and 1 deferred scripts
4Gzip compression enabled
51 third-party script(s) — manageable count
Issues Found
123 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4No responsive image srcset found
5Only 0/7 images have width/height attributes
6No font-display property found
7No effective Cache-Control header
87 inline <style> blocks
911 inline scripts
10Large CSS payload (~725KB across 24 files) — slows rendering
11Heavy JavaScript payload (~1223KB across 24 files)
12HTTP/1.1 detected — no multiplexing
13No CDN detected
14No resource hints found
1524 render-blocking CSS files — delays first paint
16Estimated CSS bundle ~965KB — above optimal
17Potential long-task scripts: Heavy third-party: Universal-Federated-Analytics-8.7.js?age, Inline script (~16KB)
18Poor estimated LCP: ~4796ms — exceeds 4s threshold
19Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
20Estimated INP: ~221ms — needs improvement (goal: <200ms)
21No analytics tracking detected — flying blind on user behavior
Recommendations to Reach 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add loading="lazy" to below-the-fold images to improve initial page load
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Use srcset and sizes attributes on images to serve appropriately sized images per device
5Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
6Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
7Preload critical resources (fonts, hero images) with <link rel="preload">
8Add font-display: swap to web font declarations to show fallback text while fonts load
9Set Cache-Control headers with appropriate max-age to leverage browser caching
10Extract inline styles into external CSS files for better caching and maintainability
11Move inline scripts to external files with defer attributes
12Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
13Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
14Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
15Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
16Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
17Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
18Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
19Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
20Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
21Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
22Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
23Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
24Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
25Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
26Performance: only 0/7 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
Key Findings
1Viewport meta tag present: width=device-width,initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Mobile-responsive hamburger menu detected
5Touch feedback CSS detected (active states or touch-action)
Issues Found
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
4No responsive image srcset — mobile users may download oversized images
5Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
6Only 1 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
Recommendations to Reach 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
3Add <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Implement srcset to serve smaller images on mobile devices, saving bandwidth
6Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
7Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
8Add env(safe-area-inset-*) CSS for proper display on notched/island devices
9Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
10Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4X-Frame-Options header prevents clickjacking
5Server header not exposing technology details
6No cookie security issues detected
7Subresource Integrity (SRI) on 1 resource(s) — prevents CDN tampering
8jQuery 3.6.0 — current version
9Rate limiting recommended for form endpoints
10No server software/technology fingerprints exposed in headers or markup
11No stack traces or sensitive error details exposed in responses
12No obvious secret/API-key patterns exposed in page source
1324 script resource(s) catalogued for software-composition review
14No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Content-Security-Policy header
2Missing Referrer-Policy header
3Missing Permissions-Policy header
424 external links missing rel="noopener noreferrer" — security risk
5HSTS header present but missing preload directive
6No privacy policy detected
7No cookie consent banner detected
8security.txt file is missing — no standardized channel for reporting vulnerabilities
91 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
10Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
111 state-changing POST form(s) show no visible anti-CSRF token (heuristic — SameSite cookies may still protect them)
12Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment — potential DOM-based XSS vectors
13Access-Control-Allow-Origin: * — the API is readable by any website
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
3Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
4Add Cross-Origin-Opener-Policy: same-origin-allow-popups
5Add Cross-Origin-Resource-Policy: cross-origin
6Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
7Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
8Add a privacy policy link — required by GDPR, CCPA, and builds user trust
9Implement a cookie consent banner for GDPR/ePrivacy compliance
10Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
11Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
12If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]
13Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
14Include a per-request anti-CSRF token (or rely on SameSite=Strict/Lax cookies plus origin checks) on all state-changing forms [Impact: Medium | Effort: Medium]
15Avoid eval, document.write, innerHTML and Function() with untrusted input; prefer textContent, DOM APIs and a trusted-types policy [Impact: Medium | Effort: Medium]
16Restrict Access-Control-Allow-Origin to an explicit allowlist of trusted origins rather than a wildcard [Impact: Medium | Effort: Low]
17A06 Insecure Design: authentication/high-value form present with no visible bot/abuse challenge (CAPTCHA/Turnstile). Add anti-automation, rate limiting and account-lockout as a threat-modeled control.
18A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
19A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
1Language declared: en-US
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 7 images have alt attributes
5All 1 forms have proper labels
6All 9 buttons have accessible labels
7Rich ARIA implementation: 25 elements with ARIA attributes
8Focus styles detected for keyboard navigation
Issues Found
1Heading hierarchy has gaps — confusing for screen readers
25 minor HTML validity issue(s)
37 images missing explicit dimensions — causes layout shifts for screen reader users
Recommendations to Reach 100%
1Review and fix HTML structure issues for better accessibility and cross-browser compatibility
2Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
3Accessibility (WCAG 2.2 1.4.12): 4 element(s) lock text spacing with !important, blocking user spacing overrides. Avoid !important on line-height/letter-spacing/word-spacing.
4Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
11 schema block(s): Organization
2Strong semantic markup: header, nav, section, footer
3FAQ/Q&A content patterns detected — highly valuable for AI citation
4Social presence signals: youtube
58 call-to-action elements detected
6No AI crawlers blocked via meta tags — content accessible to AI search engines
7High RAG-friendliness (100/100): 0 headings with IDs, 58 section anchors
8Content provenance signals detected (citations with sources, attributed claims)
9Good HTML-to-text ratio (23%) — AI crawlers can extract content efficiently
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No sitemap reference found
4No robots.txt file found
5No llms.txt file found — AI models cannot find structured guidance for your site
6No content freshness signals (dateModified, datePublished, <time> elements)
Recommendations to Reach 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add hreflang tags if your site serves multiple languages or regions
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Create a robots.txt file at your domain root — essential for crawler governance and AI SEO strategy
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
10AI Readiness (multimodal): only 29% of images have descriptive alt text (≥15 chars). Rich, standalone alt text lets multimodal models understand and cite your imagery.
Key Findings
1Moderate content depth (785 words)
21 FAQ/Q&A elements detected
35 emphasized entities
4Structured content: 18 lists, 0 tables — easily parsed by AI
525 external citations — strong reference density for AI model training
61 call-to-action element(s) detected
7Trust signals present: HTTPS Security, Privacy Policy
8Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 308 divs vs 4 semantic elements
2Weak E-E-A-T schema signals
3Paragraphs are too long for optimal AI consumption
4No author or expertise signals
5No CTA above the fold
6No social proof elements
Recommendations to Reach 100%
1Expand FAQ section with more questions to increase AI training coverage
2Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
3Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
4Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
5Add Speakable schema markup to help voice assistants identify the most important content
6Include specific statistics, percentages, and data points that AI models can extract and cite in responses
7Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
8Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
9Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
10Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
11Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
118 lists provide scannable, AI-friendly content
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Insufficient structured data for generative engine context
4paragraphs may be too long for featured snippets
5No hreflang tags — generative engines cannot determine language/region targeting
6No statistics or data points in substantial content
Recommendations to Reach 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
7Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
8Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
9Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
10Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
11GEO: only 0/13 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
12GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
118 lists provide scannable answers for People Also Ask
Issues Found
1FAQ content exists but lacks FAQPage schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4Paragraphs too long for answer engine extraction
5No breadcrumb navigation
6Few concise answer paragraphs for snippet extraction
7No direct answer patterns ("X is defined as...", "X refers to...")
8Paragraphs too long for voice assistant extraction
Recommendations to Reach 100%
1Add FAQPage schema markup to your FAQ section for rich snippet eligibility in search results
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
6Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
7Consider adding video content with VideoObject schema for multimedia search results
8Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
9Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
10Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
11AEO: no 40–60 word concise answer directly follows a question heading. Lead each question section with a self-contained ~40–60 word answer to win featured snippets and voice answers.
Key Findings
1NAP information detected: phone: 6389016277
2Phone number(s) visible: 6389016277, 2089877
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
6Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Key Findings
11 JSON-LD block(s) with types: Organization
2All structured data uses JSON-LD format — Google's recommended format
3Some top-tier schemas: Organization
4No schema validity issues detected
5Entity linking via sameAs: 4 external profiles linked — strengthens Knowledge Graph
Issues Found
1Only basic schema implementation
2Schema property completeness averaging 57%
3No rich results eligibility detected
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add more top-tier schema types — consider: LocalBusiness, Product, Article
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: WebSite, FAQPage
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more schema types — diverse structured data improves AI and search engine understanding
9Fill in missing recommended properties for each schema type
10Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
11Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
12Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
13Schema.org (maximize): long-form article content detected but no Article/BlogPosting schema. Add Article with headline, author, datePublished, dateModified, image and publisher for maximal eligibility.
Key Findings
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Focus styles detected for keyboard navigation visibility
4Page language declared — aids assistive technology
5All ARIA roles are valid
6Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
7Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
4Low semantic-to-div ratio — 308 divs vs 4 semantic elements
5No form error identification detected
Recommendations to Reach 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
4Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
5Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
6Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
7WCAG 2.2 (1.4.13 Content on Hover/Focus): 13 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
Limited-Time Offer
All 12 Optimizations — Bundled Into Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.