# BeaverCheck Audit Report — https://tarotai.chat

**Date:** September 16, 2026  
**URL:** https://tarotai.chat  
**Overall Grade:** B (85/100)  
**Report:** https://beavercheck.com/results/d3cdf532-be06-4bdb-bb2d-81b5f58851d3

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Cookie 'NEXT_LOCALE' is missing the Secure flag — Security > Cookie Security
3. **[CRITICAL]** HSTS header is missing — Security > Security Headers
4. **[CRITICAL]** Page weighs 13.4 MB (11.1 MB transferred) — Performance > Page Weight Budget
5. **[CRITICAL]** No <main> landmark found — Accessibility > Landmark Structure

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 36 |
| Accessibility | 96 |
| Best Practices | 96 |
| SEO | 100 |

---

## Security

### Security Headers (F — 10/100)

*2 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[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.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[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.
- **[PASS]** X-Powered-By header is not present
- **[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, 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 82 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

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

*1 cookies analyzed, 1 checks passed*

- **[CRITICAL]** Cookie 'NEXT_LOCALE' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'NEXT_LOCALE' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[PASS]** Cookie 'NEXT_LOCALE' has SameSite=Lax

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

*All 1 cookie(s) pass hygiene checks*

- **[PASS]** All 1 cookie(s) pass hygiene checks

### WAF / Bot Protection (A — 90/100)

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a3c0b2329d703ce1-CDG

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

*No new-tab links found -- no tabnabbing surface*

- **[PASS]** No new-tab links present

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

*1 inline style attribute(s) detected*

- **[INFO]** 1 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. 1 inline style(s) is low. Affected element types include: span. 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/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://umami.bestvid.net/script.js

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

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

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

*No source maps accessible (probed 1 candidate URL(s))*

- **[PASS]** No source maps accessible across 1 probed candidate(s)

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

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### 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 script from umami.bestvid.net 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 (C — 59/100)

*DMARC: reject, SPF: ~all*

- **[PASS]** DMARC policy is reject — strongest protection
- **[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 (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature 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)

*11.1 MB transferred, 167 requests*

- **[CRITICAL]** Page weighs 13.4 MB (11.1 MB transferred)
- **[WARNING]** Images are 9.8 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 645 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** Fonts are 487 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[WARNING]** 167 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 2.3 g CO2 per page load

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

*1% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 1% of page weight (104.0 KiB of 11.1 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)

*88 images, 0 KB saveable*

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

### JS Execution Cost (F — 20/100)

*9594ms total JS execution*

- **[WARNING]** https://tarotai.chat/assets/chatarot-landing-Dfs5c...: 3872ms CPU time
- **[WARNING]** https://tarotai.chat/assets/framework-DJH1pfSr.js: 2499ms CPU time
- **[WARNING]** Unattributable: 1903ms CPU time
- **[WARNING]** https://tarotai.chat/assets/three.module-UEBaNSRS....: 685ms CPU time
- **[WARNING]** https://tarotai.chat/: 552ms CPU time
- **[INFO]** Third-party scripts: 82ms (1% of total)

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

*20 fonts (487 KB)*

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

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

*38 scripts, 260 KB unused*

- **[WARNING]** https://tarotai.chat/assets/three.module-UEBaNSRS....: 100 KB unused (54%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://accounts.google.com/gsi/client: 75 KB unused (76%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://tarotai.chat/assets/chatarot-landing-Dfs5c...: 32 KB unused (53%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://tarotai.chat/assets/bottom-chrome-DXfCLf2W...: 29 KB unused (69%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://tarotai.chat/assets/markdown-it-BVcQdzKk.j...: 24 KB unused (60%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 260 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)

*23 hints, 0 missing preconnects*

- **[PASS]** Page uses 23 resource hint(s)

### HTTP/3 (QUIC) (A+ — 100/100)

*HTTP/3 advertised via Alt-Svc*

- **[PASS]** HTTP/3 (QUIC) is supported — First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.

### 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-store -- correct for sensitive/dynamic content*

- **[PASS]** Main HTML uses no-store -- correct for sensitive/dynamic content

### 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: RSC, Accept, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-P... — 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 (C — 55/100)

*167 resources · 11.1 MB · 260 KB savings available*

- **[WARNING]** Page weight 11.1 MB exceeds 1 MB target by 10.1 MB
- **[INFO]** ~260 KB of savings available
- **[INFO]** 5 third-party resources (1% of weight)
- **[INFO]** 1 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 — 90/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** Total JS execution time is 9.6 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

### CSS Performance Depth (B — 78/100)

*2 CSS depth issue(s) detected*

- **[WARNING]** 10 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.
- **[WARNING]** 5 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright.

---

## Content Quality

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

*127 links checked, 127 healthy, 0 broken*

- **[PASS]** 127 of 127 links are healthy

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

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

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

### Open Graph (A+ — 100/100)

*Open Graph tags are well configured for social sharing.*


### Open Graph / Twitter Card Depth (B — 80/100)

*2 OG/Twitter depth issue(s) detected*

- **[INFO]** og:image aspect ratio 1.00:1 (1200×1200) is outside Facebook's recommended ~1.91:1 — Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 1200×1200 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
- **[WARNING]** Twitter card is `summary_large_image` but OG image is 1200×1200 (ratio 1.00:1) -- closer to square — `twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (1200×1200, aspect ratio 1.00:1) are closer to square than wide. Twitter will crop the image to fit the wide format, often badly. Either: (1) provide a wider image (~2:1 ratio recommended; minimum 600×314, optimal 1200×630), or (2) change `twitter:card` to `summary` which uses a square thumbnail crop.

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

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

- **[WARNING]** Missing required property "name" for Organization — The "name" property is required for the Organization schema type.
- **[INFO]** Missing recommended property "url" for Organization — Adding "url" can improve how search engines display your content.
- **[INFO]** Missing recommended property "logo" for Organization — Adding "logo" can improve how search engines display your content.
- **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content.
- **[PASS]** Custom type "WebApplication" — unable to validate specific properties
- **[PASS]** 2 JSON-LD blocks found

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

*2 JSON-LD block(s) declaring 4 schema type(s)*

- **[PASS]** 4 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

FAQPage, Organization, WebApplication, 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 30 images*

- **[WARNING]** 3 images significantly larger than display size — Resizing to display dimensions could save approximately 288 KB.
- **[WARNING]** 3 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 1 of 30 images use legacy formats
- **[INFO]** 4 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://tarotai.chat/images/responsive/home-seo/what-hi-320.webp, https://tarotai.chat/images/responsive/home-seo/fate-wide-320.webp, https://tarotai.chat/images/responsive/home-seo/masters-wide-320.webp (+1 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*2 A records, 41 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[PASS]** Has 2 IPv6 (AAAA) record(s)
- **[PASS]** 2 nameserver(s) configured
- **[PASS]** 5 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 41 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 (C — 60/100)

*0/4 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 172.67.168.19: lookup 172.67.168.19: 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.
- **[INFO]** PTR lookup failed for 104.21.66.74: lookup 104.21.66.74: 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.
- **[INFO]** PTR lookup failed for 2606:4700:3031::6815:424a: lookup 2606:4700:3031::6815:424a: 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.
- **[INFO]** PTR lookup failed for 2606:4700:3034::ac43:a813: lookup 2606:4700:3034::ac43:a813: 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 (A+ — 100/100)

*Mean 22ms across 3 resolvers (spread 49ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 17ms
- **[PASS]** Google: 50ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (17 ms)*

- **[PASS]** IPv6 is configured and reachable at 2606:4700:3031::6815:424a, 2606:4700:3034::ac43:a813

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

*robots.txt present, sitemap with 450 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 450 entries
- **[PASS]** robots.txt references 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)

*tarotai.chat — via NameCheap, Inc., 9 days old*

- **[PASS]** Domain registered until Sep 7, 2027 (11 months remaining)
- **[INFO]** Domain is only 9 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.
- **[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: NameCheap, 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.

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A+ — 95/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[WARNING]** 1 unclassified cookie(s) set before any consent step — These cookies could not be matched to a known tracker or to a known essential-cookie family, so the scanner cannot tell whether consent was required. Verify each is strictly necessary; if any is analytics or advertising, it needs consent first. Unrecognized (treated as non-essential): NEXT_LOCALE
- **[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)

*All 5 hreflang tag(s) look correct*

- **[PASS]** All 5 hreflang tag(s) look correct

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

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

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

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

- **[INFO]** GDPR Article 13 disclosure coverage: 5 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 5 of 8 categories: Data Protection Officer contact (where applicable), International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Missing: Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller. 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 (A+ — 95/100)

*2 trackers detected*

- **[INFO]** 2 third-party trackers detected — Found 2 analytics, 0 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers.

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

*1 cookies · 2 trackers · 0 pre-consent*

- **[INFO]** 2 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 SameSite=None cookies -- no cross-site travel surface*

- **[PASS]** No cookies opted in to cross-site travel (SameSite=None)

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

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacy-policy, linked from footer.
- **[PASS]** Terms of Service detected — Found at /terms-of-service, linked from footer.
- **[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.
- **[PASS]** Refund / Returns Policy detected — Found at /refund-policy, linked from footer.
- **[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 (B — 80/100)

*© 2025 TAROTAI*

- **[INFO]** Copyright year is 2025 (1 year(s) behind) — Copyright year is 2025 — 1 year(s) behind. While copyright protection doesn't depend on the year being current, an outdated notice may suggest the site is not actively maintained. Update to © 2026 or use a range like © 2025–2026.
- **[PASS]** Copyright holder: TAROTAI

### 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 (moderate confidence) — Indicators suggesting GDPR may be relevant: Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### 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 (B — 80/100)

*Cloudflare*

- **[PASS]** Document is served via Cloudflare CDN (edge: CDG)

### HTTP Caching (D — 40/100)

*no-store (uncacheable)*

- **[INFO]** Cache-Control: no-store prevents all caching — Intentional for dynamic content, but increases server load for every page view.
- **[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 — 85/100)

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

- **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

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

*9 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[PASS]** 3 <nav> landmark(s) found
- **[PASS]** All <nav> elements are properly labeled
- **[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+ — 100/100)

*23 headings*

- **[PASS]** Single H1 present

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

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

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

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

*All 30 images OK*

- **[PASS]** 17 decorative image(s) correctly marked
- **[PASS]** 13 image(s) with good alt text

### Form Accessibility (A — 92/100)

*1 of 1 controls have issues*

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

### Link & Button Quality (A+ — 100/100)

*31 links, 26 buttons — all OK*

- **[PASS]** 31 link(s) with descriptive text

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

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

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

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

*1 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### 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"*

- **[PASS]** <html lang="en"> 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 (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 (D — 60/100)

*67% of visible text renders at >= 12 CSS px (70 below threshold)*

- **[WARNING]** 70 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 9.0px ("DECK · WAITE · 78 · UPRIGHT + REVERSED"); <span> 8.0px ("READER"); <span> 11.0px ("Mystic Poet · Mira Vale"); <span> 8.0px ("SPREAD"); <span> 11.0px ("Three Card").

---

## UX

### 404 Error Page (B — 80/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page
- **[PASS]** Navigation links present on 404 page
- **[PASS]** Homepage link present on 404 page

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

*11 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 (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 (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 — 15/100)

*No navigation patterns*

- **[PASS]** 3 navigation landmark(s) detected
- **[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)

*1 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.

---

## 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 returns 200

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

*Title optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (56 chars) is optimal
- **[INFO]** Meta description is 161 characters — truncated on mobile (~160 char limit)
- **[PASS]** Title and H1 are well-aligned

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

*1 title-style issue(s) detected*

- **[INFO]** Title uses 2 different separator characters: -, | — The page title `Free AI Tarot Reading & Rider-Waite Cards | TAROTAI.CHAT` 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.

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

*1712 words, Difficult*

- **[PASS]** Page has 1712 words — good depth for search engines
- **[INFO]** Reading level: Difficult (grade 11)

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

*31 internal, 0 external*

- **[PASS]** 31 internal links (100%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 31 internal / 0 external links

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

*30 images, 30 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 (A+ — 100/100)

*Sitemap structure / size look healthy (450 URLs, 30 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*2.62g CO2 per view*

- **[CRITICAL]** 2.62g CO2 per page view — This page transfers 11.1 MB, producing an estimated 2.62g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.07g, network 0.54g, end-user device 2.01g.
- **[INFO]** At 10,000 monthly views: 314.4 kg CO2/year — With 10,000 page views per month, this page would generate approximately 314.4 kg of CO2 annually — equivalent to charging 39298 smartphones.
- **[PASS]** Green hosting reduces data center emissions

### Green Hosting (A+ — 100/100)

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Next.js: Verified by the Green Web Foundation
- **[INFO]** Cloudflare: 100% renewable energy for global network since 2019
- **[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 31 KB (vs 11334 KB first visit). 166 of 167 resources are served from browser cache, saving 2.61g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 2.62g)

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

*95th percentile*

- **[WARNING]** 2.62g 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)

*98% efficient*

- **[PASS]** Transfer efficiency: 98% — Only 259 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/d3cdf532-be06-4bdb-bb2d-81b5f58851d3*