# BeaverCheck Audit Report — https://fetish4all.com

**Date:** August 15, 2026  
**URL:** https://fetish4all.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/2994ccf4-ce99-4a59-9b3e-15b8b19797fa

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
3. **[CRITICAL]** Page weighs 20.2 MB (18.2 MB transferred) — Performance > Page Weight Budget
4. **[CRITICAL]** 2 link(s) with no accessible text — Accessibility > Link & Button Quality
5. **[CRITICAL]** 3 control(s) without accessible label — Accessibility > Form Accessibility

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 56 |
| Accessibility | 81 |
| Best Practices | 92 |
| SEO | 100 |

---

## Security

### Security Headers (C — 60/100)

*5 of 10 headers properly configured*

- **[WARNING]** HSTS is missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP.
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 0/100)

*No enforcing CSP policy found*

- **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 7 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 64 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 3 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 100/100)

*No cookies set — no cookie security risks*

- **[PASS]** No cookies set — no cookie security risks

### Cookie Hygiene (A+ — 100/100)

*No cookies set -- cookie-hygiene check is N/A*

- **[PASS]** No cookies set

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

### security.txt (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

### Cross-Origin Tab Safety (D — 60/100)

*5 of 6 new-tab link(s) missing rel=noopener*

- **[WARNING]** 5 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

### CSP Inline-Style Readiness (B — 90/100)

*10 inline style attribute(s) detected*

- **[INFO]** 10 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 10 inline style(s) is low. Affected element types include: a, div, iframe, aside. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

*No CSP header -- Trusted Types check is N/A*

- **[PASS]** No CSP header found -- Trusted Types check is N/A

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/29 third-party resources)*

- **[WARNING]** SRI adoption: 0/29 third-party resources protected (0%) — Of 29 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://scripts.clarity.ms/0.8.69/clarity.js
  - https://www.clarity.ms/tag/pmho67t0z3?ref=gtm2
  - https://www.clarity.ms/tag/pmho67t0z3
  - https://roamer.b8europe.eu/piwik.js
  - https://www.googletagmanager.com/gtm.js?id=GTM-59MRSJS

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (A — 85/100)

*90% high-risk feature coverage (9/10)*

- **[PASS]** Permissions-Policy covers 9/10 high-risk features (90%) — The Permissions-Policy header explicitly declares policies for 9/10 high-risk features.

Covered: camera, microphone, geolocation, payment, usb, midi, accelerometer, gyroscope, magnetometer

Not declared (default-allow): serial

The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

### Referrer-Policy Strictness (D — 50/100)

*Referrer-Policy is `no-referrer-when-downgrade` (leaky -- legacy default that sends full URL cross-origin on HTTPS-to-HTTPS)*

- **[WARNING]** Referrer-Policy: `no-referrer-when-downgrade` -- leaky -- legacy default that sends full URL cross-origin on HTTPS-to-HTTPS — The legacy browser default (Chrome <85, Firefox <87). Sends the full URL (path + query) Referer on cross-origin requests as long as the protocol doesn't downgrade. This means session IDs, tracking tokens, search queries, etc. embedded in URLs leak to every third-party HTTPS origin the page links to or embeds. Switch to `strict-origin-when-cross-origin`.

### Source Map Exposure (A+ — 100/100)

*Source-map probe didn't run on this scan*

- **[PASS]** Source-map probe didn't run on this scan

### HTML Version Disclosure (D — 60/100)

*2 software version(s) disclosed in HTML*

- **[WARNING]** 2 software version(s) disclosed in HTML: Site Kit by Google 1.185.0, WordPress 7.0.4 — Each disclosed version enables direct CVE lookup -- an attacker who knows you run WordPress 6.4.2 (or whatever specific version) can search the CVE database for known exploits and target accordingly. Remove via your CMS config: WordPress (`remove_action('wp_head', 'wp_generator')`); Drupal (System / Reports / Status report -> Hide generator); Joomla (Global Configuration -> Hide generator); Hugo/Jekyll (delete or override the {{ .Site.Generator }} template hook). For HTML comments, audit your template files directly.

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (B — 80/100)

