# BeaverCheck Audit Report — https://watsnaydouch.site

**Date:** September 13, 2026  
**URL:** https://watsnaydouch.site  
**Overall Grade:** B (81/100)  
**Report:** https://beavercheck.com/results/27d5937a-83df-4cb5-839d-219b76d0f3fa

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality
4. **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — Accessibility > 404 Error Page
5. **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 62 |
| Accessibility | 90 |
| Best Practices | 100 |
| SEO | 92 |

---

## Security

### Security Headers (B — 70/100)

*6 of 10 headers properly configured*

- **[PASS]** HSTS is enabled with preload
- **[PASS]** X-Content-Type-Options is properly configured
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[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 (D — 45/100)

*4 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[PASS]** frame-ancestors directive is set
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

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

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[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 81 days)
- **[PASS]** Certificate chain has 4 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 1 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 (B — 70/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt: Missing required 'Contact' field
- **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116)

### Cross-Origin Tab Safety (A+ — 100/100)

*All 2 new-tab link(s) carry rel=noopener*

- **[PASS]** All 2 new-tab link(s) carry rel=noopener

### CSP Inline-Style Readiness (A+ — 100/100)

*No inline style attributes -- strict CSP is feasible*

- **[PASS]** No inline style attributes detected

### Trusted Types (XSS Sink Hardening) (B — 95/100)

*Trusted Types not enabled*

- **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

### 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/1 third-party resources)*

- **[WARNING]** SRI adoption: 0/1 third-party resources protected (0%) — Of 1 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 1 examples):
  - https://fonts.googleapis.com/css2?family=Battambang:wght@400;700&family=Koulen&family=Moul&family=Rajdhani:wght@300;400;500;600;700&display=swap

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 — 90/100)

*1 CORS depth signal(s) detected*

- **[INFO]** CORS allows any origin (`Access-Control-Allow-Origin: *`) — Any website can fetch this URL via JavaScript and read the response body. Acceptable for genuinely public APIs (e.g. CDN-served static assets). Risky if the URL returns user-specific or session-derived data, since other origins can scrape it via the user's browser without needing credentials. Narrow Allow-Origin to a specific origin allow-list when the response is sensitive.

### Permissions-Policy Granularity (D — 50/100)

*30% high-risk feature coverage (3/10)*

- **[WARNING]** Permissions-Policy covers 3/10 high-risk features (30%) — The Permissions-Policy header explicitly declares policies for 3/10 high-risk features.

Covered: camera, microphone, geolocation

Not declared (default-allow): payment, usb, serial, midi, accelerometer, gyroscope, magnetometer

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 (A+ — 100/100)

*Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)*

- **[PASS]** Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin — The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

### Source Map Exposure (D — 60/100)

*2 publicly-accessible source map(s) -- full source code leaked*

- **[WARNING]** 2 publicly-accessible JavaScript source map(s) — Source maps (.js.map files) reveal the original source code -- variable names, comments, file structure, and sometimes secrets that were stripped from the bundled output. They're shipped to production by mistake almost universally; the standard fix is a build-tool config flag (Webpack: `devtool: false` or `'hidden-source-map'`; Vite: `build.sourcemap: false`; Next.js: `productionBrowserSourceMaps: false`). Once removed, audit your CDN/edge cache to evict any previously-cached .map URLs. Sample accessible URLs: https://watsnaydouch.site/registerSW.js.map, https://watsnaydouch.site/assets/index-Cd66_aKO.js.map.

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### 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 1 external resources have SRI*

- **[WARNING]** External link from fonts.googleapis.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*

