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

**Date:** October 29, 2026  
**URL:** https://thebitsignal.com  
**Overall Grade:** B (83/100)  
**Report:** https://beavercheck.com/results/5c895bc0-4691-49cb-8652-249a553a5475

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Cookie 'anon_id' is missing the Secure flag — Security > Cookie Security
3. **[CRITICAL]** Cookie 'device_id' is missing the Secure flag — Security > Cookie Security
4. **[CRITICAL]** 1 link(s) with no accessible text — Accessibility > Link & Button Quality
5. **[WARNING]** 2 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 61 |
| Accessibility | 84 |
| Best Practices | 77 |
| SEO | 100 |

---

## Security

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

*1 of 10 headers properly configured*

- **[WARNING]** HSTS is enabled but missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP.
- **[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.
- **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

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

*No enforcing CSP policy found*

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

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

*TLS 1.3, 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 72 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 — 70/100)

*2 cookies analyzed, 4 checks passed*

- **[CRITICAL]** Cookie 'anon_id' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[PASS]** Cookie 'anon_id' has the HttpOnly flag
- **[PASS]** Cookie 'anon_id' has SameSite=Lax
- **[CRITICAL]** Cookie 'device_id' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[PASS]** Cookie 'device_id' has the HttpOnly flag
- **[PASS]** Cookie 'device_id' has SameSite=Lax

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

*1 hygiene issue(s) across 2 cookie(s)*

- **[INFO]** 1 cookie(s) live for more than 1 year — Cookies with Max-Age or Expires more than 1 year out are effectively permanent on the user's device. Most session and preference cookies don't need that lifetime. Long-lived tracking cookies also carry a heavier compliance load (GDPR / CCPA). Affected: device_id.

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a5221b7beb5720a1-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)

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

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

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

*9 inline style attribute(s) detected*

- **[INFO]** 9 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. 9 inline style(s) is low. Affected element types include: audio, div, img. 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/2 third-party resources)*

- **[WARNING]** SRI adoption: 0/2 third-party resources protected (0%) — Of 2 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 2 examples):
  - https://www.googletagmanager.com/gtag/js?id=G-H1SLDGF08P
  - https://challenges.cloudflare.com/turnstile/v0/api.js?render=explicit

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 10 candidate URL(s))*

- **[PASS]** No source maps accessible across 10 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 2 external resources have SRI*

- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from challenges.cloudflare.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

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

*No known vulnerabilities*

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

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

*No exposures*

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

### Email Security (B — 82/100)

*DMARC: reject, SPF: ~all, DKIM*

- **[PASS]** DMARC policy is reject — strongest protection
- **[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).
- **[PASS]** DKIM configured (selectors: google)
- **[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 — 2/100)

*3.8 MB transferred, 70 requests*

- **[WARNING]** Page weighs 5.4 MB (3.8 MB transferred)
- **[WARNING]** Images are 2.3 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[INFO]** 70 HTTP requests
- **[INFO]** Estimated 0.81 g CO2 per page load

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

*85% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 85% of page weight (3.3 MiB of 3.8 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)

*24 images, 0 KB saveable*

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

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

*1881ms total JS execution*

- **[WARNING]** https://thebitsignal.com/_next/static/chunks/2117-...: 489ms CPU time
- **[WARNING]** Unattributable: 393ms CPU time
- **[WARNING]** https://thebitsignal.com/: 382ms CPU time
- **[WARNING]** https://thebitsignal.com/cdn-cgi/challenge-platfor...: 331ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtag/js?id=G-H1SL...: 135ms CPU time
- **[INFO]** Third-party scripts: 193ms (10% of total)

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

*2 fonts (132 KB)*

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

### JS Bundles (B — 80/100)

*20 scripts, 73 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-H1SL...: 73 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 73 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)

*4 hints, 0 missing preconnects*

- **[PASS]** Page uses 4 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 max-age=0 (≤ 5min) is appropriate*

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

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

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

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

*70 resources · 3.8 MB · 73 KB savings available*

- **[WARNING]** Page weight 3.8 MB exceeds 1 MB target by 2.8 MB
- **[INFO]** ~73 KB of savings available
- **[WARNING]** 38 third-party resources (85% of weight)
- **[INFO]** 4 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]** 2 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 (F — 40/100)

*163 links checked, 91 healthy, 72 broken*

