This website audit report analyzes http://bestsextoys.online across 12 critical dimensions with actionable recommendations.
http://bestsextoys.online
86Goodout of 100
Website Audit Report
Best Sex Toys Online — Buy Premium Adult Toys | Best Sex
August 11, 2026 · 17:41 (America/New_York) 350ms response HTTPS Secure301 Redirect
Executive Summary
http://bestsextoys.online scores 86/100 (B). Strong areas include SEO, Security, AI Readiness. The site has 3502 words, 69 images, and 14 schema blocks. Data confidence: 100%. Sustainability score: 60/100. Focus on the top recommendations below to improve your score.
350ms
Response Time
3,502
Word Count
69
Images
189
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
301 Permanentredirect detected — your site correctly forces secure connections.
Loading preview…
Score History
Current scan20 scans recorded· Tap or hover a point for score & time↑ 1 pts since first scan
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Cloudflare Email Protection detected (1 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
2[SEO] Primary keyword missing from first paragraph
3[SEO] Low readability score (15 Flesch) — content is hard to read
4[Performance] No responsive image srcset found
5[Performance] Only 2/69 images have width/height attributes
6[Performance] Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
7[Security] No cookie consent banner detected
8[AI Readiness] No breadcrumb navigation
9[AI Readiness] No content freshness signals (dateModified, datePublished, <time> elements)
10[AIO] Low semantic markup ratio — 845 divs vs 43 semantic elements
Top Recommendations
1[Impact: Medium | Effort: Low] Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
3[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
4[Impact: Medium | Effort: Medium] Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
5[Impact: Medium | Effort: Medium] SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
6[Impact: Medium | Effort: Medium] Use srcset and sizes attributes on images to serve appropriately sized images per device
7[Impact: Medium | Effort: Medium] Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
8[Impact: High | Effort: Medium] Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
9[Impact: Medium | Effort: Medium] Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
10[Impact: Medium | Effort: Medium] Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
11[Impact: Medium | Effort: Medium] Implement a cookie consent banner for GDPR/ePrivacy compliance
12[Impact: Medium | Effort: High] Strengthen CSP: consider nonce-based policies when feasible
Detailed Category Analysis
Key Findings
1Title tag is 56 characters — within optimal 50–60 range (Google 2025-2026)
2Meta description is 154 characters — within optimal 140–160 range (2025-2026)
3Single H1 tag present: "Best Sex ToysOnline"
4Clean heading hierarchy with no skipped levels
5Canonical URL is set and matches the page URL
6Complete Open Graph tags (title, description, image, url, type)
7Complete Twitter Card tags present
8HTML lang attribute set to "en"
9Favicon present
10174 internal links help establish site architecture
1115 external links provide reference signals
12189 total links — within recommended range
13URL length (27 chars) is within optimal range
14All external links have proper rel attributes (nofollow/noopener)
15No redirect chain — direct URL resolution
16Healthy internal link ratio: 92% of links are internal
17Good anchor text diversity: 87% unique anchor texts
18Optimal dofollow outbound links: 2 (ideal 2–5 per page for link authority signals)
19Primary keyword "best sex toys" found in H1 — strong on-page signal
20Primary keyword present in URL — good URL optimization
21Strong E-E-A-T signals detected (6 indicators)
22og:locale set to "en_US"
23OG image uses WebP format — optimal for quality/size balance
24OG image dimensions ≥1200×630px — optimal for all platforms
25article:published_time present — content freshness signal for social platforms
26article:modified_time present — update recency signal
27Twitter card uses summary_large_image — maximum visual impact
28Internal link density (49.7/1k words) — above average but acceptable for navigation-heavy pages
29Optimal keyword density: "best sex toys" at 2.2% (26 occurrences)
30Low passive voice ratio (6%) — clear, active writing style
31Table of Contents detected — improves dwell time and jump-link navigation
32Strong entity salience: Best Sex Toys Online, Body Silicone Sex Doll Torso, Torso Sex Doll (score: 82)
33Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
34Social share buttons detected: ShareThis, Facebook Share
35OG sharing completeness: 100% — all tags present for optimal social previews
Issues Found
1Cloudflare Email Protection detected (1 obfuscated links) — these appear as /cdn-cgi/l/email-protection and return 404 to crawlers
2Primary keyword missing from first paragraph
3Low readability score (15 Flesch) — content is hard to read
Recommendations to Reach 100%
1Use JavaScript-rendered email addresses (client-side assembly) instead of plain mailto: links to prevent Cloudflare from obfuscating them. Alternative: disable Email Address Obfuscation in Cloudflare dashboard [Impact: Medium | Effort: Low]
2Include your primary keyword naturally in the first paragraph to establish topical relevance early
3Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
4Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
5SEO: 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: 350ms
2HTML is 723KB — typical for SSR framework with rich content
32 framework-managed script(s) — optimized by build pipeline
467/69 images use lazy loading
5Modern image formats (WebP/AVIF) detected
6Preconnect hints for: https://www.googletagmanager.com, https://www.google-analytics.com, https://apps.abacus.ai
7Preloaded resources: image, image, script
8font-display property detected — reduces invisible text during font loading
920 async and 0 deferred scripts
10Cache-Control header with max-age is set
1137 inline scripts (framework hydration/data — standard for SSR apps)
12Lean CSS payload (~61KB)
13JavaScript payload (~1469KB) is acceptable for framework app
14HTTP/1.1 detected — protocol upgrade managed at CDN/infrastructure level
15CDN detected: Cloudflare — reduces latency for global users
16Gzip compression enabled
1713 resource hints (preconnect/prefetch/preload) optimize loading
185 framework hydration script(s) — standard for SSR apps
19Estimated LCP: ~1110ms — within Google's "good" threshold (<2.5s)
20Estimated INP: ~200ms — within Google's "good" threshold (<200ms)
21Variable fonts detected — reduces total font file downloads
22Good analytics setup: GA4 + event tracking
Issues Found
1No responsive image srcset found
2Only 2/69 images have width/height attributes
3Moderate estimated CLS: 0.15 — above 0.1 "good" threshold
Recommendations to Reach 100%
1Use srcset and sizes attributes on images to serve appropriately sized images per device
2Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
3Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
4Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
5Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1, maximum-scale=5, viewport-fit=cover, user-s
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
767 images with lazy loading benefit mobile data users
8Mobile-responsive hamburger menu detected
9Web app manifest includes 9 icon sizes — good coverage
103 internationalization signals detected (hreflang, lang, dir, locale meta)
Issues Found
1No responsive image srcset — mobile users may download oversized images
2Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
3Manifest present but no service worker — PWA install prompt will not fire
4Estimated page weight ~5943KB — heavy for mobile data plans
Recommendations to Reach 100%
1Consider implementing a service worker for offline support and faster repeat visits
2Implement srcset to serve smaller images on mobile devices, saving bandwidth
3Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
4Add a service worker to complete PWA install requirements (manifest + SW + HTTPS)
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Add :active / touch-action CSS for tactile feedback on mobile interactions
7Reduce page weight below 3MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 301 redirect detected — properly forces secure connections
3HSTS header present — enforces HTTPS
4Content Security Policy header present
5X-Content-Type-Options: nosniff is set
6X-Frame-Options header prevents clickjacking
7Referrer-Policy set to: strict-origin-when-cross-origin
8Permissions-Policy header restricts browser features
9Cross-Origin-Opener-Policy set
10Cross-Origin-Resource-Policy set
11Cross-Origin-Embedder-Policy set
12Server via CDN proxy (cloudflare) — header added by infrastructure, not application
13All external links have security-safe rel attributes
14HSTS with preload and adequate max-age — eligible for browser preload list
15No cookie security issues detected
16Privacy policy link detected
17CSP strictness score 40/100 — adequate for modern framework apps that require inline styles/scripts
18CSP uses 2 unsafe-inline directive(s) — standard requirement for modern SSR frameworks
19Permissions-Policy restricts 10 browser features (camera, microphone, geolocation, payment)
20Rate limiting recommended for form endpoints
21No server software/technology fingerprints exposed in headers or markup
22security.txt present and valid (/.well-known/security.txt) — provides a channel for vulnerability disclosure
23No stack traces or sensitive error details exposed in responses
24No raw email addresses exposed in page source
25No obvious secret/API-key patterns exposed in page source
2622 script resource(s) catalogued for software-composition review
27No common sensitive paths (.git, .env, server-status, …) were publicly accessible
28Cross-origin isolation enabled (COOP + COEP) — hardened against Spectre-style side-channel and cross-origin leaks
29Password-reset flow detected — ensure reset tokens are single-use, time-limited and delivered out-of-band
30A03: a published SBOM (CycloneDX/SPDX) was found — excellent supply-chain transparency.
31A09: a client-side error/monitoring integration (e.g. Sentry/Datadog) is present — supports security logging & alerting.
Issues Found
1No cookie consent banner detected
Recommendations to Reach 100%
1Implement a cookie consent banner for GDPR/ePrivacy compliance
2Strengthen CSP: consider nonce-based policies when feasible
3When feasible, migrate to nonce-based CSP for inline scripts/styles
4Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
5A05 Injection: 1 raw-HTML binding sink(s) detected (dangerouslySetInnerHTML / v-html / [innerHTML]). Sanitize with a trusted library (DOMPurify) and adopt Trusted Types to close DOM-XSS vectors.
6A06 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.
7A07 Authentication Failures: no phishing-resistant factor detected (WebAuthn/passkeys/TOTP MFA). Offer passkeys or TOTP and enforce ASVS L2 credential and session controls.
Key Findings
1Language declared: en
2Skip navigation link present
3All key landmarks present (main, nav, footer)
4All 69 images have alt attributes
5All 2 forms have proper labels
6All 58 buttons have accessible labels
7Rich ARIA implementation: 105 elements with ARIA attributes
8Focus styles detected for keyboard navigation
Issues Found
1Potential contrast issues: white text on very light background detected
26 HTML validity issues detected — affects assistive technology parsing
367 images missing explicit dimensions — causes layout shifts for screen reader users
Recommendations to Reach 100%
1Ensure all text meets WCAG AA contrast ratio of at least 4.5:1
2Fix HTML nesting errors and deprecated elements. Validate at validator.w3.org for WCAG compliance
3Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
Key Findings
1Rich structured data: 14 schema blocks (Organization, WebSite, OnlineStore, Product, LocalBusiness)
2Hreflang tags: en, x-default
3Strong semantic markup: header, nav, main, section, details, summary, aside, footer
4Complete social metadata (OG + Twitter Card)
5FAQ/Q&A content patterns detected — highly valuable for AI citation
6Sitemap reference detected
720 strong entity mentions (bold/emphasized text)
8Social presence signals: facebook, instagram, tiktok, twitter
94 call-to-action elements detected
10No AI crawlers blocked via meta tags — content accessible to AI search engines
11robots.txt file found
12AI crawlers explicitly allowed in robots.txt: GPTBot, ChatGPT-User, CCBot, anthropic-ai, Google-Extended, PerplexityBot
13robots.txt references 2 sitemap(s) — aids AI crawler discoverability
14llms.txt detected (score: 85/100, quality: comprehensive)
15llms-full.txt companion file detected (3KB)
16llms.txt has proper title and description block
17llms.txt has 6 well-organized sections
18llms.txt references 15 URLs for AI navigation
19llms.txt includes service/product catalog
20llms.txt uses proper Markdown formatting for machine readability
21llms.txt links to detailed documentation (llms-full.txt)
22llms.txt referenced in HTML for discoverability
23llms.txt uses canonical domain in URLs
24High RAG-friendliness (95/100): 0 headings with IDs, 13 section anchors
25Additional AI crawlers allowed: PerplexityBot
26Content provenance signals detected (citations with sources, attributed claims)
27Good HTML-to-text ratio (57%) — AI crawlers can extract content efficiently
28JS content ratio 51% — expected for SSR framework apps that serve pre-rendered HTML with hydration scripts
Issues Found
1No breadcrumb navigation
2No content freshness signals (dateModified, datePublished, <time> elements)
Recommendations to Reach 100%
1Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
2Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Key Findings
1Comprehensive content (3502 words) — strong for AI model training
2Rich Q&A content (15 FAQ/accordion elements)
3Strong entity emphasis: 20 key terms highlighted
4Structured content: 4 lists, 1 tables — easily parsed by AI
5E-E-A-T schema signals present (2 types)
6Good paragraph length for readability and AI parsing
7Speakable schema detected — content optimized for voice assistants
810 external citations — strong reference density for AI model training
9124 statistics/data points — excellent for AI knowledge extraction
101 call-to-action element(s) detected
11Good form usability score: 100/100
12Trust signals present: Reviews/Testimonials, Trust Badges, Guarantee
13Social proof elements detected — builds credibility and conversion confidence
14Clear value proposition detected in heading elements
Issues Found
1Low semantic markup ratio — 845 divs vs 43 semantic elements
2No author or expertise signals
3No CTA above the fold
Recommendations to Reach 100%
1Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
2Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
3Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
4Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
5Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
Key Findings
1Direct question-answer patterns found — good for Google SGE and AI citations
21 comparison/data table(s) — highly extractable by AI
34 lists detected
42 ordered lists provide step-by-step structure
5How-to instructional patterns detected — valued by AI answer engines
61 definition list(s) — excellent for AI glossary extraction
7Comprehensive content depth (3502 words) supports AI citation
820 emphasized terms suggest unique, quotable insights
914 schema blocks help AI engines understand content context
10comprehensive content length — good for authority signals
11Hreflang includes self-referencing tag
12x-default hreflang fallback present
13124 data points/statistics — content has original research signals
Recommendations to Reach 100%
1Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
2Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Key Findings
1FAQPage schema markup present — eligible for rich FAQ results
2HowTo schema markup present — eligible for how-to rich results
3Question-answer heading patterns support featured snippet capture
4Speakable schema supports voice search optimization
5Short paragraphs are well-suited for answer extraction
64 lists provide scannable answers for People Also Ask
740 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
Issues Found
1No breadcrumb navigation
2No direct answer patterns ("X is defined as...", "X refers to...")
Recommendations to Reach 100%
1Add breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
2Consider adding video content with VideoObject schema for multimedia search results
3Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Key Findings
1NAP information detected: phone: 6643667
2Phone number(s) visible: 6643667, 13971731025
3LocalBusiness schema: OnlineStore, LocalBusiness
4Address microdata markup detected
5Geo meta tags present for location targeting
6Business hours/opening hours detected
7Review schema with 1247 reviews (4.8 avg rating)
8Multiple location signals detected — consider individual location pages
9Service area defined in schema
Issues Found
1No Google Maps embed
Recommendations to Reach 100%
1Consider displaying a business email for direct contact signals
2Add an embedded Google Map to your contact or about page for local search signals
3Local 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.
4Local 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
114 JSON-LD block(s) with types: Organization, WebSite, OnlineStore, Product, LocalBusiness, Organization, Service, FAQPage, WebPage, Review
2Some microdata attributes detected alongside JSON-LD — common for address/local business markup in modern frameworks
3Comprehensive schema implementation
4Strong top-tier schema coverage: LocalBusiness, Organization, Product, FAQPage, BreadcrumbList, WebSite
5Good secondary schema coverage: HowTo, Service, Review
6BreadcrumbList schema → breadcrumb rich results
7FAQPage schema → expandable FAQ rich results
8Product schema → rich product results with pricing
9Service schema describes your offerings
10Review/Rating schema → star ratings in search results
11HowTo schema → step-by-step rich results
12No schema validity issues detected
13Rich schema diversity: 11 distinct types with properties
14Entity linking via sameAs: 10 external profiles linked — strengthens Knowledge Graph
15Average schema property completeness: 82% — well-implemented
16Rich results eligible: FAQ, HowTo, Breadcrumbs, Product with Reviews, Review
17Schema nesting depth: 2 levels — rich entity relationships
18SearchAction schema present — eligible for sitelinks search box in Google
Recommendations to Reach 100%
1When feasible, consolidate all structured data into JSON-LD format
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)
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Moderate cognitive load — acceptable for interactive modern web apps with rich UI patterns
9Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
10Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
112 ARIA live regions for dynamic content announcements
12Reduced motion enforced: animations disabled when prefers-reduced-motion is set
Issues Found
1No error suggestion mechanisms detected in forms
2Low semantic-to-div ratio — 845 divs vs 43 semantic elements
31 potential color contrast issue(s)
4No form error identification detected
Recommendations to Reach 100%
1Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
2Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
3Audit color contrast ratios — ensure at least 4.5:1 for normal text and 3:1 for large text (WCAG 1.4.3)
4Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
5WCAG 2.2 (1.4.13 Content on Hover/Focus): 79 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.