- **[PASS]** security.txt is present — good practice
- **[PASS]** No sensitive files exposed

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

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[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 (B — 75/100)

*3 directives, 2 missing*

- **[PASS]** camera=() — blocked for all origins
- **[PASS]** microphone=() — blocked for all origins
- **[PASS]** geolocation=() — blocked for all origins
- **[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 (C — 60/100)

*Origin: **

- **[INFO]** Access-Control-Allow-Origin: * — unrestricted — Any website can read this resource's response. Appropriate for public APIs but not for user-specific content.
- **[INFO]** Origin reflection not testable with a single request — Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header.

---

## Performance

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

*3.2 MB transferred, 26 requests*

- **[WARNING]** Page weighs 4.7 MB (3.2 MB transferred)
- **[WARNING]** Images are 1.4 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[PASS]** 26 HTTP requests
- **[INFO]** Estimated 0.67 g CO2 per page load

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

*3% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 3% of page weight (91.6 KiB of 3.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 (A — 90/100)

*2 images, 0 KB saveable*

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

### JS Execution Cost (C — 60/100)

*1036ms total JS execution*

- **[WARNING]** Unattributable: 518ms CPU time
- **[WARNING]** https://watsnaydouch.site/: 281ms CPU time
- **[INFO]** https://watsnaydouch.site/assets/index-Cd66_aKO.js: 236ms CPU time

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

*8 fonts (165 KB)*

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

### JS Bundles (D — 50/100)

*5 scripts, 206 KB unused*

- **[WARNING]** https://watsnaydouch.site/assets/vendor-export-BNq...: 131 KB unused (75%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://watsnaydouch.site/assets/index-Cd66_aKO.js: 49 KB unused (44%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://watsnaydouch.site/assets/vendor-motion-DTu...: 25 KB unused (58%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://watsnaydouch.site/assets/vendor-lucide-PAw...: unminified — 4 KB could be saved
- **[INFO]** Total unused JavaScript: 206 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+ — 100/100)

*3 hints, 0 missing preconnects*

- **[PASS]** Page uses 3 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.

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

*Document response uses brotli*

- **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

### Asset Compression

*No text asset hosts to measure*

- **[INFO]** No third-party or subdomain host served enough text assets to measure — Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

### 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 uses no-cache -- safe revalidate-on-request policy*

- **[PASS]** Main HTML uses no-cache -- safe revalidate-on-request policy

### 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+ — 100/100)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — 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).
- **[PASS]** Both `ETag` and `Last-Modified` present -- efficient revalidation supported — The page returns both `ETag` (content hash) and `Last-Modified` (timestamp) headers. Browsers can issue conditional GETs with `If-None-Match` or `If-Modified-Since`; the server returns 304 Not Modified for unchanged content, saving bandwidth. ETag is the more reliable of the two (timestamps fail in DST transitions and clock skew).

### Page Weight Inventory (C — 55/100)

*26 resources · 3.2 MB · 206 KB savings available*

- **[WARNING]** Page weight 3.2 MB exceeds 1 MB target by 2.2 MB
- **[INFO]** ~206 KB of savings available
- **[INFO]** 9 third-party resources (3% of weight)
- **[INFO]** 3 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+ — 100/100)

*No CSS performance depth issues detected*

- **[PASS]** No CSS performance depth issues detected

---

## Content Quality

### Links (A — 90/100)

*18 links checked, 16 healthy, 2 broken*

- **[WARNING]** 16 of 18 links are healthy
- **[WARNING]** Broken link: https://fonts.googleapis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://fonts.gstatic.com — Found in <link href>. Returns HTTP 404.

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (C — 75/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.
- **[INFO]** og:title is short (12 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.

### 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 (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

### Image Optimization (F — 35/100)

*5 issues found across 4 images*

- **[WARNING]** 1 images significantly larger than display size — Resizing to display dimensions could save approximately 441 KB.
- **[WARNING]** 4 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 4 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.
- **[WARNING]** Total image weight: 3442 KB (3.4 MB) — Consider compressing images, using modern formats, and serving appropriately sized images.

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

*No autoplay media on the page*

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

---

## Infrastructure

### DNS Records (A — 90/100)

*1 A records, 191 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.
- **[INFO]** No IPv6 (AAAA) records
- **[PASS]** 2 nameserver(s) configured
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 191 ms

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

*No subdomain takeover risk detected*

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

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

*Signed and validating*

- **[PASS]** DNSSEC fully signed and chain validates (ECDSAP256SHA256)

### 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 (C — 60/100)

*0/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 69.46.46.40: lookup 69.46.46.40: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (B — 80/100)

*Mean 196ms across 3 resolvers (spread 170ms)*

- **[PASS]** Quad9: 123ms
- **[PASS]** Google: 174ms
- **[PASS]** Cloudflare: 293ms

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

*No redirects — direct access*

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

### IPv6 Readiness (C — 60/100)

*No IPv6 support*

- **[INFO]** No IPv6 (AAAA) records found — IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

### Crawlability (C — 65/100)

*robots.txt present, sitemap with 0 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[WARNING]** sitemap.xml contains invalid XML — Search engines may not be able to parse the sitemap. Fix XML validation errors.
- **[WARNING]** sitemap.xml is empty — no URLs found — An empty sitemap provides no value. Add <url> entries for your pages.
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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

- **[PASS]** www/non-www redirect configured correctly (preferred: non-www)
- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*watsnaydouch.site — via Spaceship, Inc., 11 days old, hosted on RAILWAY - Railway, US*

- **[PASS]** Domain registered until Sep 2, 2027 (11 months remaining)
- **[INFO]** Domain is only 11 days old — Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
- **[PASS]** DNSSEC is enabled
- **[PASS]** Registrar: Spaceship, Inc.
- **[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.
- **[PASS]** Hosting: RAILWAY - Railway, US

---

## Compliance

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

*No testable criteria*


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

*No consent signals detected*

- **[INFO]** Privacy policy may exist but is not linked from the page — No privacy-policy link was found in the rendered page, but https://watsnaydouch.site/privacy responded. Verify the page is real and link it from the footer -- an unlinked policy is hard for visitors to find, and a scanner cannot confirm one exists from the URL alone.
- **[INFO]** No terms of service link detected
- **[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. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (D — 50/100)

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

- **[INFO]** GDPR Article 13 disclosures not assessed (policy language: km) — The privacy policy appears to be written in "km", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate.

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

*No third-party trackers detected*

- **[PASS]** No third-party trackers detected

### 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 — 0/100)

*0 of 7 expected legal pages detected*

- **[INFO]** Privacy Policy may exist but is not linked — No link to a Privacy Policy was found on the page, but https://watsnaydouch.site/privacy responded. Verify the page is real and link it from the footer -- an unlinked policy is hard for visitors (and regulators) to find.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[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 (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*0 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]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### Third-Party Data Sharing

*0 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]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

### 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 (document or assets)*

- **[WARNING]** No CDN (document or assets) — Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

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

*no-cache*

- **[PASS]** Cache-Control header is set
- **[PASS]** ETag present — enables conditional (304) responses
- **[PASS]** Last-Modified header present

### 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 (includeSubDomains, preload)
- **[PASS]** HSTS preload enabled
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (A+ — 100/100)

*Health endpoint at https://watsnaydouch.site/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://watsnaydouch.site/health

### 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 (C — 65/100)

*1 landmarks*

- **[PASS]** <main> landmark present
- **[WARNING]** No <nav> landmark found
- **[INFO]** No banner (header) landmark
- **[INFO]** No contentinfo (footer) landmark
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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

*5 headings, 1 skip(s)*

- **[PASS]** Single H1 present
- **[WARNING]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

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

*1 heading-text-quality issue(s) detected*

- **[INFO]** 5 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

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

*All 4 images OK*

- **[PASS]** 4 image(s) with good alt text

### Form Accessibility (B — 84/100)

*2 of 3 controls have issues*

- **[WARNING]** 2 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 1 control(s) properly labeled

### Link & Button Quality (B — 84/100)

*1 issue(s) across 2 links and 17 buttons*

- **[WARNING]** 2 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 1 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.

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

*3 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (A — 90/100)

*1 input-semantic issue(s) across 3 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">.

### Mobile Keyboard & Autofill (D — 60/100)

*1/1 eligible field(s) missing autocomplete or inputmode*

- **[WARNING]** 1 field(s) missing recommended autocomplete attribute — WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: current-password.

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

*Lang attribute set to "km"*

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

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

*No explicit tabindex attributes found*

- **[PASS]** No explicit tabindex attributes found

### Iframe Accessibility (A+ — 100/100)

*No iframes on this page*

- **[PASS]** No iframes on this page

### 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 25 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 — 20/100)

*Soft 404 detected*

- **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

### Favicon & Branding (B — 80/100)

*7 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** SVG favicon detected — scales perfectly to any size
- **[PASS]** Multiple icon sizes detected

### Web Manifest (F — 30/100)

*Invalid JSON*

- **[WARNING]** Manifest contains invalid JSON — Manifest at https://watsnaydouch.site/manifest.json contains invalid JSON. Browsers cannot parse it.

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

*No PWA depth issues detected*

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

### Dark Mode Support (B — 70/100)

*Dark mode detected*

- **[PASS]** Dark-specific theme-color detected — A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
- **[PASS]** prefers-color-scheme CSS detected in inline styles
- **[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 (F — 0/100)

*No navigation patterns*

- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

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

*2 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

## SEO

### Canonical URL (B — 80/100)

*Minor issues*

- **[WARNING]** No canonical tag found — Search engines will determine the canonical URL themselves, which may cause duplicate content issues.

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (36 chars) is optimal
- **[INFO]** Meta description is only 61 characters — too short to be informative
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

### Content Depth (D — 40/100)

*51 words, Very Easy*

- **[WARNING]** Page has 51 words — thin content — Most well-ranking pages have 300+ words of substantive content.
- **[INFO]** Reading level: Very Easy (grade 4)
- **[WARNING]** Thin content — only 51 words

### Internal Links (B — 70/100)

*0 internal, 2 external*

- **[WARNING]** No internal links found — Internal links help search engines discover and rank your other pages.
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 0 internal / 2 external links
- **[WARNING]** Dead-end page — no outgoing internal links

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

*4 images, 4 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 (C — 70/100)

*Sitemap exists but no <lastmod> entries*

- **[INFO]** Sitemap has no <lastmod> entries — Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.

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

*No sitemap-vs-robots conflicts detected*

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

### Sitemap Hygiene (B — 75/100)

*1 hygiene issue(s) on a 0-URL sitemap*

- **[WARNING]** Sitemap is empty -- 0 URLs listed — The sitemap file is reachable and parses as valid XML, but contains no `<url>` entries. Common causes: a templated sitemap that didn't iterate the URL set during build, a static placeholder shipped to production, or a CMS that lost its URL index. Search engines fetch and discard empty sitemaps.

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

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*0.91g CO2 per view*

- **[INFO]** 0.91g CO2 per page view — This page transfers 3.2 MB, producing an estimated 0.91g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.17g, network 0.16g, end-user device 0.58g.
- **[INFO]** At 10,000 monthly views: 109.1 kg CO2/year — With 10,000 page views per month, this page would generate approximately 109.1 kg of CO2 annually — equivalent to charging 13642 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 2 KB (vs 3288 KB first visit). 25 of 26 resources are served from browser cache, saving 0.91g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.91g)

### Carbon Budget (D — 50/100)

*58th percentile*

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

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

*94% efficient*

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

### Web Font Weight Variants (C — 70/100)

*9 font weights loaded across 4 famil(y/ies)*

- **[WARNING]** 9 font weights loaded -- likely 100+ KB of unused payload — Loading 9 font weights typically transfers 200-400 KB just for fonts. Most pages legitimately use 2-3 weights (regular + bold, maybe medium). Audit which weights your stylesheet actually applies and trim the Google Fonts URL accordingly. Affected families: Battambang, Koulen, Moul, Rajdhani.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/27d5937a-83df-4cb5-839d-219b76d0f3fa*