This website audit report analyzes https://www.war.gov/ across 12 critical dimensions with actionable recommendations.
https://www.war.gov/
45Poorout of 100
Website Audit Report
Home | U.S. Department of War
September 16, 2026 at 10:38 AM EDT 110ms response HTTPS Secure
Executive Summary
https://www.war.gov/ scores 45/100 (F). Strong areas include Accessibility. Priority improvements needed in SEO, Performance, Security. The site has 1296 words, 22 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 75/100. Focus on the top recommendations below to improve your score.
110ms
Response Time
1,296
Word Count
22
Images
268
Links
Website Preview
Visit SiteLoading preview…
Score History
Current scan3 scans recorded· Tap or hover a point for score & time↓ 3 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (29 chars)
2[SEO] Meta description may be truncated (161 chars)
3[SEO] Missing canonical URL
4[SEO] High link count (268) — above recommended range
5[SEO] 27 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6[SEO] Title and H1 share no keywords — misaligned topic signals
7[SEO] High dofollow external link count (71) — excessive link equity leakage
8[SEO] Primary keyword "home" not found in H1
9[SEO] Primary keyword missing from first paragraph
10[SEO] Low readability score (11 Flesch) — content is hard to read
Top Recommendations
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Trim your meta description to under 160 characters to prevent truncation
3[Impact: High | Effort: Low] Add a <link rel="canonical"> tag pointing to the preferred version of this page
4[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
5[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
6[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7[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
8[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
9[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
10[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
11[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
Detailed Category Analysis
Key Findings
1Single H1 tag present: "PEACE THROUGH Strength"
2Clean heading hierarchy with no skipped levels
3Complete Open Graph tags (title, description, image, url, type)
4Complete Twitter Card tags present
5HTML lang attribute set to "en-US"
6Favicon present
7196 internal links help establish site architecture
871 external links provide reference signals
9Content length of 1296 words is adequate
10URL length (20 chars) is within optimal range
11No redirect chain — direct URL resolution
12Healthy internal link ratio: 73% of links are internal
13Primary keyword not in URL — acceptable for homepage/root URLs
14Moderate E-E-A-T signals (3 indicators)
15Twitter card uses summary_large_image — maximum visual impact
16Low passive voice ratio (6%) — clear, active writing style
17Table of Contents detected — improves dwell time and jump-link navigation
18Zero-click optimized: 0 TL;DR/summary block(s) + 2 definition-style lead paragraph(s)
19Moderate entity presence: Joint Chiefs, See More News, United States
20Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
21Social share buttons detected: ShareThis
22Character encoding declared as UTF-8
Issues Found
1Title tag is very short (29 chars)
2Meta description may be truncated (161 chars)
3Missing canonical URL
4High link count (268) — above recommended range
527 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
6Title and H1 share no keywords — misaligned topic signals
7High dofollow external link count (71) — excessive link equity leakage
8Primary keyword "home" not found in H1
9Primary keyword missing from first paragraph
10Low readability score (11 Flesch) — content is hard to read
11Missing og:locale tag — social platforms may guess language/region
12Very high internal link density (151.2/1k words) — may appear spammy
13Low keyword density (0.4%) for "home"
14Multiple <title> tags detected (2) — search engines may use an unintended title
151 image(s) have a missing or empty src — broken images hurt UX and image search
Recommendations to Reach 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Trim your meta description to under 160 characters to prevent truncation
3Add a <link rel="canonical"> tag pointing to the preferred version of this page
4Aim for ≤150–200 total links per page including nav, footer, and content links
5Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
6Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
7Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
8Include your primary keyword in the H1 heading for strongest on-page SEO signal
9Include your primary keyword naturally in the first paragraph to establish topical relevance early
10Include your primary keyword in the URL slug for improved crawlability and click-through rates
11Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
12Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
13Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
14Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
15Add <meta property="article:published_time"> for content freshness signals in social shares
16Add <meta property="article:modified_time"> to signal content freshness
17Reduce internal link density — excessive linking dilutes individual link value
18Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
19OG sharing completeness at 83% — add missing tags for better social previews
20Keep exactly one <title> tag in the document head [Impact: Medium | Effort: Low]
21Provide a valid src for every <img>, or remove the empty tags [Impact: Medium | Effort: Low]
22SEO: 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: 110ms
2HTML size is 206KB — acceptable
31 async and 0 deferred scripts
4Gzip compression enabled
52 third-party script(s) — manageable count
6Lab-proxy estimates — Speed Index ~5396ms, TTI ~9520ms, TBT ~2000ms (estimated from resource composition, not third-party field data)
Issues Found
137 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/22 images have width/height attributes
6No font-display property found
7No effective Cache-Control header
820 inline <style> blocks
916 inline scripts
10Large CSS payload (~769KB across 25 files) — slows rendering
11Heavy JavaScript payload (~1939KB across 38 files)
12268 links increase DOM size and parsing time
13HTTP/1.1 detected — no multiplexing
14No CDN detected
15No resource hints found
1625 render-blocking CSS files — delays first paint
17Estimated CSS bundle ~1019KB — above optimal
18Estimated JS bundle ~2319KB — heavy payload
19Potential long-task scripts: Heavy third-party: Universal-Federated-Analytics-8.7.js?age, Heavy third-party: DVIDSVideoAnalytics.min.js?cdv=2104, Inline script (~16KB)
20Poor estimated LCP: ~6210ms — exceeds 4s threshold
21Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
22Estimated INP: ~255ms — needs improvement (goal: <200ms)
23Basic analytics only — missing event tracking or tag management
24Excessive DOM size (1581 elements) — increases memory use and slows rendering
25Inline JavaScript does not appear minified
26No efficient cache policy (Cache-Control max-age) on the main document
2722 image(s) lack explicit width/height — a common cause of layout shift (CLS)
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
14Reduce links per page to improve DOM parsing performance and reduce memory usage
15Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
16Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
17Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
18Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
19Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
20Reduce JS bundle with code splitting, tree shaking, and dynamic imports. Target <500KB initial JS
21Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
22Critical LCP issue: preload LCP image with fetchpriority="high", inline critical CSS, reduce server response time, eliminate render-blocking scripts
23Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
24Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
25Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
26Reduce DOM node count to under ~1,500 by simplifying markup and paginating long lists (Lighthouse best practice) [Impact: Medium | Effort: Medium]
27Minify JavaScript to reduce parse and transfer time [Impact: Low | Effort: Low]
28Set a Cache-Control header with an appropriate max-age (and immutable for versioned assets) to enable browser caching [Impact: Medium | Effort: Low]
29Add width and height attributes (or CSS aspect-ratio) to every image to reserve space and prevent layout shift [Impact: Medium | Effort: Low]
30Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
31Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
32Performance: only 0/22 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
33Performance: ES modules are used without modulepreload. Add <link rel="modulepreload"> for critical modules to remove waterfall latency on module graphs.
Key Findings
1Viewport meta tag present: width=device-width,initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Touch feedback CSS detected (active states or touch-action)
522 image(s) without explicit width/height — most impactful for layout stability (CLS) on mobile (see Performance for remediation)
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)
7Estimated page weight ~4644KB — heavy for mobile data plans
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
9Reduce page weight below 2MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
10Mobile/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.
11Mobile/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
7Rate limiting recommended for form endpoints
8No server software/technology fingerprints exposed in headers or markup
9No stack traces or sensitive error details exposed in responses
10No obvious secret/API-key patterns exposed in page source
11Client-side library inventory (SBOM): Moment.js
1238 script resource(s) catalogued for software-composition review
13No 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
427 external links missing rel="noopener noreferrer" — security risk
5HSTS header present but missing preload directive
6No privacy policy detected
7No cookie consent banner detected
8No Subresource Integrity (SRI) on external scripts
9Outdated libraries detected: Moment.js (deprecated, use date-fns or Temporal)
10security.txt file is missing — no standardized channel for reporting vulnerabilities
111 email address(es) exposed in page source (e.g. [email protected]) — can be harvested for spam/phishing
12Legacy X-XSS-Protection header present — deprecated and can introduce vulnerabilities in older browsers
13Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment — potential DOM-based XSS vectors
14Access-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
10Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
11Update outdated JavaScript libraries to latest versions — older versions have known security vulnerabilities (CVEs)
12Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
13Add 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]
14If 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]
15Remove the deprecated X-XSS-Protection header and rely on a strong Content-Security-Policy instead [Impact: Low | Effort: Low]
16Avoid eval, document.write, innerHTML and Function() with untrusted input; prefer textContent, DOM APIs and a trusted-types policy [Impact: Medium | Effort: Medium]
17Restrict Access-Control-Allow-Origin to an explicit allowlist of trusted origins rather than a wildcard [Impact: Medium | Effort: Low]
18A03 Software Supply Chain: only 0% of 2 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
19A08 Integrity Failures: dynamic remote script injection detected. Load third-party code with static tags carrying SRI, or gate it behind a strict CSP with Trusted Types to prevent tampered-update execution.
20A09 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 22 images have alt attributes
5All 1 forms have proper labels
6Rich ARIA implementation: 71 elements with ARIA attributes
7Focus styles detected for keyboard navigation
8No major HTML nesting or validity issues detected
Issues Found
11 button(s) missing accessible labels
222 images missing explicit dimensions — causes layout shifts for screen reader users
Recommendations to Reach 100%
1Add text content or aria-label to all buttons
2Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
Key Findings
11 schema block(s): Organization
2Strong semantic markup: header, nav, main, figure, figcaption, time, section, footer
3Complete social metadata (OG + Twitter Card)
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5Social presence signals: twitter, facebook, instagram, linkedin, youtube
66 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8High RAG-friendliness (100/100): 0 headings with IDs, 116 section anchors
9Content provenance signals detected (citations with sources, attributed claims)
10Good HTML-to-text ratio (27%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No sitemap reference found
3No robots.txt file found
4No llms.txt file found — AI models cannot find structured guidance for your site
5No 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
Key Findings
1Moderate content depth (1296 words)
21 FAQ/Q&A elements detected
34 emphasized entities
4Good semantic-to-div ratio: 49 semantic elements
5Structured content: 39 lists, 0 tables — easily parsed by AI
656 external citations — strong reference density for AI model training
7Strong CRO: 3 clear call-to-action elements detected
8Above-the-fold CTA detected — captures immediate visitor attention
9Trust signals present: Trust Badges, HTTPS Security
10Clear value proposition detected in heading elements
Issues Found
1Weak E-E-A-T schema signals
2Paragraphs are too long for optimal AI consumption
3No author or expertise signals
4No social proof elements
Recommendations to Reach 100%
1Expand FAQ section with more questions to increase AI training coverage
2Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
3Break long paragraphs into shorter ones (under 30 words) for better AI comprehension and snippet extraction
4Add Speakable schema markup to help voice assistants identify the most important content
5Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
6Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
7Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
239 lists provide scannable, AI-friendly content
3Comprehensive content depth (1296 words) supports AI citation
49 original data elements (charts, figures, data tables)
Issues Found
1No data tables for AI comparison extraction
2Insufficient structured data for generative engine context
3paragraphs may be too long for featured snippets
4No hreflang tags — generative engines cannot determine language/region targeting
Recommendations to Reach 100%
1Add comparison tables with structured data — generative AI engines frequently cite tabular content
2Include how-to or step-by-step instructional content for generative AI answer inclusion
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Include unique statistics, expert quotes, and original insights that generative AI would want to cite
5Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
6Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
7Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
8GEO: only 1/44 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
9GEO: 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
1Question-answer heading patterns support featured snippet capture
239 lists provide scannable answers for People Also Ask
3Video content detected — supports multimedia answer results
411 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1FAQ content exists but lacks FAQPage schema
2No Speakable schema for voice search
3Paragraphs too long for answer engine extraction
4No breadcrumb navigation
5No direct answer patterns ("X is defined as...", "X refers to...")
6Paragraphs 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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Keep answer paragraphs under 30 words — voice assistants and answer engines prefer concise, direct responses
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
7Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
8AEO: 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: 6391918290
2Phone number(s) visible: 6391918290, 2637202
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
7Local SEO: local business signals present but no explicit city/region in the title, H1 or opening paragraph. Add "City, State" to your title/H1 and intro to reinforce local relevance.
8Local SEO (NAP): a phone number is shown but not declared in structured data. Add telephone (and address) to LocalBusiness schema so NAP is machine-verifiable.
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
Issues Found
1Only basic schema implementation
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 57%
4No 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
9Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
10Fill in missing recommended properties for each schema type
11Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
12Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
13Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
14Schema.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)
21 media element(s) without autoplay
3Relative units (rem/em/clamp) detected — supports text resizing
4Good semantic element usage (49 semantic elements)
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
9Accessible 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
4Moderate cognitive load from interactive patterns
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)
4Review animation and notification patterns for cognitive accessibility
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): 27 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.