- **[CRITICAL]** 91 of 163 links are healthy
- **[CRITICAL]** Broken link: https://thebitsignal.com/events — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/companies — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/people — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/paths — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/episodes — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/btc-sessions/bitcoin-break... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/btc-sessions — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast/a... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-takeover-podcast/d... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-takeover-podcast — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-blockspace-podcast/blo... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-blockspace-podcast — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-news-alerts-daily-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-news-alerts-daily-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-blockspace-podcast/ins... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/btc-sessions/ep-104-cia-wa... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simon-dixon-hard-talk/this... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simon-dixon-hard-talk — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/the-ai-bail... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/leaked-here... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/coin-stories/bitcoin-dips-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/coin-stories — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/bi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast/m... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/bi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-jack-mallers-show/fran... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-jack-mallers-show — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast/j... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/btc-sessions/simply-sessio... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast/s... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/btc-sessions/this-signal-c... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-bitcoin-way-podcast/ar... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-bitcoin-way-podcast — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-magazine-podcast/r... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-blockspace-podcast/spa... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/ro... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/michael-say... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/st... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-for-millennials/bi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/bitcoin-in-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/crypto-voices/is-147k-poss... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/ut... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/s-p-500-s-h... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/ungovernable-misfits/the-l... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-well-podcast/bitco... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-for-millennials/wh... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/ungovernable-misfits/keepi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/rabbit-hole-recap/rome-s-t... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-for-millennials/bi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-jack-mallers-show/bein... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-bitcoin-way-podcast/th... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/simply-bitcoin/ep-1618-sim... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-bitcoin-way-podcast/wh... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-for-millennials/wh... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-for-millennials — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/less-noise-more-signal/fra... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/less-noise-more-signal — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/stacker-news-live/fridges-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/stacker-news-live — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/wa... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/the-wolf-of-all-streets/bi... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/stephan-livera-podcast/ep-... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/stephan-livera-podcast — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/bitcoin-takeover-podcast/e... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/ungovernable-misfits/a-lot... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/ungovernable-misfits — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/crypto-voices/silly-season... — Found in <a href>. Returns HTTP 403.
- **[CRITICAL]** Broken link: https://thebitsignal.com/shows/crypto-voices — Found in <a href>. Returns HTTP 403.

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

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

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

*1 JSON-LD block(s) found — some improvements recommended.*

- **[WARNING]** Missing required property "name" for WebSite — The "name" property is required for the WebSite schema type.
- **[WARNING]** Missing required property "url" for WebSite — The "url" property is required for the WebSite schema type.
- **[INFO]** Missing recommended property "description" for WebSite — Adding "description" can improve how search engines display your content.
- **[INFO]** Missing recommended property "potentialAction" for WebSite — Adding "potentialAction" can improve how search engines display your content.

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

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

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

Organization, 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 (F — 55/100)

*5 issues found across 79 images*

- **[WARNING]** 4 images significantly larger than display size — Resizing to display dimensions could save approximately 7 KB.
- **[WARNING]** 79 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.
- **[INFO]** 69 of 79 images use legacy formats
- **[INFO]** 8 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://thebitsignal.com/_next/image?url=%2Fhero-transparent.avif&w=384&q=75&dpl=dpl_hJUX3zrpTnkFtVLbYQGwb2jGFPPJ, https://i.ytimg.com/vi/031ks2nfIcw/hqdefault.jpg, https://i.ytimg.com/vi/zpNQcVVlk7w/hqdefault.jpg (+5 more).

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

*1 media element(s) found, none autoplay*

- **[PASS]** 1 media element(s) found, none autoplay

---

## Infrastructure

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

