# BeaverCheck Audit Report — https://orbitapp.buzz

**Date:** September 20, 2026  
**URL:** https://orbitapp.buzz  
**Overall Grade:** B (86/100)  
**Report:** https://beavercheck.com/results/002feaa8-c70a-4655-a476-2436c153ad20

## Top Findings

1. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
2. **[WARNING]** 10 third-party resources (56% of weight) — Performance > Page Weight Inventory
3. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers
4. **[WARNING]** External script from challenges.cloudflare.com lacks integrity attribute — Security > Subresource Integrity
5. **[WARNING]** Login form does not contain a recognizable CSRF token — Security > Auth Security

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 75 |
| Accessibility | 100 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*8 of 10 headers properly configured*

- **[PASS]** HSTS is enabled
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[PASS]** Permissions-Policy is set
- **[PASS]** Content-Security-Policy is present
- **[INFO]** Cross-Origin-Opener-Policy is set but not 'same-origin'
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (B — 80/100)

*8 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.
- **[PASS]** No 'unsafe-eval' in script source
- **[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, 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 88 days)
- **[PASS]** Certificate chain has 3 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)

*1 cookies analyzed, 3 checks passed*

- **[PASS]** Cookie '__cf_bm' has the Secure flag
- **[PASS]** Cookie '__cf_bm' has the HttpOnly flag
- **[PASS]** Cookie '__cf_bm' has SameSite=None

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

*All 1 cookie(s) pass hygiene checks*

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

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a3e3be27dddbd4f9-SJC

### security.txt (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

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

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

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

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

*6 inline style attribute(s) detected*

- **[INFO]** 6 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. 6 inline style(s) is low. Affected element types include: html, span. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

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

*Trusted Types not enabled*

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

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

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

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

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

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

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

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/1 third-party resources)*

- **[WARNING]** SRI adoption: 0/1 third-party resources protected (0%) — Of 1 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 1 examples):
  - https://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 (B — 70/100)

*50% high-risk feature coverage (5/10)*

- **[INFO]** Permissions-Policy covers 5/10 high-risk features (50%) — The Permissions-Policy header explicitly declares policies for 5/10 high-risk features.

Covered: camera, microphone, geolocation, payment, usb

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

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

### Referrer-Policy Strictness (A+ — 100/100)

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

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

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

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

- **[PASS]** No source maps accessible across 2 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 (B — 80/100)

*5 auth-security finding(s) on the login page*

