This website audit report analyzes http://HomeDepot.com across 12 critical dimensions with actionable recommendations.
http://HomeDepot.com
40Poorout of 100
Website Audit Report
The Home Depot
August 10, 2026 · 22:56 (America/New_York) 497ms response HTTPS Secure301 Redirect
Executive Summary
http://HomeDepot.com scores 40/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 794 words, 89 images, and 2 schema blocks. Data confidence: 90%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
497ms
Response Time
794
Word Count
89
Images
242
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (14 chars)
2[SEO] Meta description may be truncated (229 chars)
3[SEO] No H1 heading found
4[SEO] Heading hierarchy gaps: h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3)
5[SEO] Missing OG tags: og:image
6[SEO] No Twitter Card tags found
7[SEO] Missing favicon
8[SEO] High link count (242) — above recommended range
9[SEO] 11 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
10[SEO] Title and description are identical to Open Graph tags — missed optimization opportunity
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 exactly one H1 tag with your primary keyword to establish page topic
4[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:image
6[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
7[Impact: Medium | Effort: Medium] Add a favicon for brand recognition in browser tabs and bookmarks
8[Impact: Medium | Effort: Medium] Aim for ≤150–200 total links per page including nav, footer, and content links
9[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
10[Impact: High | Effort: Low] Customize og:title and og:description separately from page title/meta description for better social sharing CTR
11[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
12[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
Detailed Category Analysis
Key Findings
1Canonical URL is set and matches the page URL
2HTML lang attribute set to "en"
3228 internal links help establish site architecture
413 external links provide reference signals
5Content length of 794 words is adequate
6URL length (26 chars) is within optimal range
7No redirect chain — direct URL resolution
8SPA framework detected (react) with adequate SSR content
9Healthy internal link ratio: 94% of links are internal
10Good anchor text diversity: 89% unique anchor texts
11Primary keyword not in URL — acceptable for homepage/root URLs
12Optimal keyword density: "the home depot" at 0.8% (2 occurrences)
13Low passive voice ratio (1%) — clear, active writing style
14Moderate entity presence: Stainless Steel, Tool Only, Home Decorators
15Social share buttons detected: ShareThis
Issues Found
1Title tag is very short (14 chars)
2Meta description may be truncated (229 chars)
3No H1 heading found
4Heading hierarchy gaps: h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3), h2 → h5 (skips h3)
5Missing OG tags: og:image
6No Twitter Card tags found
7Missing favicon
8High link count (242) — above recommended range
911 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
10Title and description are identical to Open Graph tags — missed optimization opportunity
11High dofollow external link count (11) — excessive link equity leakage
12Primary keyword missing from first paragraph
13Weak E-E-A-T signals (2 indicators)
14Low readability score (16 Flesch) — content is hard to read
15Missing og:locale tag — social platforms may guess language/region
16Very high internal link density (287.2/1k words) — may appear spammy
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 exactly one H1 tag with your primary keyword to establish page topic
4Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5Add missing Open Graph tags: og:image
6Add Twitter Card meta tags for better social media previews
7Add a favicon for brand recognition in browser tabs and bookmarks
8Aim for ≤150–200 total links per page including nav, footer, and content links
9Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
10Customize og:title and og:description separately from page title/meta description for better social sharing CTR
11Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
12Include your primary keyword naturally in the first paragraph to establish topical relevance early
13Include your primary keyword in the URL slug for improved crawlability and click-through rates
14Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
15Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
16Link to a Contact page — essential trust signal for E-E-A-T and local SEO
17Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
18Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
19Add <meta property="article:published_time"> for content freshness signals in social shares
20Add <meta property="article:modified_time"> to signal content freshness
21Reduce internal link density — excessive linking dilutes individual link value
22Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
23Add engagement signals: related posts section, "Read next" links, and table of contents to increase dwell time
24OG sharing completeness at 67% — add missing tags for better social previews
25SEO: 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: 497ms
275/89 images use lazy loading
3Responsive images with srcset detected
4Most images have explicit width/height attributes (prevents layout shift)
5Preconnect hints for: https://assets.thdstatic.com, https://images.thdstatic.com, https://dam.thdstatic.com
6Preloaded resources: font, font, font, font, image, image, image, image, style
7font-display property detected — reduces invisible text during font loading
84 async and 15 deferred scripts
9Gzip compression enabled
1032 resource hints (preconnect/prefetch/preload) optimize loading
114 font(s) preloaded for faster text rendering
12Estimated LCP: ~1177ms — within Google's "good" threshold (<2.5s)
13Variable fonts detected — reduces total font file downloads
14Server-Timing header present — enables performance debugging
15Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
1Very large HTML: 1259KB
22 render-blocking script(s)
3No WebP or AVIF image formats found
4No effective Cache-Control header
521 inline scripts
6Large CSS payload (~607KB across 1 files) — slows rendering
7Heavy JavaScript payload (~1327KB across 21 files)
8242 links increase DOM size and parsing time
9HTTP/1.1 detected — no multiplexing
10No CDN detected
1119 third-party scripts from 2 domains — significant performance impact
1230 font files loaded — excessive font weight
13Estimated CSS bundle ~617KB — above optimal
14Estimated JS bundle ~1537KB — heavy payload
15Potential long-task scripts: Inline script (~61KB), Heavy third-party: sync.js, Inline script (~173KB)
16Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
17Estimated INP: ~300ms — needs improvement (goal: <200ms)
Recommendations to Reach 100%
1Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
2Add async or defer attributes to render-blocking scripts
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Set Cache-Control headers with appropriate max-age to leverage browser caching
5Move inline scripts to external files with defer attributes
6Reduce CSS payload with PurgeCSS, tree-shaking unused styles, and critical CSS inlining. Aim for <200KB total CSS
7Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
8Reduce links per page to improve DOM parsing performance and reduce memory usage
9Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
10Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
11Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
12Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
13Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
14Reduce JS bundle with code splitting, tree shaking, and dynamic imports. Target <500KB initial JS
15Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
16Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
17Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
18Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
19Performance: only 0/89 images set decoding="async". Add decoding="async" to non-critical images to keep image decode off the main thread.
20Performance: 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.0
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Responsive images via srcset serve appropriate sizes per device
675 images with lazy loading benefit mobile data users
7Orientation handling declared in manifest or meta
8Touch feedback CSS detected (active states or touch-action)
93 internationalization signals detected (hreflang, lang, dir, locale meta)
Issues Found
1No web app manifest found
2Missing Apple touch icon
3Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
4Estimated page weight ~7863KB — heavy for mobile data plans
Recommendations to Reach 100%
1Create a manifest.json for PWA capabilities and add-to-homescreen support
2Add <link rel="apple-touch-icon"> for iOS homescreen icons
3Consider implementing a service worker for offline support and faster repeat visits
4Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
7Mobile/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.
8Mobile/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
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Content-Type-Options: nosniff is set
5Server via CDN proxy (nginx) — header added by infrastructure, not application
6Privacy policy link detected
7Rate limiting recommended for form endpoints
8No stack traces or sensitive error details exposed in responses
9No raw email addresses exposed in page source
10No obvious secret/API-key patterns exposed in page source
11Client-side library inventory (SBOM): React, Swiper
1221 script resource(s) catalogued for software-composition review
13No common sensitive paths (.git, .env, server-status, …) were publicly accessible
14A09: a client-side error/monitoring integration (e.g. Sentry/Datadog) is present — supports security logging & alerting.
Issues Found
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
511 external links missing rel="noopener noreferrer" — security risk
6HSTS header present but missing preload directive
7Cookie security issues: missing Secure flag; missing HttpOnly flag; missing SameSite attribute
8No cookie consent banner detected
9No Subresource Integrity (SRI) on external scripts
10Server technology disclosed via response headers/markup: Server: nginx
11security.txt file is missing — no standardized channel for reporting vulnerabilities
121 javascript: URL(s) found — a legacy XSS/injection vector
13robots.txt discloses sensitive-looking path(s): /*THDLogon*, /custom-blinds/Configurator* — Disallow entries can act as a map for attackers
Recommendations to Reach 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
3Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
4Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
5Add Cross-Origin-Opener-Policy: same-origin-allow-popups
6Add Cross-Origin-Resource-Policy: cross-origin
7Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
8Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
9Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
10Implement a cookie consent banner for GDPR/ePrivacy compliance
11Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
12Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
13Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
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]
15Replace javascript: URLs with proper event handlers and href targets [Impact: Low | Effort: Low]
16Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
17A03 Software Supply Chain: only 0% of 20 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
18A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
19A07 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.
20A08 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.
Key Findings
1Language declared: en
2All 89 images have alt attributes
3All 20 buttons have accessible labels
4Rich ARIA implementation: 83 elements with ARIA attributes
5Focus styles detected for keyboard navigation
Issues Found
1No skip navigation link
2Missing landmarks: main, nav, footer
32 form(s) missing proper labels
4Heading hierarchy has gaps — confusing for screen readers
58 HTML validity issues detected — affects assistive technology parsing
61 button(s) with no accessible label
75 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <nav>, <footer>
3Add <label> elements associated with every form input via for/id attributes
4Fix HTML nesting errors and deprecated elements. Validate at validator.w3.org for WCAG compliance
5Add text content, aria-label, or title to all buttons — icon-only buttons need aria-label (WCAG 4.1.2)
6Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
7Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
12 schema block(s): WebSite, Organization
2Hreflang tags: en, x-default, en-ca, fr-ca, es-mx
3Some semantic elements: section, article, figure
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5Social presence signals: facebook, twitter, pinterest, youtube
65 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 1 sitemap(s) — aids AI crawler discoverability
10High RAG-friendliness (100/100): 0 headings with IDs, 65 section anchors
11Content provenance signals detected (citations with sources, attributed claims)
12Good HTML-to-text ratio (67%) — AI crawlers can extract content efficiently
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No sitemap reference 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
2Increase use of semantic HTML5 elements (article, section, aside, figure) for better AI understanding
3Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
4Create and reference an XML sitemap for AI crawler discoverability
5Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
6Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
7Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
8Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Moderate content depth (794 words)
2Structured content: 8 lists, 0 tables — easily parsed by AI
311 external citations — strong reference density for AI model training
475 statistics/data points — excellent for AI knowledge extraction
51 call-to-action element(s) detected
6Trust signals present: Guarantee, HTTPS Security, Privacy Policy
7Clear value proposition detected in heading elements
Issues Found
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Low semantic markup ratio — 1079 divs vs 43 semantic elements
4Weak E-E-A-T schema signals
5No author or expertise signals
6No CTA above the fold
7No social proof elements
Recommendations to Reach 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
4Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
5Add Speakable schema markup to help voice assistants identify the most important content
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 more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
9Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
10Add 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
28 lists provide scannable, AI-friendly content
32 schema blocks help AI engines understand content context
4Hreflang includes self-referencing tag
5x-default hreflang fallback present
675 data points/statistics — content has original research signals
724 original data elements (charts, figures, data tables)
848 unique insight patterns detected (original research/analysis signals)
Issues Found
1No data tables for AI comparison extraction
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
5GEO: only 1/42 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
Key Findings
1Question-answer heading patterns support featured snippet capture
28 lists provide scannable answers for People Also Ask
Issues Found
1No FAQ content or schema
2No Speakable schema for voice search
3No breadcrumb navigation
4Few concise answer paragraphs for snippet extraction
5No direct answer patterns ("X is defined as...", "X refers to...")
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
3Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
4Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
5Consider adding video content with VideoObject schema for multimedia search results
6Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
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: 6349342
2Phone number(s) visible: 6349342, 2100000000
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): the visible phone number does not match schema telephone. Keep Name/Address/Phone identical across visible content, schema and directories for local ranking consistency.
Key Findings
12 JSON-LD block(s) with types: WebSite, Organization
2All structured data uses JSON-LD format — Google's recommended format
3Moderate schema coverage
4Some top-tier schemas: Organization, WebSite
5Entity linking via sameAs: 6 external profiles linked — strengthens Knowledge Graph
6SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
1WebSite has very few properties (2)
2Schema property completeness averaging 61%
3No rich results eligibility detected
Recommendations to Reach 100%
1Add more top-tier schema types — consider: LocalBusiness, Product, Article
2Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
3Add missing high-impact schemas: Product
4Add BreadcrumbList schema — enables breadcrumb rich results in Google
5Add FAQPage schema to FAQ content — enables expandable rich results
6Consider adding HowTo schema for instructional content
7Add more properties to schema types — aim for at least 5 meaningful properties per type
8Fill in missing recommended properties for each schema type
9Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
10Schema.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.
11Schema.org (maximize): commerce signals detected but no Product schema. Add Product with offers (price, priceCurrency, availability), aggregateRating and review for product rich results.
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Form error/validation feedback detected
5Relative units (rem/em/clamp) detected — supports text resizing
6Focus styles detected for keyboard navigation visibility
7Page language declared — aids assistive technology
8All ARIA roles are valid
9Form error identification mechanisms present (WCAG 3.3.1)
10Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
11Reduced motion enforced: animations disabled when prefers-reduced-motion is set
Issues Found
1Low semantic-to-div ratio — 1079 divs vs 43 semantic elements
2Moderate cognitive load from interactive patterns
36 heading level skip(s) — confuses screen reader navigation
4Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
Recommendations to Reach 100%
1Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
2Review animation and notification patterns for cognitive accessibility
3Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
4Ensure 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)
5Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
6WCAG 2.2 (1.4.13 Content on Hover/Focus): 71 interactive elements rely on native title tooltips, which are not dismissable, hoverable or persistent. Replace with accessible tooltip components.
Limited-Time Offer
Audit-informed Optimizations for 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.
Use the audit findings to prioritize improvements during development. Scores depend on measured conditions; rankings and fixed scores are not guaranteed.