# BeaverCheck Audit Report — https://akj.io

**Date:** May 10, 2026  
**URL:** https://akj.io  
**Overall Grade:** B (84/100)  
**Report:** https://beavercheck.com/results/c1043dde-6e7a-4a82-863f-c6f996a78fd2

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[CRITICAL]** Page body has only 168 chars of text -- likely empty / placeholder — Security > Empty Page Detection
4. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers
5. **[WARNING]** No DMARC record found — Security > Email Security

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 98 |
| Accessibility | 69 |
| Best Practices | 96 |
| SEO | 80 |

---

## Security

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

*8 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy has a weak value
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[PASS]** Cross-Origin-Opener-Policy is properly configured
- **[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: removed) — 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 (C — 60/100)

*7 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[PASS]** object-src is set to 'none'
- **[PASS]** base-uri is properly restricted
- **[PASS]** frame-ancestors directive is set
- **[PASS]** form-action directive is set
- **[PASS]** upgrade-insecure-requests is enabled

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

*TLS 1.3, 7 checks passed*

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

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

### security.txt (A+ — 100/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found

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

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

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

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

*2 inline style attribute(s) detected*

- **[INFO]** 2 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. 2 inline style(s) is low. Affected element types include: div. 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) (B — 95/100)

*Trusted Types not enabled*

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

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

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

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

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

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

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

### Empty Page Detection (F — 0/100)

*1 empty-page signal(s) detected -- page may be a placeholder or have content-rendering bugs*

- **[CRITICAL]** Page body has only 168 chars of text -- likely empty / placeholder — After HTML stripping, the page body contains 168 characters of text content. Below 200 chars almost always means: (1) the page is a placeholder that was never filled in, (2) JavaScript was supposed to render content but failed, (3) the page is a redirect / interstitial / wrapper that should have a real status code other than 200, or (4) it's a legitimately small page like a single-form login (in which case this finding is a false positive that confirms 'minimal content' is intentional).

Review the page in a browser. If content is missing, the most common root cause is a JS-rendering pipeline that needs prerendering or server-side rendering for crawlers / scanners to capture content.

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

*Page has no third-party scripts or stylesheets -- SRI not applicable*

- **[PASS]** No third-party scripts or stylesheets to protect with SRI

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

*1 CORS depth signal(s) detected*

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

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

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

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

Covered: camera, microphone, geolocation

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

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

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

*Referrer-Policy is `origin-when-cross-origin` (leaky -- origin sent cross-origin even on protocol downgrade)*

- **[WARNING]** Referrer-Policy: `origin-when-cross-origin` -- leaky -- origin sent cross-origin even on protocol downgrade — Same-origin requests get full URL; cross-origin gets only origin. Similar shape to the modern default BUT does NOT suppress Referer on HTTPS-to-HTTP downgrade -- the origin leaks even when the protocol is downgrading to HTTP. Switch to `strict-origin-when-cross-origin` for the same UX with no downgrade leak.

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

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

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

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

*No external resources*

- **[PASS]** No external resources to protect

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

*No known vulnerabilities*

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

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

*No exposures*

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

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

*no DMARC, SPF: ?all, DKIM*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** SPF ends in ?all — provides no enforcement — ?all (neutral) and +all (pass-everything) make the SPF record decorative. Receivers will accept any sender. Switch to -all (hard fail) or ~all (soft fail).
- **[PASS]** DKIM configured (selectors: fm3, fm1, fm2)
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

### Permissions-Policy (B — 80/100)

*4 directives, 2 missing*

- **[PASS]** camera=() — blocked for all origins
- **[PASS]** microphone=() — blocked for all origins
- **[PASS]** geolocation=() — blocked for all origins
- **[PASS]** browsing-topics=() — blocked for all origins
- **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content.
- **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content.

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

*Origin: **

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

---

## Performance

### Page Weight Budget (A+ — 100/100)

*447 KB transferred, 22 requests*

- **[PASS]** Page weighs 865 KB (447 KB transferred)
- **[PASS]** 22 HTTP requests
- **[INFO]** Estimated 0.09 g CO2 per page load

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

*No third-party resources*

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

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

*All text resources are compressed*

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

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

*No images on this page*

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

### JS Execution Cost (B — 80/100)

*958ms total JS execution*

- **[WARNING]** Unattributable: 277ms CPU time
- **[INFO]** https://akj.io/: 245ms CPU time
- **[INFO]** https://akj.io/_next/static/chunks/643ad021-013c34...: 234ms CPU time
- **[INFO]** https://akj.io/_next/static/chunks/402-47bfdc5efea...: 201ms CPU time
- **[INFO]** Third-party scripts: 277ms (29% of total)

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

*2 fonts (54 KB)*

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

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

*11 scripts, 73 KB unused*

- **[WARNING]** https://akj.io/_next/static/chunks/390-2daba5734f8...: 28 KB unused (75%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://akj.io/_next/static/chunks/402-47bfdc5efea...: 24 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://akj.io/_next/static/chunks/643ad021-013c34...: 21 KB unused (34%) — 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)

*No optimization needed*

- **[PASS]** No resource hint issues

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

*HTTP/3 not advertised*

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

### Compression Algorithm (C — 70/100)

*Main response served uncompressed*

- **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-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).
- **[PASS]** `ETag` present -- conditional GET supported

### Page Weight Inventory (A+ — 100/100)

*22 resources · 447 KB · 73 KB savings available*

- **[PASS]** Within 1MB page-weight target
- **[INFO]** ~73 KB of savings available

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

*No render-blocking JS or document.write usage detected*

- **[PASS]** No JavaScript blocking issues detected

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

