# BeaverCheck Audit Report — https://www.tradingtitans007.sbs

**Date:** November 5, 2026  
**URL:** https://www.tradingtitans007.sbs  
**Overall Grade:** C (79/100)  
**Report:** https://beavercheck.com/results/e4ce46f8-bd37-4705-9581-bc9d49cd04f4

## 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. **[WARNING]** 122 third-party resources (56% of weight) — Performance > Page Weight Inventory
4. **[WARNING]** 233 HTTP requests — consider bundling or reducing — Performance > Page Weight Budget
5. **[WARNING]** Images are 1.9 MB — compress or use modern formats — Performance > Page Weight Budget

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 43 |
| Accessibility | 91 |
| Best Practices | 92 |
| SEO | 100 |

---

## Security

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

*10 of 10 headers properly configured*

- **[PASS]** HSTS is enabled with preload
- **[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
- **[PASS]** Cross-Origin-Opener-Policy is properly configured
- **[PASS]** Cross-Origin-Embedder-Policy is set
- **[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 (D — 50/100)

*6 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
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[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 63 days)
- **[PASS]** Certificate chain has 4 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 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

### CSP Inline-Style Readiness (A+ — 100/100)

*No inline style attributes -- strict CSP is feasible*

- **[PASS]** No inline style attributes detected

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

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

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

*no DMARC, no SPF*

- **[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]** 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 (A — 85/100)

*5 directives, 0 missing*

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

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (F — 15/100)

*3.4 MB transferred, 233 requests*

- **[WARNING]** Page weighs 6.3 MB (3.4 MB transferred)
- **[WARNING]** Images are 1.9 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 984 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 233 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.71 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 (1.9 MiB of 3.4 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

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

*All text resources are compressed*

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

### Image Optimization (B — 70/100)

*162 images, 0 KB saveable*

- **[WARNING]** https://i.ibb.co/5XqpffZJ/logo0101-3-2.webp is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*63978ms total JS execution*

- **[WARNING]** https://www.tradingtitans007.sbs/assets/index-Q3XH...: 50153ms CPU time
- **[WARNING]** https://www.tradingtitans007.sbs/assets/HomePage--...: 6364ms CPU time
- **[WARNING]** Unattributable: 2833ms CPU time
- **[WARNING]** https://www.tradingtitans007.sbs/: 1859ms CPU time
- **[WARNING]** https://www.tradingtitans007.sbs/assets/proxy-CMC9...: 1833ms CPU time
- **[INFO]** Third-party scripts: 936ms (1% of total)

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

*3 fonts (79 KB)*

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

### JS Bundles (D — 40/100)

*54 scripts, 490 KB unused*

- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-179...: 114 KB unused (75%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-ZSDV...: 72 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=AW-179...: 60 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.tradingtitans007.sbs/assets/index-I6OK...: 56 KB unused (90%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.tradingtitans007.sbs/assets/index-Q3XH...: 51 KB unused (44%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 490 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.

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

*3 server-response signal(s) detected*

- **[PASS]** `Cache-Status` header present (RFC 9211): "Netlify Edge"; fwd=miss; fwd-status=200; stored — The page returns a `Cache-Status` header -- the standardized way for CDNs and caches to communicate per-hop cache state to debugging tools. Format: `Cache-Status: cdn-name; hit; ttl=300` (or `; fwd=miss` / `; fwd=stale`). Standard alternative to vendor-specific `X-Cache` patterns each CDN had historically. Cloudflare, Fastly, and Akamai all support emitting it.
- **[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).
- **[PASS]** `ETag` present -- conditional GET supported

### Page Weight Inventory (F — 35/100)

*233 resources · 3.4 MB · 490 KB savings available*

- **[WARNING]** Page weight 3.4 MB exceeds 1 MB target by 2.4 MB
- **[INFO]** ~490 KB of savings available
- **[WARNING]** 122 third-party resources (56% of weight)
- **[INFO]** 1 resources over 200KB

---

## Infrastructure

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

*1 A records, 92 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
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[PASS]** 2 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[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: 92 ms

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

*No subdomain takeover risk detected*

- **[PASS]** CNAME does not point at a known takeover-able service

### 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 75.2.60.5 does not match any cert SAN: acd89244c803f7181.awsglobalaccelerator.com — 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 — 90/100)

*Mean 61ms across 3 resolvers (spread 42ms)*

- **[PASS]** Google: 37ms
- **[PASS]** Cloudflare: 67ms
- **[PASS]** Quad9: 79ms

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

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 138 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: www)
- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*tradingtitans007.sbs — via HOSTINGER operations, UAB, 1 years, 9 months old, hosted on AWS*

- **[PASS]** Domain registered until Feb 11, 2027 (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: HOSTINGER operations, UAB
- **[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: 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 in the page — No link matching the privacy-policy vocabulary was found in the rendered page. The common privacy-policy paths were not probed for this scan, so this is an unconfirmed absence and is excluded from the regulatory-risk estimate.
- **[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. 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: . 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 (A — 85/100)

*Netlify ("Netlify Edge"; fwd=miss; fwd-status=200; stored)*

- **[PASS]** Document is served via Netlify CDN
- **[INFO]** CDN cache status: "Netlify Edge"; fwd=miss; fwd-status=200; stored

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

*Health endpoint at https://www.tradingtitans007.sbs/api/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://www.tradingtitans007.sbs/api/health

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

*Cache state: fresh (Age=0)*

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

---

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

*6 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]** SVG favicon detected — scales perfectly to any size
- **[PASS]** Multiple icon sizes detected

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

*PWA-ready*

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

*0.80g CO2 per view*

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

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

*Green (cdn)*

- **[PASS]** Netlify CDN uses renewable energy — Since most traffic is served through the CDN, the majority of data transfer energy is renewable.
- **[INFO]** Netlify: Hosted on AWS/Google Cloud with renewable energy matching
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 4 KB (vs 3480 KB first visit). 232 of 233 resources are served from browser cache, saving 0.80g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.80g)

### Carbon Budget (D — 50/100)

*55th percentile*

- **[WARNING]** 0.80g CO2 — above the median website (0.60g) — Heavier than an estimated 45% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 55th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

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

*86% efficient*

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

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/e4ce46f8-bd37-4705-9581-bc9d49cd04f4*