This website audit report analyzes https://omipsychiatry.com/ across 12 critical dimensions with actionable recommendations.
https://omipsychiatry.com/
47Poorout of 100
Website Audit Report
Psychiatry and TMS in Baltimore, MD - Healing Begins Here
August 6, 2026 at 10:39 AM EDT 113ms response HTTPS Secure
Executive Summary
https://omipsychiatry.com/ scores 47/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 1456 words, 11 images, and 1 schema blocks. Data confidence: 95%. Sustainability score: 90/100. Focus on the top recommendations below to improve your score.
113ms
Response Time
1,456
Word Count
11
Images
124
Links
Website Preview
Visit SiteLoading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h5 (skips h3), h3 → h5 (skips h4)
2[SEO] Missing Twitter tags: twitter:title, twitter:description, twitter:image
3[SEO] 1 broken anchor links detected
4[SEO] 19 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
6[SEO] High dofollow external link count (19) — excessive link equity leakage
7[SEO] Primary keyword "psychiatry and tms" not found in H1
8[SEO] Primary keyword missing from first paragraph
9[SEO] Low readability score (37 Flesch) — content is hard to read
10[SEO] Very high internal link density (69.4/1k words) — may appear spammy
Top Recommendations
1[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2[Impact: Medium | Effort: Medium] Fix broken anchor links — ensure all #hash targets exist on the page
3[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5[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
6[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
7[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
8[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
9[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10[Impact: Medium | Effort: Medium] Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
11[Impact: Medium | Effort: Low] Add <meta property="article:published_time"> for content freshness signals in social shares
12[Impact: High | Effort: Medium] Reduce internal link density — excessive linking dilutes individual link value
Detailed Category Analysis
Key Findings
1Title tag is 57 characters — within optimal 50–60 range (Google 2025-2026)
2Meta description is 141 characters — within optimal 140–160 range (2025-2026)
3Single H1 tag present: "Omi Psychiatry & TMS"
4Canonical URL is set and matches the page URL
5Complete Open Graph tags (title, description, image, url, type)
6HTML lang attribute set to "en-US"
7Favicon present
8101 internal links help establish site architecture
919 external links provide reference signals
10Content length of 1456 words is adequate
11124 total links — within recommended range
12URL length (26 chars) is within optimal range
13No redirect chain — direct URL resolution
14Healthy internal link ratio: 81% of links are internal
15Primary keyword not in URL — acceptable for homepage/root URLs
16Moderate E-E-A-T signals (3 indicators)
17og:locale set to "en_US"
18OG image dimensions ≥1200×630px — optimal for all platforms
19article:modified_time present — update recency signal
20Twitter card uses summary_large_image — maximum visual impact
21Low passive voice ratio (5%) — clear, active writing style
22Table of Contents detected — improves dwell time and jump-link navigation
23Zero-click optimized: 0 TL;DR/summary block(s) + 2 definition-style lead paragraph(s)
24Moderate entity presence: Omi Psychiatry, Contact Us, Learn More About Us Treatment Services
25Social share buttons detected: ShareThis
26OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Heading hierarchy gaps: h1 → h3 (skips h2), h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h5 (skips h3), h3 → h5 (skips h4)
2Missing Twitter tags: twitter:title, twitter:description, twitter:image
31 broken anchor links detected
419 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
5Title and description are identical to Open Graph tags — missed optimization opportunity
6High dofollow external link count (19) — excessive link equity leakage
7Primary keyword "psychiatry and tms" not found in H1
8Primary keyword missing from first paragraph
9Low readability score (37 Flesch) — content is hard to read
10Very high internal link density (69.4/1k words) — may appear spammy
11Primary keyword "psychiatry and tms" not found in body content
Recommendations to Reach 100%
1Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2Fix broken anchor links — ensure all #hash targets exist on the page
3Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
4Customize og:title and og:description separately from page title/meta description for better social sharing CTR
5Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
6Include your primary keyword in the H1 heading for strongest on-page SEO signal
7Include your primary keyword naturally in the first paragraph to establish topical relevance early
8Include your primary keyword in the URL slug for improved crawlability and click-through rates
9Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
10Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
11Add <meta property="article:published_time"> for content freshness signals in social shares
12Reduce internal link density — excessive linking dilutes individual link value
13Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
14SEO: 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: 113ms
2HTML size is 273KB — acceptable
3Responsive images with srcset detected
4Most images have explicit width/height attributes (prevents layout shift)
5Preloaded resources: style, style, style
6font-display property detected — reduces invisible text during font loading
7Cache-Control header with max-age is set
8HTTP/3 (QUIC) detected — fastest connection protocol
9CDN detected: Cloudflare — reduces latency for global users
10Brotli compression enabled — best-in-class compression
111 third-party script(s) — manageable count
12Estimated INP: ~145ms — within Google's "good" threshold (<200ms)
Issues Found
113 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
418 inline <style> blocks
519 inline scripts
6Moderate CSS payload (~421KB)
7Moderate JavaScript payload (~668KB)
817 font files loaded — excessive font weight
99 render-blocking CSS files — delays first paint
10Estimated CSS bundle ~511KB — above optimal
11Estimated LCP: ~2533ms — needs improvement (goal: <2.5s)
12Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
13Web fonts loaded without preload — causes FOIT/FOUT flash
14Basic analytics only — missing event tracking or tag management
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
4Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
5Extract inline styles into external CSS files for better caching and maintainability
6Move inline scripts to external files with defer attributes
7Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
8Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
9Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
10Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
11Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
12Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
13Optimize Largest Contentful Paint: preload hero image, reduce render-blocking resources, use CDN for static assets
14Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
15Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
16Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Responsive images via srcset serve appropriate sizes per device
6Mobile-responsive hamburger menu detected
Issues Found
1No theme-color meta tag
2No web app manifest found
3Viewport disables user zoom (maximum-scale=1 or user-scalable=no)
4Fixed-width elements detected (>800px) — may cause horizontal scrolling on mobile
5Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
6Only 3 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
3Consider implementing a service worker for offline support and faster repeat visits
4Remove maximum-scale=1 and user-scalable=no from viewport meta — users must be able to zoom for accessibility (WCAG 1.4.4)
5Replace fixed pixel widths with relative units (%, vw, max-width) to prevent horizontal overflow on small screens
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
9Add :active / touch-action CSS for tactile feedback on mobile interactions
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
2Permissions-Policy header restricts browser features
3Server via CDN proxy (cloudflare) — header added by infrastructure, not application
4No cookie security issues detected
5Privacy policy link detected
6Permissions-Policy restricts 2 feature(s) — consider expanding to more features
7Rate limiting recommended for form endpoints
8No stack traces or sensitive error details exposed in responses
9No obvious secret/API-key patterns exposed in page source
10Client-side library inventory (SBOM): WordPress
1113 script resource(s) catalogued for software-composition review
12No common sensitive paths (.git, .env, server-status, …) were publicly accessible
13Password-reset flow detected — ensure reset tokens are single-use, time-limited and delivered out-of-band
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
619 external links missing rel="noopener noreferrer" — security risk
7No cookie consent banner detected
8No Subresource Integrity (SRI) on external scripts
9Server-side software version disclosed: Divi v.4.27.7 — enables version-based vulnerability (CVE) lookups
10Additional technology fingerprints exposed: Generator meta tag: Divi v.4.27.7
11security.txt file is missing — no standardized channel for reporting vulnerabilities
122 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
131 state-changing POST form(s) show no visible anti-CSRF token (heuristic — SameSite cookies may still protect them)
141 javascript: URL(s) found — a legacy XSS/injection vector
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Cross-Origin-Opener-Policy: same-origin-allow-popups
7Add Cross-Origin-Resource-Policy: cross-origin
8Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
9Implement a cookie consent banner for GDPR/ePrivacy compliance
10Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
11Expand Permissions-Policy to restrict camera, microphone, geolocation, payment, usb, and autoplay
12Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
13Suppress version numbers in the Server / X-Powered-By headers and generator meta tag, and keep the framework patched to its latest release to close known CVEs [Impact: High | Effort: Low]
14Add 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]
15If 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]
16Include 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]
17Replace javascript: URLs with proper event handlers and href targets [Impact: Low | Effort: Low]
18A06 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.
19A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
20A07 Authentication Failures: cookies do not use the __Host-/__Secure- prefix. Prefix session cookies with __Host- (with Secure, Path=/, no Domain) and add the Partitioned (CHIPS) attribute for cross-site isolation.
21A08 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.
22A09 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 11 images have alt attributes
4Rich ARIA implementation: 14 elements with ARIA attributes
5Focus styles detected for keyboard navigation
6No major HTML nesting or validity issues detected
Issues Found
1Missing landmarks: main
22 form(s) missing proper labels
32 button(s) missing accessible labels
4Heading hierarchy has gaps — confusing for screen readers
52 button(s) with no accessible label
61 focusable element(s) inside aria-hidden containers
Recommendations to Reach 100%
1Add semantic landmark elements: <main>
2Add <label> elements associated with every form input via for/id attributes
3Add text content or aria-label to all buttons
4Add text content, aria-label, or title to all buttons — icon-only buttons need aria-label (WCAG 4.1.2)
5Remove focusable elements (links, buttons, inputs) from aria-hidden regions — they trap keyboard users in invisible content
6Accessibility: 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):
2Strong semantic markup: header, nav, article, footer, section
3Complete social metadata (OG + Twitter Card)
410 strong entity mentions (bold/emphasized text)
5Social presence signals: facebook, instagram
611 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9High RAG-friendliness (88/100): 0 headings with IDs, 11 section anchors
10Content provenance signals detected (citations with sources, attributed claims)
11Content freshness signals present (dateModified/datePublished/time elements)
12Good HTML-to-text ratio (66%) — AI crawlers can extract content efficiently
Issues Found
1No breadcrumb navigation
2No FAQ or Q&A content patterns found
3No sitemap reference found
4robots.txt has no Sitemap directive
5No llms.txt file found — AI models cannot find structured guidance for your site
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
4Add an FAQ section with FAQPage schema to increase chances of AI engine citations
5Create and reference an XML sitemap for AI crawler discoverability
6Add a Sitemap: directive to your robots.txt pointing to your XML sitemap for AI and search crawler discoverability
7Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
8Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
9Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
Key Findings
1Moderate content depth (1456 words)
2Strong entity emphasis: 10 key terms highlighted
3Structured content: 18 lists, 0 tables — easily parsed by AI
4Good paragraph length for readability and AI parsing
511 external citations — strong reference density for AI model training
6Strong CRO: 6 clear call-to-action elements detected
7Above-the-fold CTA detected — captures immediate visitor attention
8Good form usability score: 100/100
9Trust signals present: HTTPS Security, Privacy Policy
10Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Low semantic markup ratio — 314 divs vs 7 semantic elements
3Weak E-E-A-T schema signals
4No author or expertise signals
5No social proof elements
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
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
4Add Speakable schema markup to help voice assistants identify the most important content
5Include specific statistics, percentages, and data points that AI models can extract and cite in responses
6Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
7Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
8Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
9AIO: primary entity name is inconsistent across title, H1 and schema "name". Align the brand/entity term across all three so AI systems resolve a single, unambiguous entity.
Key Findings
118 lists provide scannable, AI-friendly content
2Comprehensive content depth (1456 words) supports AI citation
310 emphasized terms suggest unique, quotable insights
4Content is fresh (updated within 30 days) — strong recency signal
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
4No hreflang tags — generative engines cannot determine language/region targeting
5No 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
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 specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
8Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
10GEO: only 1/18 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
Key Findings
1Short paragraphs are well-suited for answer extraction
218 lists provide scannable answers for People Also Ask
317 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
4Content length and paragraph structure are voice-search optimized
Issues Found
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
Recommendations to Reach 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
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
5Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Consider adding video content with VideoObject schema for multimedia search results
7AEO: 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: 4108016575, email: [email protected]
2Phone number(s) visible: 4108016575, 12998879
3Email address found: [email protected]
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%
1Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
5Add 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:
2All structured data uses JSON-LD format — Google's recommended format
3No schema validity issues detected
4Schema nesting depth: 3 levels — rich entity relationships
5Schema.org: a connected @graph with 25 entity types is present — strong structured-data maturity.
Issues Found
1Only basic schema implementation
2No top-tier schema types found (Organization, Product, Article, FAQPage, BreadcrumbList, WebSite)
3No sameAs properties in schema — missing entity disambiguation
4No rich results eligibility detected
Recommendations to Reach 100%
1Expand structured data with more specific schema types relevant to your content
2Add at least Organization and WebSite schema — these are foundational for any website
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: Organization, WebSite
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
10Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
11Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
12Schema.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.
13Schema.org (maximize): local-business signals (address, hours, phone) detected but no LocalBusiness schema. Add LocalBusiness with address, geo, openingHoursSpecification and telephone for local rich results.
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
6Accessible 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 — 314 divs vs 7 semantic elements
510 elements with tabindex="-1" — may hide content from keyboard users
6Moderate cognitive load from interactive patterns
75 heading level skip(s) — confuses screen reader navigation
8No form error identification detected
9Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
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
5Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
6Review animation and notification patterns for cognitive accessibility
7Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
8Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
9Ensure sticky headers/footers do not fully obscure the keyboard focus indicator. Use scroll-padding-top or ensure focus remains visible under overlapping elements (WCAG 2.4.11 AA)
10Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
11WCAG 2.2 (1.4.13 Content on Hover/Focus): 9 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.