*3 auth-security finding(s) on the login page*

- **[PASS]** Login page detected — The page contains a `type=password` input and at least one identifier field (username / email). Auth-security findings below evaluate the page's hardening posture.
- **[WARNING]** Login form does not contain a recognizable CSRF token — Standard frameworks emit CSRF tokens as a hidden input named `_csrf`, `csrf_token`, `csrfmiddlewaretoken` (Django), `authenticity_token` (Rails), or `__RequestVerificationToken` (ASP.NET). None of those were found. Possibilities: (1) the form posts to an API that uses a custom header or SameSite cookie reliance for CSRF -- legitimate but not visible from this scan, (2) the form is genuinely missing CSRF protection, which would let an attacker submit logins from another origin via a hidden POST. Verify the auth flow has SOME CSRF defense.
- **[INFO]** No password-reset link found on the login page — Login pages should link to a password-reset flow (typically /forgot, /reset, or a 'Forgot password?' link). Absence usually means the reset flow lives elsewhere on the site (separately reachable), but if it's truly missing, users locked out of accounts have no self-service recovery path.

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 29 external resources have SRI*

- **[WARNING]** External script from scripts.clarity.ms lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.clarity.ms lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.clarity.ms lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from roamer.b8europe.eu lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.fetish4all.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from eyov5sd2xs2.exactdn.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from edwmpt.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (F — 29/100)

*DMARC: none, SPF: ~all*

- **[WARNING]** DMARC policy is none — monitoring only — This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject after monitoring DMARC reports.
- **[INFO]** DMARC configured without rua= aggregate reporting — Without rua=, you have no visibility into spoof attempts or auth failures from your own legitimate senders. Add rua=mailto:dmarc@<your-domain> (or a managed inbox at a reporting service).
- **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (C — 60/100)

*1 directives, 4 missing*

- **[INFO]** geolocation=(); midi=();notifications=();push=();sync-xhr=();accelerometer=(); gyroscope=(); magnetometer=(); payment=(); camera=(); microphone=();usb=(); xr=();speaker=(self);vibrate=();fullscreen=(self);
- **[INFO]** camera not restricted — Consider adding camera=() to block camera access from embedded content.
- **[INFO]** microphone not restricted — Consider adding microphone=() to block microphone access from embedded content.
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (F — 0/100)

*18.2 MB transferred, 157 requests*

- **[CRITICAL]** Page weighs 20.2 MB (18.2 MB transferred)
- **[WARNING]** Images are 16.6 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 966 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 157 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 3.8 g CO2 per page load

### Third-Party Impact (D — 50/100)

