This website audit report analyzes http://pornhub.com across 12 critical dimensions with actionable recommendations.
http://pornhub.com
40Poorout of 100
Website Audit Report
Free Porn Videos & Sex Movies - Porno, XXX, Porn Tube | Pornhub
August 20, 2026 at 1:42 PM EDT 948ms response HTTPS Secure301 Redirect
Executive Summary
http://pornhub.com scores 40/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 2537 words, 140 images, and 2 schema blocks. Data confidence: 95%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
948ms
Response Time
2,537
Word Count
140
Images
501
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan2 scans recorded· Tap or hover a point for score & time↑ 0 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is too long (63 chars — may be truncated in SERPs)
2[SEO] Heading hierarchy gaps: h3 → h5 (skips h4)
3[SEO] No Open Graph tags found
4[SEO] No Twitter Card tags found
5[SEO] 7 empty/unlabeled links found
6[SEO] Excessive links on page (501) — search engines may devalue link equity
7[SEO] 21 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8[SEO] High dofollow external link count (21) — excessive link equity leakage
9[SEO] Primary keyword "free porn videos" not found in H1
10[SEO] Primary keyword missing from first paragraph
Top Recommendations
1[Impact: High | Effort: Low] Shorten your title to under 60 characters to prevent truncation in search results
2[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
4[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
5[Impact: Medium | Effort: Medium] Add descriptive anchor text to all links for better SEO and accessibility
6[Impact: Medium | Effort: Medium] Reduce total links to under 200 per page. Use pagination, nofollow on low-value links, and consolidate navigation
7[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
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
1Meta description is 157 characters — within optimal 140–160 range (2025-2026)
2Single H1 tag present: "Hot Porn Videos"
3Canonical URL is set and matches the page URL
4HTML lang attribute set to "en"
5Favicon present
6464 internal links help establish site architecture
730 external links provide reference signals
8Content length of 2537 words is adequate
9URL length (24 chars) is within optimal range
10No redirect chain — direct URL resolution
11Healthy internal link ratio: 93% of links are internal
12Good anchor text diversity: 88% unique anchor texts
13Primary keyword not in URL — acceptable for homepage/root URLs
14Low passive voice ratio (5%) — clear, active writing style
15Strong entity salience: Scott Stark, No Ads, Exclusive Content (score: 50)
16Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
17Social share buttons detected: ShareThis
Issues Found
1Title tag is too long (63 chars — may be truncated in SERPs)
2Heading hierarchy gaps: h3 → h5 (skips h4)
3No Open Graph tags found
4No Twitter Card tags found
57 empty/unlabeled links found
6Excessive links on page (501) — search engines may devalue link equity
721 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8High dofollow external link count (21) — excessive link equity leakage
9Primary keyword "free porn videos" not found in H1
10Primary keyword missing from first paragraph
11Weak E-E-A-T signals (2 indicators)
12Low readability score (37 Flesch) — content is hard to read
13Very high internal link density (182.9/1k words) — may appear spammy
14Low keyword density (0.1%) for "free porn videos"
15Long content without Table of Contents
16Low OG sharing completeness (0%) — social previews will be poor
Recommendations to Reach 100%
1Shorten your title to under 60 characters to prevent truncation in search results
2Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
3Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
4Add Twitter Card meta tags for better social media previews
5Add descriptive anchor text to all links for better SEO and accessibility
6Reduce total links to under 200 per page. Use pagination, nofollow on low-value links, and consolidate navigation
7Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
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 an About page to establish authoritativeness and brand trust (E-E-A-T)
14Link to a Contact page — essential trust signal for E-E-A-T and local SEO
15Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
16Reduce internal link density — excessive linking dilutes individual link value
17Increase primary keyword usage to 0.5–2.5% density — include it naturally in headings, paragraphs, and image alt text
18Add a Table of Contents with anchor links for articles over 1500 words — improves UX, dwell time, and enables jump-link rich results
19Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
20Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
21SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Acceptable response time: 948ms
297/140 images use lazy loading
3Preloaded resources: script, style
43 async and 2 deferred scripts
5Brotli compression enabled — best-in-class compression
Issues Found
1Very large HTML: 1148KB
213 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
4No responsive image srcset found
5No font-display property found
6No effective Cache-Control header
760 inline scripts
8Moderate CSS payload (~395KB)
9Heavy JavaScript payload (~1296KB across 15 files)
10501 links increase DOM size and parsing time
11HTTP/1.1 detected — no multiplexing
12No CDN detected
1315 third-party scripts from 3 domains — significant performance impact
1413 render-blocking CSS files — delays first paint
15Estimated CSS bundle ~525KB — above optimal
16Potential long-task scripts: Inline script (~15KB), Inline script (~42KB), Inline script (~202KB)
17Estimated LCP: ~3688ms — needs improvement (goal: <2.5s)
18Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
19Estimated INP: ~295ms — needs improvement (goal: <200ms)
20Basic analytics only — missing event tracking or tag management
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
3Convert all non-critical scripts to async/defer to eliminate render-blocking resources
4Convert images to WebP or AVIF format for 30–50% file size reduction
5Use srcset and sizes attributes on images to serve appropriately sized images per device
6Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
7Add font-display: swap to web font declarations to show fallback text while fonts load
8Set Cache-Control headers with appropriate max-age to leverage browser caching
9Move inline scripts to external files with defer attributes
10Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
11Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
12Reduce links per page to improve DOM parsing performance and reduce memory usage
13Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
14Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
15Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
16Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
17Reduce CSS bundle size with PurgeCSS/tree-shaking. Aim for <200KB total CSS
18Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
19Optimize Largest Contentful Paint: preload hero image, reduce render-blocking resources, use CDN for static assets
20Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
21Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
22Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
23Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
24Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
25Performance: only 0/140 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.0
2HTML5 doctype declared
3Character encoding declared
4Service worker detected — offline capability possible
597 images with lazy loading benefit mobile data users
6Mobile-responsive hamburger menu detected
7Orientation handling declared in manifest or meta
83 internationalization signals detected (hreflang, lang, dir, locale meta)
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
5Fixed-width elements detected (>800px) — may cause horizontal scrolling on mobile
6Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
7Estimated page weight ~10119KB — 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
4Implement srcset to serve smaller images on mobile devices, saving bandwidth
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 env(safe-area-inset-*) CSS for proper display on notched/island devices
8Add :active / touch-action CSS for tactile feedback on mobile interactions
9Reduce page weight below 3MB: 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
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4X-Frame-Options header prevents clickjacking
5HSTS with preload and adequate max-age — eligible for browser preload list
6Privacy policy link detected
7Cookie consent mechanism detected
8jQuery 3.6.0 — current version
9Rate limiting recommended for form endpoints
10No stack traces or sensitive error details exposed in responses
11No obvious secret/API-key patterns exposed in page source
12Client-side library inventory (SBOM): jQuery 3.6.0
1315 script resource(s) catalogued for software-composition review
14No common sensitive paths (.git, .env, server-status, …) were publicly accessible
15Login form detected — ensure it is protected by rate limiting, HTTPS and anti-automation controls
16Password-reset flow detected — ensure reset tokens are single-use, time-limited and delivered out-of-band
17A09: 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-Content-Type-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: openresty
621 external links missing rel="noopener noreferrer" — security risk
7Cookie security issues: missing Secure flag; missing SameSite attribute
8No Subresource Integrity (SRI) on external scripts
9Server technology disclosed via response headers/markup: Server: openresty
10security.txt file is missing — no standardized channel for reporting vulnerabilities
112 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
12A password field does not disable autocomplete on a shared/sensitive context — may persist credentials on shared devices
13Dangerous client-side sink(s) detected in inline scripts: innerHTML assignment, new Function() — potential DOM-based XSS vectors
1447 inline event handlers (onclick=, onload=, …) — inline handlers require CSP unsafe-inline and widen the XSS surface
154 javascript: URL(s) found — a legacy XSS/injection vector
16robots.txt discloses sensitive-looking path(s): /albums/private*, */videos/private*, /video/privates* — 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-Content-Type-Options: nosniff to prevent MIME type sniffing
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
7Remove or obfuscate the Server header to avoid exposing your technology stack
8Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
9Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
10Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
11Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
12Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
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]
15Consider autocomplete="new-password"/"off" on high-sensitivity password fields where appropriate (informational) [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]
17Move inline event handlers to external scripts with addEventListener so a strict CSP can forbid inline execution [Impact: Low | Effort: Medium]
18Replace javascript: URLs with proper event handlers and href targets [Impact: Low | Effort: Low]
19Avoid listing admin/private paths in robots.txt; protect them with authentication instead of relying on obscurity [Impact: Low | Effort: Low]
20Protect the detected login form with rate limiting / lockout and multi-factor authentication to resist credential-stuffing [Impact: High | Effort: Medium]
21A03 Software Supply Chain: only 0% of 15 cross-origin scripts use Subresource Integrity. Pin every third-party script with integrity+crossorigin and adopt SLSA provenance / a published SBOM for build integrity.
22A07 Authentication Failures: username/identifier field lacks an explicit autocomplete token. Set autocomplete="username" (and "current-password") so password managers and passkeys work reliably.
23A07 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.
24A08 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 140 images have alt attributes
3Rich ARIA implementation: 36 elements with ARIA attributes
4Focus styles detected for keyboard navigation
5CAPTCHA with accessible alternative detected
Issues Found
1No skip navigation link
2Missing landmarks: main, nav, footer
31 form(s) missing proper labels
44 button(s) missing accessible labels
5Heading hierarchy has gaps — confusing for screen readers
64 minor HTML validity issue(s)
74 video(s) missing captions/subtitles
88 button(s) with no accessible label
92 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
4Add text content or aria-label to all buttons
5Review and fix HTML structure issues for better accessibility and cross-browser compatibility
6Add <track kind="captions"> or <track kind="subtitles"> to all video elements (WCAG 1.2.2)
7Add text content, aria-label, or title to all buttons — icon-only buttons need aria-label (WCAG 4.1.2)
8Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
9Accessibility: 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: x-default, en, de, de-DE, fr, it, pt, es, ru, ru-RU, ru-BY, pl, ja, nl, cs, zh
3Some semantic elements: header, aside, section
4FAQ/Q&A content patterns detected — highly valuable for AI citation
5Sitemap reference detected
620 strong entity mentions (bold/emphasized text)
7Social presence signals: twitter
812 call-to-action elements detected
9No AI crawlers blocked via meta tags — content accessible to AI search engines
10robots.txt file found
11robots.txt references 1 sitemap(s) — aids AI crawler discoverability
12High RAG-friendliness (100/100): 3 headings with IDs, 50 section anchors
13Content provenance signals detected (citations with sources, attributed claims)
14Good HTML-to-text ratio (29%) — AI crawlers can extract content efficiently
Issues Found
1Incomplete social metadata
2No breadcrumb navigation
3No llms.txt file found — AI models cannot find structured guidance for your site
4No 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 /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
5Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
6Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
7Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Comprehensive content (2537 words) — strong for AI model training
21 FAQ/Q&A elements detected
3Strong entity emphasis: 20 key terms highlighted
4Structured content: 36 lists, 0 tables — easily parsed by AI
530 external citations — strong reference density for AI model training
65 statistics/data points — excellent for AI knowledge extraction
7Strong CRO: 6 clear call-to-action elements detected
8Above-the-fold CTA detected — captures immediate visitor attention
9Trust signals present: Reviews/Testimonials, Trust Badges, HTTPS Security
10Social proof elements detected — builds credibility and conversion confidence
11Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 1111 divs vs 9 semantic elements
2Weak E-E-A-T schema signals
3Paragraphs are too long for optimal AI consumption
4No author or expertise signals
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 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
Key Findings
136 lists provide scannable, AI-friendly content
2How-to instructional patterns detected — valued by AI answer engines
3Comprehensive content depth (2537 words) supports AI citation
420 emphasized terms suggest unique, quotable insights
52 schema blocks help AI engines understand content context
6Hreflang includes self-referencing tag
7x-default hreflang fallback present
85 data points/statistics — content has original research signals
93 original data elements (charts, figures, data tables)
Issues Found
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3paragraphs may be too long for featured snippets
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
3Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
4Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
5GEO: only 0/13 sub-headings are question-phrased. Convert key sections into natural-language questions so generative engines can extract and cite direct answers.
6GEO: 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
136 lists provide scannable answers for People Also Ask
2Video content detected — supports multimedia answer results
36 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1FAQ content exists but lacks FAQPage schema
2How-to content exists but lacks HowTo schema
3Content not optimized for featured snippets
4No Speakable schema for voice search
5Paragraphs too long for answer engine extraction
6No breadcrumb navigation
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
2Add HowTo schema to your instructional content for rich result eligibility
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
7Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
8Keep paragraphs under 30 words for voice search — voice assistants read concise, conversational content
9AEO: 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: 1000001, email: [email protected]
2Phone number(s) visible: 1000001, 2026081904
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
6Local 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.
7Local 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
12 JSON-LD block(s) with types: WebSite, Organization
2Moderate schema coverage
3Some top-tier schemas: Organization, WebSite
4Entity linking via sameAs: 3 external profiles linked — strengthens Knowledge Graph
5SearchAction schema present — eligible for sitelinks search box in Google
Issues Found
1Microdata or RDFa detected alongside JSON-LD
2WebSite has very few properties (2)
3Schema property completeness averaging 54%
4No rich results eligibility detected
Recommendations to Reach 100%
1Migrate all structured data to JSON-LD format — it's easier to maintain, debug, and is Google's preferred format
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: FAQPage, HowTo
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 properties to schema types — aim for at least 5 meaningful properties per type
9Fill in missing recommended properties for each schema type
10Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
11Schema.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.
12Schema.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
1Links are visually distinguishable (underline or decoration detected)
2Form error/validation feedback detected
34 media element(s) without autoplay
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7Form error identification mechanisms present (WCAG 3.3.1)
8Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Issues Found
1No prefers-reduced-motion support
2No high contrast mode support
3Low semantic-to-div ratio — 1111 divs vs 9 semantic elements
4Invalid ARIA roles: submenus-items-holder
5Multiple 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
3Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
4Use only valid WAI-ARIA roles — invalid roles are ignored by assistive technology and may confuse screen readers (WCAG 4.1.2)
5Ensure 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)
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): 188 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.