*2 A records, 2 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[PASS]** Has 2 IPv6 (AAAA) record(s)
- **[PASS]** 2 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 2 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 188.114.97.2: lookup 188.114.97.2: 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 188.114.96.2: lookup 188.114.96.2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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 19ms across 3 resolvers (spread 28ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Google: 29ms
- **[PASS]** Cloudflare: 29ms

### 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 2a06:98c1:3120::2, 2a06:98c1:3121::2

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

*robots.txt present, sitemap with 50001 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 50001 entries
- **[PASS]** robots.txt references sitemap

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

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

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

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

*thebitsignal.com — via GoDaddy.com, LLC, 1 years, 4 months old*

- **[PASS]** Domain registered until Jun 13, 2027 (7 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: GoDaddy.com, LLC
- **[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 (B — 75/100)

*No consent signals detected*

- **[WARNING]** No privacy policy found (page links and common paths checked) — No link matching the privacy-policy vocabulary was found in the rendered page, and the common privacy-policy paths returned nothing. A privacy policy page is recommended for transparency and may be legally required.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[WARNING]** 2 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): anon_id, device_id
- **[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 (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 (F — 25/100)

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

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

### Third-Party Trackers (C — 55/100)

*4 trackers detected*

- **[INFO]** 4 third-party trackers detected — Found 3 analytics, 0 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 4 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

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

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

- **[INFO]** 1 cookie(s) could not be classified
- **[INFO]** 4 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 (F — 0/100)

*0 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[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 (A+ — 100/100)

*© 2026 The Bit Signal Your Bitcoin signal*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 The Bit Signal Your Bitcoin signal
- **[PASS]** Copyright holder: The Bit Signal Your Bitcoin signal

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

*2 third-party service(s) detected*

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

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

*0 compliance badge(s) detected*

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

---

## Availability

### CDN & Delivery (A — 85/100)

*Document on Cloudflare; assets also on Fastly, Akamai, AWS CloudFront*

- **[PASS]** Document is served via Cloudflare CDN (edge: CDG)
- **[INFO]** CDN cache status: DYNAMIC
- **[PASS]** Assets on Cloudflare: media.beehiiv.com (assets: 5), cache HIT
- **[PASS]** Assets on Fastly: megaphone.imgix.net (assets: 4), cache HIT, HIT
- **[PASS]** Assets on Akamai: artwork.captivate.fm (assets: 3)
- **[PASS]** Assets on Cloudflare: assets.podhome.fm (assets: 3), cache DYNAMIC
- **[PASS]** Assets on Cloudflare: feeds.fountain.fm (assets: 3)
- **[PASS]** Assets on AWS CloudFront: image.simplecastcdn.com (assets: 3), cache Hit from cloudfront

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

*public, max-age=0, must-revalidate*

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

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

*No status page link detected*

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

### Transport Security (A+ — 100/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.
- **[PASS]** HSTS enabled (base policy)
- **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

### CDN Cache Observability (A+ — 100/100)

*Cache state: DYNAMIC*

- **[PASS]** CDN cache state observable via 3 header(s)

---

## Accessibility

### Landmark Structure (B — 70/100)

*8 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 2 <nav> landmark(s) found
- **[WARNING]** 2 of 2 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[INFO]** No banner (header) 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+ — 100/100)

*39 headings*

- **[PASS]** Single H1 present

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

*All 39 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 79 images OK*

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

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

*2 of 2 controls have issues*

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

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

*1 issue(s) across 166 links and 29 buttons*

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

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

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

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

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

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

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

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

*2/2 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: email.
- **[WARNING]** 1 field(s) would benefit from inputmode attribute — Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

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

*Lang attribute set to "en"*

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

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

*No explicit tabindex attributes found*

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

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

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

- **[WARNING]** <iframe> missing title attribute (src="") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (D — 60/100)

*14 tap target(s) too small or too close together*

- **[WARNING]** 14 tap target(s) too small or too close to neighbors — WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

### Mobile-Readable Font Sizes (D — 60/100)

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

- **[WARNING]** 178 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> 11.0px ("Bitcoin podcasts · tuned to you"); <span> 11.0px ("$80,060"); <span> 11.0px ("BLOCK"); <span> 11.0px ("973,690"); <span> 11.0px ("19,595").

---

## 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)

*6 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (A+ — 100/100)

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: The Bit Signal
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*No navigation patterns*

- **[PASS]** 2 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)
- **[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+ — 97/100)

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Properly configured*

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

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

*Title: 62 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 62 characters — may be truncated in search results
- **[INFO]** Meta description is 162 characters — truncated on mobile (~160 char limit)
- **[PASS]** Title and H1 are well-aligned

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

*1142 words, Standard*

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

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

*164 internal, 2 external*

- **[PASS]** 164 internal links (99%)
- **[PASS]** 99% of links use descriptive anchor text
- **[INFO]** 164 internal / 2 external links

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

*79 images, 73 descriptive filenames*

- **[INFO]** 6 image(s) have hash/generic filenames

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

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

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

- **[PASS]** Sitemap actively maintained — newest lastmod: 3 days ago

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

*No sitemap-vs-robots conflicts in the URL sample*

- **[PASS]** All 5 sampled sitemap URLs are crawlable per robots.txt

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

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

- **[WARNING]** Sitemap contains 50001 URLs -- approaching the 50,000 protocol cap — The sitemap.xml protocol caps each file at 50,000 URLs (or 50MB uncompressed). Sitemaps that exceed either limit have the overflow silently dropped by Google and other crawlers. Split into multiple sitemap files indexed by a sitemap index (`<sitemapindex>`) before you hit the ceiling.

### 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.8 MB, producing an estimated 0.91g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.02g, network 0.19g, end-user device 0.70g.
- **[INFO]** At 10,000 monthly views: 109.2 kg CO2/year — With 10,000 page views per month, this page would generate approximately 109.2 kg of CO2 annually — equivalent to charging 13645 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)

*94% cached*

- **[PASS]** 94% reduction on repeat visits — Returning visitors download only 218 KB (vs 3935 KB first visit). 68 of 70 resources are served from browser cache, saving 0.86g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.05g 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)

*98% efficient*

- **[PASS]** Transfer efficiency: 98% — Only 73 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/5c895bc0-4691-49cb-8652-249a553a5475*