*100% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 100% of page weight (18.2 MiB of 18.2 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (B — 75/100)

*89 images, 0 KB saveable*

- **[PASS]** All images are well-optimized

### JS Execution Cost (D — 40/100)

*3224ms total JS execution*

- **[WARNING]** Unattributable: 856ms CPU time
- **[WARNING]** https://fetish4all.com/: 647ms CPU time
- **[WARNING]** https://eyov5sd2xs2.exactdn.com/wp-content/plugins...: 404ms CPU time
- **[WARNING]** https://scripts.clarity.ms/0.8.69/clarity.js: 296ms CPU time
- **[INFO]** https://eyov5sd2xs2.exactdn.com/wp-includes/js/jqu...: 190ms CPU time
- **[WARNING]** Third-party scripts: 1721ms (53% of total)

### Font Loading (A+ — 100/100)

*5 fonts (159 KB)*

- **[INFO]** 5 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (C — 60/100)

*41 scripts, 246 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=GT-TNP...: 115 KB unused (69%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://cdn.fetish4all.com/wp-content/cache/caos/3...: 66 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtm.js?id=GTM-59M...: 66 KB unused (57%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 246 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A — 90/100)

*11 hints, 0 missing preconnects*

- **[INFO]** 3 dns-prefetch redundant with preconnect on same origin — preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://cdn.fetish4all.com, https://www.googletagmanager.com, https://eyov5sd2xs2.exactdn.com. Remove the redundant dns-prefetch entries.
- **[INFO]** 3 URL(s) appear in multiple hints — The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: //www.googletagmanager.com (preconnect+dns-prefetch), //cdn.fetish4all.com (dns-prefetch+preconnect), //eyov5sd2xs2.exactdn.com (dns-prefetch+preconnect+preconnect).
- **[PASS]** Page uses 11 resource hint(s)

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Compression Algorithm (B — 80/100)

*Main response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=0 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 95/100)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding,User-Agent — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (D — 40/100)

*157 resources · 18.2 MB · 246 KB savings available*

- **[WARNING]** Page weight 18.2 MB exceeds 1 MB target by 17.2 MB
- **[INFO]** ~246 KB of savings available
- **[WARNING]** 154 third-party resources (100% of weight)
- **[INFO]** 2 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (A — 94/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

### CSS Performance Depth (A — 88/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 6 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (F — 40/100)

*200 links checked, 129 healthy, 71 broken*

- **[CRITICAL]** 129 of 200 links are healthy
- **[WARNING]** Broken link: https://www.googletagmanager.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://fetish4all.com/feed/ — Found in <link href>. Returns HTTP 503.
- **[WARNING]** Broken link: https://fetish4all.com/wp-json/ — Found in <link href>. Returns HTTP 503.
- **[WARNING]** Broken link: https://fetish4all.com/xmlrpc.php?rsd — Found in <link href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/legalporno-update/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/go/fetish-webcam/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/go/hankeys-toys/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/tags/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/?filter=latest — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/?filter=popular — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/?filter=most-viewed — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/?filter=longest — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/?filter=random — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/alterotic/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/amateur/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/amateur/amateure-xtreme/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/anal/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/big-tits/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/bisexual/biphoria/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/bisexual/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/busty-dames/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/club-rubber/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/transgenders/devilstgirls/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/dominated-men/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/empress-empire/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/femdomfilms/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/gay/fisting-filthy/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/gay/gay-fisting/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/transgenders/genderx/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/german-porn/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/amateur/girly-cast/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/gay/menover30/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/milf/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/gay/nextdoortaboo/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/puretaboo/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/ropemarks/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/rubbertits/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/category/latex-fetish/the-fetish-c... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/categories — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/go/adulttime/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/the-mask/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/what-a-mean-release-from-chastity-... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/reload-balls-deep-nicole-aria-1on1... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/my-romantic-date-turns-wild-and-ro... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/p-sluts-vol-41-starring-young-slut... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/brazilian-milf-takes-crazy-dog-sty... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/sissy-is-a-cocksucking-slut/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/zoey-foxx-mean-property-manager/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/anuskatzz-gets-anal-fucked-face-fu... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/saving-the-family-business/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/dirty-blowjob-handjob-on-a-corn-fi... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/wet-nylon/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/blonde-melissa-black-dp-ass-filled... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/putting-balls-deep-into-the-big-as... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/playful-poker-chapter-2-horny-bffs... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/lore-hot-always-delighted-to-recei... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/you-are-anal-we-are-double-penetra... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/a-gorgeous-spanish-girl-with-great... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/petite-slut-larinha-small-comes-ba... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/dominique-palermo-takes-big-cock-d... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/prelude-to-something-anna-de-ville... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/daddy-loves-to-fuck-my-ass-and-i-d... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/sidis-horny-threesome-with-our-pho... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/are-you-mine/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/diary-of-a-slut-mysterious-man/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/viviana-rose-randi-cheeks-in-a-tat... — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/page/3/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/page/156/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/actors/ — Found in <a href>. Returns HTTP 503.
- **[CRITICAL]** Broken link: https://fetish4all.com/icwp-wpsf-link-cheese/ — Found in <a href>. Returns HTTP 503.

### Mixed Content (B — 80/100)

*1 HTTP resource(s) loaded on HTTPS page*

- **[CRITICAL]** HTTP link loaded on HTTPS page — Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

### Open Graph (B — 85/100)

*Open Graph tags are partially configured — some improvements recommended.*

- **[WARNING]** Missing og:image — The og:image tag provides a preview image for social sharing.

### Open Graph / Twitter Card Depth (A+ — 100/100)

*OG image dimensions and Twitter card configuration look healthy*

- **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

### Structured Data (A+ — 100/100)

*1 JSON-LD block(s) found — structured data is well configured.*

- **[PASS]** Custom type "AdultEntertainment" — unable to validate specific properties

### Rich Results Eligibility (A+ — 100/100)

*1 JSON-LD block(s) declaring 3 schema type(s)*

- **[PASS]** SiteLinks Search Box markup detected — The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
- **[PASS]** 3 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

AdultEntertainment, CollectionPage, WebSite

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (D — 60/100)

*4 issues found across 57 images*

- **[WARNING]** 31 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[INFO]** 56 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 56 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[INFO]** 8 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://eyov5sd2xs2.exactdn.com/wp-content/uploads/2026/08/green-leather-and-white-leather-gloves-outdoor-blowjob-handjob-touch-my-tits-cum-in-my-face.jpg?strip=all&fit=167,94, https://eyov5sd2xs2.exactdn.com/wp-content/uploads/2026/08/the-lent-rubber-object.jpg?strip=all&fit=167,94, https://eyov5sd2xs2.exactdn.com/wp-content/uploads/2026/08/anna-de-ville-april-bigass-5on2-anal-fisting-balls-deep-dap-deepthroat-rough-sex-tp-big-gapes-monster-buttrose-squirt-cum-in-mouth-swallow-ah312.jpg?strip=all&fit=167,94 (+5 more).

### Autoplay Media (A+ — 100/100)

*No autoplay media on the page*

- **[PASS]** No autoplay media on the page

---

## Infrastructure

### DNS Records (A+ — 95/100)

*1 A records, 56 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[PASS]** Has 1 IPv6 (AAAA) record(s)
- **[PASS]** 3 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 56 ms

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** No CNAME record present

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (B — 75/100)

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 185.104.29.50 does not match any cert SAN: web0102.zxcs.nl — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a06:2ec0:1::102 does not match any cert SAN: web0102.zxcs.nl — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

### Multi-Resolver DNS Speed (A+ — 100/100)

*Mean 26ms across 3 resolvers (spread 26ms)*

- **[PASS]** Quad9: 17ms
- **[PASS]** Google: 20ms
- **[PASS]** Cloudflare: 43ms

### Redirect Chain (A+ — 100/100)

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (30 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a06:2ec0:1::102

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 44 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 44 entries
- **[PASS]** Sitemap index with 44 child sitemaps
- **[PASS]** robots.txt references sitemap

### URL Variants (A+ — 100/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[PASS]** HTTP correctly 301-redirects to HTTPS

### Domain Intelligence (A+ — 100/100)

*fetish4all.com — via Key-Systems GmbH, 7 years, 7 months old*

- **[PASS]** Domain registered until Jan 26, 2027 (5 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: Key-Systems GmbH
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (A — 85/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — A privacy policy page is recommended for transparency and may be legally required.
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (C — 60/100)

*Viewport prevents zooming*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[CRITICAL]** Viewport prevents user zooming — user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y.

### GDPR Article 13 Disclosures (F — 25/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

### Third-Party Trackers (F — 20/100)

*7 trackers detected*

- **[INFO]** 7 third-party trackers detected — Found 4 analytics, 1 advertising, 0 marketing, 1 tag manager, 1 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
- **[WARNING]** 1 session-replay tool(s) detected (Microsoft Clarity) — Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 7 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

### Cookie & Tracker Inventory (A+ — 100/100)

*0 cookies · 7 trackers · 0 pre-consent*

- **[INFO]** 7 third-party tracker(s) detected on page

### Tracking Pixel Inventory (A+ — 100/100)

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No cookies on the page*

- **[PASS]** No cookies set on the page response

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 25/100)

*1 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[PASS]** Terms of Service detected — Found at https://fetish4all.com/legalporno-update/.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (A+ — 100/100)

*©2026 | Fetish4All*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: ©2026 | Fetish4All
- **[PASS]** Copyright holder: | Fetish4All

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (weak confidence) — Indicators suggesting GDPR may be relevant: Text mentions: gdpr. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*2 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 2 third-party services across 2 categories — 2 third-party services detected across 2 categories: Analytics (1), Tag Management (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## Availability

### CDN & Delivery (D — 50/100)

*No CDN detected*

- **[WARNING]** No CDN detected — A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (B — 70/100)

*max-age=0*

- **[PASS]** Cache-Control header is set
- **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (A — 90/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[PASS]** HSTS enabled (base policy)
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 500, /health: 500, /healthz: 500, /ping: 500, /status: 500.

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Landmark Structure (A — 90/100)

*55 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 1 <nav> landmark(s) found
- **[PASS]** Skip navigation link present
- **[WARNING]** Skip link target(s) don't exist on page: #content — The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

### Heading Hierarchy (A+ — 100/100)

*6 headings*

- **[PASS]** Single H1 present

### Heading Text Quality (A+ — 100/100)

*All 6 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (A — 94/100)

*All 58 images OK*

- **[INFO]** 3 image(s) with alt text over 125 characters
- **[PASS]** 55 image(s) with good alt text

### Form Accessibility (C — 55/100)

*3 of 9 controls have issues*

- **[CRITICAL]** 3 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[PASS]** 6 control(s) properly labeled

### Link & Button Quality (C — 68/100)

*2 issue(s) across 138 links and 19 buttons*

- **[CRITICAL]** 2 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 4 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 132 link(s) with descriptive text

### Form Input Types (A+ — 95/100)

*1 input(s) using type=text where a specific type would help*

- **[INFO]** Input "wpst_user_or_email" should use type="email" (currently type="text") — Field name "wpst_user_or_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

### Form Input Quality (B — 82/100)

*2 input-semantic issue(s) across 9 form control(s)*

- **[INFO]** 1 password field(s) missing or with invalid `autocomplete` — Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="wpst_user_pass">.
- **[INFO]** 2 login form field(s) missing `autocomplete=username` (or `email`) — On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="wpst_user_login">, <input type="text" name="wpst_user_or_email">.

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "en-US"*

- **[PASS]** <html lang="en-US"> is set and valid

### Tabindex Anti-Patterns (A+ — 100/100)

*1 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (B — 70/100)

*3/3 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="https://cdn.creativesumo.com/html/c/8/c83162daf2754a01e3fc482819db0ec3.html") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://atwmcd.com/natlf/lf/ch/?c=object_container&site=fetishfix&cobrandId=&ps…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (A+ — 100/100)

*All 156 visible text node(s) render at >= 12 CSS pixels*

- **[PASS]** All text uses legible mobile font sizes (>= 12 CSS px)

---

## UX

### 404 Error Page (F — 25/100)

*HTTP 500, custom page*

- **[WARNING]** Unexpected status code: HTTP 500 — Expected HTTP 404 but received 500. This may confuse search engine crawlers.
- **[PASS]** Custom styled 404 page

### Favicon & Branding (F — 15/100)

*1 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

### Web Manifest (D — 40/100)

*Not found*

- **[INFO]** No web manifest found — No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (D — 40/100)

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (D — 40/100)

*2 navigation pattern(s)*

- **[PASS]** Skip navigation link detected
- **[PASS]** Back-to-top link detected
- **[PASS]** 1 navigation landmark(s) detected

### Mobile UX Depth (A+ — 97/100)

*1 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

---

## SEO

### Canonical URL (A+ — 100/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target reachable (self-referencing)

### Meta Tags (A+ — 100/100)

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (54 chars) is optimal
- **[PASS]** Meta description length (143 chars) is optimal
- **[PASS]** Title and H1 are well-aligned

### Title Style Depth (B — 75/100)

*2 title-style issue(s) detected*

- **[INFO]** Title uses 2 different separator characters: -, | — The page title `Fetish4All.com - Fetish Adult Porn | Feed Your Fetish!` uses multiple separator characters (-, |). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.
- **[WARNING]** Title repeats `fetish` 3 times -- likely keyword stuffing — The word `fetish` appears 3 times in the title. Modern search engines penalize keyword stuffing -- repeating a target keyword multiple times in the title was a 2008-era SEO tactic that now triggers spam-filter signals. Use the keyword once and rely on natural variations (synonyms, related terms) for the rest of the title.

### Content Depth (A — 85/100)

*1120 words, Fairly Difficult*

- **[PASS]** Page has 1120 words — good depth for search engines
- **[INFO]** Text-to-HTML ratio is 3% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Fairly Difficult (grade 13)

### Internal Links (A+ — 100/100)

*128 internal, 10 external*

- **[PASS]** 128 internal links (93%)
- **[PASS]** 99% of links use descriptive anchor text
- **[INFO]** 128 internal / 10 external links

### Image SEO (A+ — 100/100)

*58 images, 58 descriptive filenames*

- **[PASS]** All images have descriptive filenames

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (A+ — 100/100)

*Sitemap updated within 90 days (44/44 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: 1 months ago

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts detected*

- **[PASS]** Sitemap URLs are not blocked by robots.txt

### Sitemap Hygiene (A+ — 100/100)

*Sitemap structure / size look healthy (44 URLs, 6 KB)*

- **[PASS]** Sitemap structure / size look healthy (44 URLs)

### Markup Quality (A+ — 95/100)

*1 markup-quality issue(s) detected*

- **[INFO]** 3 redundant ARIA role attribute(s) on native semantic element(s) — The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.

---

## Sustainability

### CO2 Per Page Load (F — 15/100)

*5.16g CO2 per view*

- **[CRITICAL]** 5.16g CO2 per page view — This page transfers 18.2 MB, producing an estimated 5.16g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.95g, network 0.89g, end-user device 3.31g.
- **[INFO]** At 10,000 monthly views: 618.7 kg CO2/year — With 10,000 page views per month, this page would generate approximately 618.7 kg of CO2 annually — equivalent to charging 77338 smartphones.

### Green Hosting (D — 40/100)

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 46 KB (vs 18642 KB first visit). 154 of 157 resources are served from browser cache, saving 5.14g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 5.16g)

### Carbon Budget (F — 15/100)

*95th percentile*

- **[WARNING]** 5.16g CO2 — above the median website (0.60g) — Heavier than an estimated 5% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 95th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (A+ — 100/100)

*99% efficient*

- **[PASS]** Transfer efficiency: 99% — Only 246 KB of potential savings identified. Your page is well-optimized for size.

### Web Font Weight Variants (B — 90/100)

*No detectable Google Fonts weights*

- **[INFO]** No detectable Google Fonts weights — The analyzer detects font weights via Google Fonts URL parameters (~70% of font-using sites). Self-hosted fonts and non-Google CDN fonts aren't visible to URL-based detection. If you self-host fonts, manually audit how many @font-face weights you ship -- 2-3 weights per family is typically enough; 5+ is usually unused payload.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/2994ccf4-ce99-4a59-9b3e-15b8b19797fa*
