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

**Date:** July 13, 2026  
**URL:** https://aiseomate.com  
**Overall Grade:** B (80/100)  
**Report:** https://beavercheck.com/results/5399209e-8bfd-43a6-b4ca-f70ec36bb3d3

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
3. **[WARNING]** 31 inline style attribute(s) detected — Security > CSP Inline-Style Readiness
4. **[WARNING]** 43 third-party resources (51% of weight) — Performance > Page Weight Inventory
5. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 56 |
| Accessibility | 91 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*4 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
- **[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.
- **[WARNING]** Server header reveals version information — The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

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

*No enforcing CSP policy found*

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

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

*TLS 1.3, 7 checks passed*

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

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

### security.txt (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.

### CSP Inline-Style Readiness (C — 75/100)

*31 inline style attribute(s) detected*

- **[WARNING]** 31 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. 31 inline style(s) is moderate. Affected element types include: img, div, text. 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

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

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

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

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

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

- **[PASS]** DMARC policy is quarantine — good 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 (B — 75/100)

*3 directives, 2 missing*

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

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

*No CORS headers*

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

---

## Performance

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

*965 KB transferred, 81 requests*

- **[PASS]** Page weighs 2.1 MB (965 KB transferred)
- **[INFO]** 81 HTTP requests
- **[INFO]** Estimated 0.20 g CO2 per page load

### Third-Party Impact (B — 70/100)

*51% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 51% of page weight (495.1 KiB of 965.2 KiB)
- **[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)

*27 images, 0 KB saveable*

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

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

*2105ms total JS execution*

- **[WARNING]** https://www.redditstatic.com/ads/pixel.js: 450ms CPU time
- **[WARNING]** https://aiseomate.com/_next/static/chunks/2117-d94...: 396ms CPU time
- **[WARNING]** Unattributable: 376ms CPU time
- **[WARNING]** https://aiseomate.com/: 350ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-GX4T...: 314ms CPU time
- **[INFO]** Third-party scripts: 764ms (36% of total)

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

*1 fonts (47 KB)*

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

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

*26 scripts, 68 KB unused*

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

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

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

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

*LCP preload audit not available*

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

### Main HTML Cache-Control (B — 85/100)

*Cache-Control present but without max-age*

- **[INFO]** Main HTML Cache-Control has no max-age: s-maxage=31536000, stale-while-revalidate

### 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, Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[PASS]** `ETag` present -- conditional GET supported

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

*81 resources · 965 KB · 68 KB savings available*

- **[PASS]** Within 1MB page-weight target
- **[INFO]** ~68 KB of savings available
- **[WARNING]** 43 third-party resources (51% of weight)

---

## Infrastructure

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

*1 A records, 117 ms lookup*

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

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

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

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

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

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

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

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 66.241.124.219 does not match any cert SAN: ip-66-241-124-219.shared.customer.flyio.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 2a09:8280:1::8d:6e6c:0 does not match any cert SAN: ipv6.customer.flyio.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

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

*Mean 143ms across 3 resolvers (spread 72ms)*

- **[PASS]** Google: 107ms
- **[PASS]** Quad9: 144ms
- **[PASS]** Cloudflare: 179ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (24 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a09:8280:1::8d:6e6c:0

### Crawlability (A+ — 100/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
- **[PASS]** Sitemap index with 15 child sitemaps
- **[PASS]** robots.txt references sitemap

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

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

- **[PASS]** www/non-www redirect configured correctly (preferred: non-www)
- **[WARNING]** HTTP→HTTPS redirect uses 302 instead of 301

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

*aiseomate.com — via DreamHost, LLC, 8 months old*

- **[PASS]** Domain registered until Oct 17, 2026 (3 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: DreamHost, 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 — 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 script URLs to scan -- tracker inventory is N/A*

- **[PASS]** No script URLs to scan -- tracker inventory is N/A

### 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 HTML captured -- i18n extras check is N/A*

- **[PASS]** No HTML captured -- i18n extras check is N/A

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

*Font sizes and tap targets checked*


### Viewport Configuration (F — 30/100)

*No viewport meta tag*

- **[CRITICAL]** No viewport meta tag found — Without a viewport meta tag, the page will not render correctly on mobile devices.

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

*No accessibility statement detected*

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

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

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: . 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)

*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

### 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 HTML captured -- beacon-tracking check is N/A*

- **[PASS]** No HTML captured -- beacon-tracking check is N/A

---

## Availability

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

*No CDN detected*

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

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

*s-maxage=31536000, stale-while-revalidate*

- **[PASS]** Cache-Control header is set
- **[PASS]** CDN TTL: 52 weeks (s-maxage=31536000)
- **[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 (A+ — 100/100)

*Health endpoint at https://aiseomate.com/api/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://aiseomate.com/api/health

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

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

*Font-size measurement not available for this scan*

- **[PASS]** Font-size measurement not available for this scan

---

## UX

### 404 Error Page (C — 65/100)

*HTTP 404, custom page*

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

### Favicon & Branding (D — 50/100)

*5 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'>.
- **[PASS]** Multiple icon sizes detected

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

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: AISEOMate
- **[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 (D — 40/100)

*No dark mode signals*

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

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

*No print styles*

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

### Navigation UX (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)

*No HTML captured -- mobile-depth check is N/A*

- **[PASS]** No HTML captured -- mobile-depth check is N/A

---

## SEO

### SEO Audit Unavailable

*Content probe data missing -- see finding for details*

- **[INFO]** SEO checks could not run for this scan — Content probe data is missing for this scan -- SEO checks need the rendered DOM (canonical tag, meta description, hreflang, etc.). Common causes: bot-detection block (Akamai/Cloudflare/Imperva served the worker a challenge instead of the page), worker timeout, or the site redirected to an unrelated host.

---

## Sustainability

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

*0.22g CO2 per view*

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

### Green Hosting (B — 80/100)

*Green (hosting)*

- **[PASS]** Fly.io uses renewable energy
- **[INFO]** Fly.io: Carbon offsets for all compute
- **[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)

*97% cached*

- **[PASS]** 97% reduction on repeat visits — Returning visitors download only 33 KB (vs 965 KB first visit). 80 of 81 resources are served from browser cache, saving 0.22g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.22g)

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

*12th percentile*

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

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

*93% efficient*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/5399209e-8bfd-43a6-b4ca-f70ec36bb3d3*