- **[PASS]** Login page detected — The page contains a `type=password` input and at least one identifier field (username / email). Auth-security findings below evaluate the page's hardening posture.
- **[WARNING]** Login form does not contain a recognizable CSRF token — Standard frameworks emit CSRF tokens as a hidden input named `_csrf`, `csrf_token`, `csrfmiddlewaretoken` (Django), `authenticity_token` (Rails), or `__RequestVerificationToken` (ASP.NET). None of those were found. Possibilities: (1) the form posts to an API that uses a custom header or SameSite cookie reliance for CSRF -- legitimate but not visible from this scan, (2) the form is genuinely missing CSRF protection, which would let an attacker submit logins from another origin via a hidden POST. Verify the auth flow has SOME CSRF defense.
- **[PASS]** CAPTCHA detected on page (Cloudflare Turnstile) — A CAPTCHA / bot-protection widget is loaded on the page, which adds anti-credential-stuffing protection at the cost of UX friction. Modern alternatives (Cloudflare Turnstile, Apple's Private Access Tokens) are less intrusive than reCAPTCHA v2's checkboxes.
- **[PASS]** 1 SSO / OAuth provider(s) detected: Google — Single-sign-on lowers the credential-management cost for users (no separate password) and shifts auth security to the identity provider's defense-in-depth. Each provider requires its own consent / scope decisions; the catalog is informational.
- **[INFO]** No password-reset link found on the login page — Login pages should link to a password-reset flow (typically /forgot, /reset, or a 'Forgot password?' link). Absence usually means the reset flow lives elsewhere on the site (separately reachable), but if it's truly missing, users locked out of accounts have no self-service recovery path.

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 1 external resources have SRI*

- **[WARNING]** External 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 (D — 40/100)

*DMARC: quarantine, no SPF*

- **[PASS]** DMARC policy is quarantine — good protection
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

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

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

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

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

*6 directives, 0 missing*

- **[PASS]** geolocation=() — blocked for all origins
- **[PASS]** usb=() — blocked for all origins
- **[PASS]** payment=() — blocked for all origins
- **[INFO]** camera=(self)
- **[INFO]** microphone=(self)
- **[INFO]** display-capture=(self)

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

*No CORS headers*

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

---

## Performance

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

*887 KB transferred, 62 requests*

- **[PASS]** Page weighs 2.2 MB (887 KB transferred)
- **[INFO]** 62 HTTP requests
- **[INFO]** Estimated 0.18 g CO2 per page load

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

*56% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 56% of page weight (499.7 KiB of 886.9 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 (A+ — 95/100)

*1 images, 0 KB saveable*

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

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

*3145ms total JS execution*

- **[WARNING]** https://orbitapp.buzz/assets/index-CmINsZJb.js: 1269ms CPU time
- **[WARNING]** https://orbitapp.buzz/: 974ms CPU time
- **[WARNING]** Unattributable: 557ms CPU time
- **[INFO]** https://orbitapp.buzz/~flock.js: 216ms CPU time
- **[INFO]** https://challenges.cloudflare.com/turnstile/v0/api...: 129ms CPU time
- **[INFO]** Third-party scripts: 129ms (4% of total)

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

*1 fonts (27 KB)*

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

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

*47 scripts, 104 KB unused*

- **[WARNING]** https://orbitapp.buzz/assets/client-Bn93UADq.js: 45 KB unused (83%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://orbitapp.buzz/assets/index-CmINsZJb.js: 38 KB unused (36%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://orbitapp.buzz/assets/AppShell-D2SdbX_4.js: 21 KB unused (85%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 104 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)

*1 hints, 0 missing preconnects*

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

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

*HTTP/3 not advertised*

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

### Document Compression (B — 80/100)

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

### Asset Compression

*No text asset hosts to measure*

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

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

*LCP preload audit not available*

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

### Main HTML Cache-Control (A+ — 100/100)

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

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

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[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 (A — 85/100)

*62 resources · 887 KB · 104 KB savings available*

- **[PASS]** Within 1MB page-weight target
- **[INFO]** ~104 KB of savings available
- **[WARNING]** 10 third-party resources (56% of weight)
- **[INFO]** 1 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

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

*No third-party resources detected*


### JavaScript Blocking (A+ — 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)

*34 links checked, 34 healthy, 0 broken*

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

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

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

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

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

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

- **[INFO]** og:title is short (16 characters) — Ideal length is 25–60 characters for social sharing previews.
- **[INFO]** og:description is short (39 characters) — Ideal length is 55–200 characters for social sharing previews.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.

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

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

- **[INFO]** 2 Twitter Card field(s) differ from Open Graph counterparts — Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches:
  - title: twitter="Orbit — photos, videos and private chats", og="Sign in to Orbit"
  - description: twitter="Share photos and videos from your galler...", og="Create your @username profile on Orbit."

Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.

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

*1 A records, 13 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[INFO]** No IPv6 (AAAA) records
- **[PASS]** 2 nameserver(s) configured
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 13 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/1 IPs match cert SAN*

- **[INFO]** PTR for 185.158.133.1 does not match any cert SAN: lovable-app-cd-1-4.p.l5e.io — 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 (A+ — 100/100)

*Mean 7ms across 3 resolvers (spread 12ms)*

- **[PASS]** Cloudflare: 2ms
- **[PASS]** Quad9: 6ms
- **[PASS]** Google: 14ms

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

*robots.txt present, sitemap with 4 URLs*

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

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

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

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

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

*orbitapp.buzz — via GoDaddy.com, LLC, 4 days old, hosted on Cloudflare*

- **[PASS]** Domain registered until Sep 16, 2027 (1 years remaining)
- **[INFO]** Domain is only 4 days old — Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: 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.
- **[PASS]** Hosting: Cloudflare

---

## Compliance

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

*No testable criteria*


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

*No consent signals detected*

- **[INFO]** Privacy policy may exist but is not linked from the page — No privacy-policy link was found in the rendered page, but https://orbitapp.buzz/privacy responded. Verify the page is real and link it from the footer -- an unlinked policy is hard for visitors to find, and a scanner cannot confirm one exists from the URL alone.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[PASS]** 1 essential cookie(s) on initial load — no consent required
- **[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)

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

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

*1 cross-site cookie(s) (1 tracking-shaped, 0 essential)*

- **[INFO]** 1 tracking-shaped cross-site cookie(s): __cf_bm — Cookies with SameSite=None travel in cross-site contexts (third-party iframes, cross-origin POSTs, embedded widgets). With third-party cookies dying in Chrome/Firefox, the legitimate use cases narrowed to SSO + payment widgets + federated auth. Each tracking-shaped cookie surfaced here is a cross-site analytics or ad-tech surface that needs explicit privacy-policy disclosure beyond basic cookie banner consent. Audit each: is it conditional on consent? Does the privacy policy name the recipient + purpose? Switching to SameSite=Lax disables the cross-site travel without breaking same-site analytics.

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*0 of 7 expected legal pages detected*

- **[INFO]** Privacy Policy may exist but is not linked — No link to a Privacy Policy was found on the page, but https://orbitapp.buzz/privacy responded. Verify the page is real and link it from the footer -- an unlinked policy is hard for visitors (and regulators) to find.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

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

### Regulatory Indicators

*0 regulatory indicator(s) detected*

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

### Third-Party Data Sharing

*1 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]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: CDN (1). Each of these services receives some user data from your site visitors.
- **[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 (B — 80/100)

*Cloudflare*

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

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

*no-cache, must-revalidate, max-age=0*

- **[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 — 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)
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

### Landmark Structure (C — 65/100)

*2 landmarks*

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

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

*2 headings*

- **[PASS]** Single H1 present

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

*All 2 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)

*No images*

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

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

*All 2 controls labeled*

- **[PASS]** 2 control(s) properly labeled

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

*0 links, 6 buttons — all OK*


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

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

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

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

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

- **[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)

*1 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

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

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

### Mobile-Readable Font Sizes (B — 90/100)

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

- **[INFO]** 1 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: <span> 11.0px ("or with email").

---

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

*5 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (B — 80/100)

*Valid manifest*

- **[PASS]** Name present: Orbit
- **[WARNING]** No 192x192 icon — A 192px icon is required for PWA installation.
- **[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 — 45/100)

*Theme color only*

- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[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)

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

*Title: 16 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 16 characters — consider expanding
- **[INFO]** Meta description is only 53 characters — too short to be informative
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

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

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

### Content Depth (F — 25/100)

*60 words, Easy*

- **[WARNING]** Page has 60 words — thin content — Most well-ranking pages have 300+ words of substantive content.
- **[INFO]** Text-to-HTML ratio is 1% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Easy (grade 6)
- **[WARNING]** Thin content — only 60 words

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

*No links*

- **[PASS]** No links found on this page
- **[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 (C — 70/100)

*Sitemap exists but no <lastmod> entries*

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

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

*No sitemap-vs-robots conflicts detected*

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

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

*Sitemap structure / size look healthy (4 URLs, 297 bytes)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*0.20g CO2 per view*

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

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

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Cloudflare: 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)

*89% cached*

- **[PASS]** 89% reduction on repeat visits — Returning visitors download only 94 KB (vs 886 KB first visit). 60 of 62 resources are served from browser cache, saving 0.18g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.02g CO2 (first visit: 0.20g)

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

*10th percentile*

- **[PASS]** 0.20g 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)

*88% efficient*

- **[INFO]** Transfer efficiency: 88% — An estimated 103 KB (12%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 103 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/002feaa8-c70a-4655-a476-2436c153ad20*