*No CSS performance depth issues detected*

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

---

## Content Quality

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

*1 links checked, 1 healthy, 0 broken*

- **[PASS]** 1 of 1 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 (F — 0/100)

*No Open Graph tags found — social sharing previews will be generic.*

- **[WARNING]** No Open Graph meta tags found — Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

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

*No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)*

- **[PASS]** No OG image / Twitter card to evaluate

### Structured Data (C — 40/100)

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

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

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

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

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

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

*No images to analyze*


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

*No autoplay media on the page*

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

---

## Infrastructure

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

*1 A records, 48 ms lookup*

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

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

*No subdomain takeover risk detected*

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

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

*Signed and validating*

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

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

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

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

### Reverse DNS (C — 60/100)

*0/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 76.76.21.21: lookup 76.76.21.21: 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 (C — 65/100)

*Mean 93ms across 3 resolvers (spread 259ms)*

- **[PASS]** Quad9: 0ms
- **[PASS]** Cloudflare: 22ms
- **[PASS]** Google: 259ms
- **[INFO]** High latency spread between resolvers: 259ms (min 0ms / max 259ms) — Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

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

*No redirects — direct access*

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

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

*No IPv6 support*

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

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

*robots.txt present, sitemap with 15 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 15 entries
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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

- **[WARNING]** HTTP→HTTPS redirect uses 302 instead of 301

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

*akj.io — via 101domain GRS Limited, 11 years, 5 months old, hosted on AWS*

- **[PASS]** Domain registered until Jan 15, 2028 (1 years, 8 months remaining)
- **[PASS]** Registrar: 101domain GRS Limited
- **[PASS]** Registrar lock is enabled — Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
- **[PASS]** Hosting: AWS

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (B — 80/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected — 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
- **[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 (B — 70/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[WARNING]** <html lang> value may be invalid — Use a valid BCP 47 language tag (e.g. 'en', 'fr', 'de-DE').
- **[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.

### 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 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: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

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

*1 trackers detected*

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

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

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

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

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

*No image data to inspect for tracking pixels*

- **[PASS]** No image data to inspect for tracking pixels

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*0 of 7 expected legal pages detected*

- **[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 (C — 55/100)

*No copyright notice detected*

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

### Regulatory Indicators

*0 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### Third-Party Data Sharing

*0 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

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

*0 compliance badge(s) detected*

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

---

## Availability

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

*Vercel (HIT)*

- **[PASS]** Site is served via Vercel CDN
- **[PASS]** CDN cache status: HIT

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

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

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

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

*No status page link detected*

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

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

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

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

### Health Check Endpoint (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: HIT*

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

---

## Accessibility

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

*2 landmarks*

- **[PASS]** <main> landmark present
- **[WARNING]** No <nav> landmark found
- **[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 (B — 80/100)

*No headings*

- **[WARNING]** No headings found — Headings (H1-H6) create the document outline for screen reader navigation.

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

*No headings to evaluate -- check is N/A*

- **[PASS]** No headings to evaluate -- check is N/A

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

*No images*

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

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

*No form controls*

- **[PASS]** No form controls on this page

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

*1 links, 0 buttons — all OK*

- **[WARNING]** 1 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.

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

*No form controls on this page*

- **[PASS]** No form controls on this page

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

*No form controls on this page*

- **[PASS]** No form controls on this page

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

*No form controls -- mobile keyboard check is N/A*

- **[PASS]** No form controls on this page

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

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

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

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

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

---

## UX

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

*HTTP 404, bare page*

- **[PASS]** Correct 404 status code returned
- **[WARNING]** Bare server default 404 page — The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

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

*1 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

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

*Not found*

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

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

*No PWA depth issues detected*

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

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

*Dark mode detected*

- **[PASS]** Dark-specific theme-color detected — A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
- **[PASS]** prefers-color-scheme CSS detected in inline styles
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

*No print styles*

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

### Navigation UX (F — 0/100)

*No navigation patterns*

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

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

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

*Minor issues*

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

### Meta Tags (B — 75/100)

*Title: 26 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 26 characters — consider expanding
- **[WARNING]** No meta description tag found — Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.

### 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 (F — 10/100)

*18 words, Very Difficult*

- **[CRITICAL]** Page has only 18 words — nearly empty — Search engines need substantive text content to understand and rank a page.
- **[INFO]** Text-to-HTML ratio is 0% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Very Difficult (grade 14)
- **[WARNING]** Thin content — only 18 words

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

*0 internal, 1 external*

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

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

*No images*

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

### 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 (15/15 URLs have lastmod)*

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

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

*No sitemap-vs-robots conflicts detected*

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

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

*Sitemap structure / size look healthy (15 URLs, 2 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (A+ — 100/100)

*0.10g CO2 per view*

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

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

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Vercel: Hosted on AWS/Google Cloud with renewable energy commitments
- **[INFO]** Vercel: Hosted on AWS/Google Cloud with renewable energy commitments
- **[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)

*98% cached*

- **[PASS]** 98% reduction on repeat visits — Returning visitors download only 8 KB (vs 446 KB first visit). 21 of 22 resources are served from browser cache, saving 0.10g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.10g)

### Carbon Budget (A+ — 100/100)

*10th percentile*

- **[PASS]** 0.10g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 90% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 10th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (B — 80/100)

*84% efficient*

- **[INFO]** Transfer efficiency: 84% — An estimated 72 KB (16%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 72 KB of unused JavaScript. This wasted data produces 0.02g of unnecessary CO2 per page view.

### 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/c1043dde-6e7a-4a82-863f-c6f996a78fd2*