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

**Date:** August 11, 2026  
**URL:** https://alexmackxxx.com  
**Overall Grade:** B (81/100)  
**Report:** https://beavercheck.com/results/fe803933-9987-4005-9bc2-ad5a0df81233

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** HSTS header is missing — Security > Security Headers
3. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
4. **[CRITICAL]** No <main> landmark found — Accessibility > Landmark Structure
5. **[WARNING]** 3 `@font-face` rule(s) without `font-display` -- causes FOIT — Performance > CSS Performance Depth

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 37 |
| Accessibility | 90 |
| Best Practices | 77 |
| SEO | 69 |

---

## Security

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

*2 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[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 (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 173 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.

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

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

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

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

*No CSP header -- Trusted Types check is N/A*

- **[PASS]** No CSP header found -- Trusted Types check is N/A

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

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

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

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

*HTTP status is non-2xx -- soft-404 check is N/A*

- **[PASS]** HTTP status is non-2xx -- soft-404 check is N/A

### 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/59 third-party resources)*

- **[WARNING]** SRI adoption: 0/59 third-party resources protected (0%) — Of 59 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 5 examples):
  - https://sdk.snapkit.com/js/v1/create.js
  - https://assets.production.linktr.ee/profiles/_next/static/native-bridge-bootstrap.js
  - https://assets.production.linktr.ee/consent-scripts/geo-consent.js
  - https://api.consentjs.datagrail.io/b8f6c3bf-2519-4023-963a-974547789e46/bdebe460-46f3-470f-8bb7-09929c22ee50/consent-loader.js
  - https://edge.browser-fp.production.linktr.ee/script.js

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

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

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

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

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

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

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

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

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

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

*No risky subdomain names in certificate SANs*

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

---

## Advanced Security

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

*0 of 59 external resources have SRI*

- **[WARNING]** External script from sdk.snapkit.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from api.consentjs.datagrail.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from edge.browser-fp.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from api.consentjs.datagrail.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from api.consentjs.datagrail.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from assets.production.linktr.ee 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 (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 (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

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

*No CORS headers*

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

---

## Performance

### Page Weight Budget (C — 66/100)

*1.7 MB transferred, 82 requests*

- **[INFO]** Page weighs 5.2 MB (1.7 MB transferred)
- **[WARNING]** JavaScript is 1.2 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** 82 HTTP requests
- **[INFO]** Estimated 0.35 g CO2 per page load

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

*100% third-party, 0 ms blocking*

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

*8 images, 0 KB saveable*

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

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

*7311ms total JS execution*

- **[WARNING]** https://edge.browser-fp.production.linktr.ee/scrip...: 1410ms CPU time
- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 1336ms CPU time
- **[WARNING]** https://linktr.ee/AlexMackXXX: 1287ms CPU time
- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 1178ms CPU time
- **[WARNING]** Unattributable: 774ms CPU time
- **[WARNING]** Third-party scripts: 6537ms (89% of total)

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

*2 fonts (114 KB)*

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

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

*59 scripts, 312 KB unused*

- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 153 KB unused (73%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 71 KB unused (87%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 37 KB unused (41%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://sdk.snapkit.com/js/v1/create.js: 28 KB unused (56%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://assets.production.linktr.ee/profiles/_next...: 22 KB unused (55%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 312 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)

*7 hints, 0 missing preconnects*

- **[PASS]** Page uses 7 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.

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

*Main response served uncompressed*

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

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

*LCP preload audit not available*

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

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

*No Cache-Control header on main HTML response*

- **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

### 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 (D — 40/100)

*82 resources · 1.7 MB · 312 KB savings available*

- **[WARNING]** Page weight 1.7 MB exceeds 1 MB target by 693 KB
- **[INFO]** ~312 KB of savings available
- **[WARNING]** 81 third-party resources (100% of weight)
- **[INFO]** 2 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 (B — 78/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 4 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
- **[WARNING]** Total JS execution time is 7.3 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

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

*1 CSS depth issue(s) detected*

- **[WARNING]** 3 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright.

---

## Content Quality

### Links (B — 85/100)

*148 links checked, 145 healthy, 3 broken*

- **[WARNING]** 145 of 148 links are healthy
- **[WARNING]** Broken link: https://sdk.snapkit.com/js/v1/create.js — Found in <script src>. Get "https://sdk.snapkit.com/js/v1/create.js": tls: failed to verify certificate: x509: certificate signed by unknown authority
- **[WARNING]** Broken link: https://fonts.googleapis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://fonts.gstatic.com — Found in <link href>. Returns HTTP 404.

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

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

- **[INFO]** og:title is long (68 characters) — Titles over 60 characters may be truncated in social sharing previews.

### Open Graph / Twitter Card Depth (B — 80/100)

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

- **[INFO]** og:image aspect ratio 1.00:1 (600×600) is outside Facebook's recommended ~1.91:1 — Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 600×600 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
- **[WARNING]** Twitter card is `summary_large_image` but OG image is 600×600 (ratio 1.00:1) -- closer to square — `twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (600×600, aspect ratio 1.00:1) are closer to square than wide. Twitter will crop the image to fit the wide format, often badly. Either: (1) provide a wider image (~2:1 ratio recommended; minimum 600×314, optimal 1200×630), or (2) change `twitter:card` to `summary` which uses a square thumbnail crop.

### Structured Data (B — 85/100)

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

- **[WARNING]** Missing or invalid @context in block #1 — The @context should be "https://schema.org" for search engines to recognize the data.
- **[PASS]** Custom type "ProfilePage" — unable to validate specific properties
- **[PASS]** 2 JSON-LD blocks found

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

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

- **[PASS]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

BreadcrumbList, ProfilePage

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (D — 60/100)

*4 issues found across 8 images*

- **[WARNING]** 7 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 8 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 3 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 5 of 8 images use legacy formats

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*2 A records, 15 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[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: 15 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 15.197.225.128 does not match any cert SAN: aec037177372cc6cd.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.
- **[INFO]** PTR for 3.33.251.168 does not match any cert SAN: aec037177372cc6cd.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+ — 100/100)

*Mean 13ms across 3 resolvers (spread 21ms)*

- **[PASS]** Cloudflare: 4ms
- **[PASS]** Quad9: 12ms
- **[PASS]** Google: 25ms

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

*1 redirect(s), 98 ms total*

- **[PASS]** Single redirect
- **[INFO]** Cross-domain redirect detected

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

*no robots.txt, no sitemap*

- **[INFO]** No robots.txt found — robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
- **[INFO]** No sitemap.xml found — A sitemap helps search engines discover and index your pages more efficiently.

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

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

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

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

*alexmackxxx.com — via GoDaddy.com, LLC, 7 years, 6 months old, hosted on AWS*

- **[PASS]** Domain registered until Mar 13, 2030 (3 years, 7 months remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: GoDaddy.com, LLC
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
- **[PASS]** Hosting: AWS

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A+ — 95/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

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

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

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

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

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

*Viewport prevents zooming*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[CRITICAL]** Viewport prevents user zooming — user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision.

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

*2 trackers detected*

- **[INFO]** 2 third-party trackers detected — Found 1 analytics, 0 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.

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

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

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

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

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*1 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://linktr.ee/privacy.
- **[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

*1 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]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .ee; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*0 third-party service(s) detected*

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

### Compliance Badges (B — 70/100)

*1 compliance badge(s) detected*

- **[PASS]** TRUSTe / TrustArc badge detected — Found via body text: 'truste'. Note: the presence of a badge does not verify the certification is current or valid.

---

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

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

### 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 (B — 75/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.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.

### 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 (D — 40/100)

*1 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[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+ — 95/100)

*5 headings*

- **[PASS]** Single H1 present
- **[WARNING]** 1 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

*All 5 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

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

*All 8 images OK*

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

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

*All 1 controls labeled*

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

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

*57 links, 30 buttons — all OK*

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

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

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

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

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

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

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

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

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

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

*Lang attribute set to "en"*

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

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

*0 positive, 1 -1-on-focusable*

- **[INFO]** tabindex="-1" on naturally-focusable <button> — tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

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

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

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

### Tap Target Adequacy (C — 75/100)

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

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

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

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

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

---

## UX

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

*Could not test*

- **[INFO]** 404 page could not be tested — The 404 page check encountered an error. This may be due to a timeout or network issue.

### Favicon & Branding (B — 75/100)

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

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

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: Linktree | The Only Link You'll Ever Need
- **[PASS]** 192x192 icon present
- **[PASS]** Display mode: minimal-ui

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

*1 PWA signal(s) surfaced*

- **[INFO]** Manifest has no maskable icon — Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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

*2 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.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

## SEO

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

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200
- **[INFO]** Canonical points to a different domain

### Meta Tags (A — 85/100)

*Title: 7 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 7 characters — consider expanding
- **[PASS]** Meta description length (93 chars) is optimal
- **[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 (C — 65/100)

*585 words, Very Difficult*

- **[PASS]** Page has 585 words of content
- **[INFO]** Text-to-HTML ratio is 2% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Very Difficult (grade 24)

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

*0 internal, 57 external*

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

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

*8 images, 5 descriptive filenames*

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

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

### Sitemap Freshness (C — 75/100)

*No sitemap.xml found*

- **[INFO]** No sitemap.xml found — Sitemaps help search engines discover and prioritize URLs. Not strictly required for small sites where every page is linked from the homepage, but recommended once a site grows beyond a few dozen URLs.

### Sitemap × Robots Consistency (C — 75/100)

*Sitemap or robots.txt missing -- consistency check skipped*

- **[INFO]** Cross-check skipped (sitemap or robots.txt absent)

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

*No sitemap to evaluate -- depth check is N/A*

- **[PASS]** No sitemap fetched -- depth check skipped

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

*1 markup-quality issue(s) detected*

- **[INFO]** `<meta charset>` declared at byte 3024 -- past the 1024-byte spec window — The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.

---

## Sustainability

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

*0.47g CO2 per view*

- **[PASS]** 0.47g CO2 per page view — This page transfers 1.7 MB, producing an estimated 0.47g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.09g, network 0.08g, end-user device 0.30g.
- **[INFO]** At 10,000 monthly views: 57.0 kg CO2/year — With 10,000 page views per month, this page would generate approximately 57.0 kg of CO2 annually — equivalent to charging 7123 smartphones.

### Green Hosting (D — 40/100)

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*98% cached*

- **[PASS]** 98% reduction on repeat visits — Returning visitors download only 35 KB (vs 1717 KB first visit). 81 of 82 resources are served from browser cache, saving 0.46g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.47g)

### Carbon Budget (B — 70/100)

*37th percentile*

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

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

*82% efficient*

- **[INFO]** Transfer efficiency: 82% — An estimated 311 KB (18%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 311 KB of unused JavaScript. This wasted data produces 0.09g 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/fe803933-9987-4005-9bc2-ad5a0df81233*