# BeaverCheck Audit Report — https://www.gambling.com/be

**Date:** August 27, 2026  
**URL:** https://www.gambling.com/be  
**Overall Grade:** B (81/100)  
**Report:** https://beavercheck.com/results/a0cb00a3-7156-4134-98d2-3fcb3d92fb37

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** Cookie 'cf.bot_management.js.detection.passed' is missing the Secure flag — Security > Cookie Security
3. **[CRITICAL]** Cookie 'cf.bot_management.js.detection.score' is missing the Secure flag — Security > Cookie Security
4. **[CRITICAL]** Cookie 'op_list_region_be' is missing the Secure flag — Security > Cookie Security
5. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 32 |
| Accessibility | 86 |
| Best Practices | 81 |
| SEO | 100 |

---

## Security

### Security Headers (D — 40/100)

*4 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured (consider adding preload)
- **[PASS]** X-Content-Type-Options is properly configured
- **[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, 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 77 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (D — 40/100)

*3 cookies analyzed, 0 checks passed*

- **[CRITICAL]** Cookie 'op_list_region_be' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'op_list_region_be' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'op_list_region_be' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[CRITICAL]** Cookie 'cf.bot_management.js.detection.passed' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'cf.bot_management.js.detection.passed' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'cf.bot_management.js.detection.passed' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
- **[CRITICAL]** Cookie 'cf.bot_management.js.detection.score' is missing the Secure flag — Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
- **[WARNING]** Cookie 'cf.bot_management.js.detection.score' is missing the HttpOnly flag — Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
- **[WARNING]** Cookie 'cf.bot_management.js.detection.score' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

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

*All 3 cookie(s) pass hygiene checks*

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

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a31a2f33fa57c50d-GRU

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

*10 of 13 new-tab link(s) missing rel=noopener*

- **[WARNING]** 10 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

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

*17 inline style attribute(s) detected*

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

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

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

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

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

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

- **[WARNING]** SRI adoption: 1/17 third-party resources protected (5%) — Of 17 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (5%) 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://www.googletagmanager.com/gtm.js?id=GTM-TJ32CD6&gtg_health=1
  - https://uk1-api.eng.bloomreach.com/js/exponea.min.js
  - https://gut.gambling.com/lib/gutloader.js?id=TJ32CD6
  - https://95632935.adoric-om.com/adoric.js
  - https://objects2.kaxmedia.com/gambling.com-lambda/assets-0e8d9783388fded54a455901de88c2f7/build/assets/google-page-speed-insights-helpers-DG1hrHRy.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 (D — 40/100)

*1 of 17 external resources have SRI*

- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from uk1-api.eng.bloomreach.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from gut.gambling.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from 95632935.adoric-om.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from static.adoric.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from objects2.kaxmedia.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from static.cloudflareinsights.com has SRI protection

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

*2.3 MB transferred, 208 requests*

- **[INFO]** Page weighs 9.3 MB (2.3 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.
- **[WARNING]** 208 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.48 g CO2 per page load

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

*73% third-party, 0 ms blocking*

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

*51 images, 0 KB saveable*

- **[WARNING]** https://objects.kaxmedia.com/auto/o/285909/9c6fedf... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/175826/f98238b... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/236143/5e4b386... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/249427/c652fb7... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/217655/0f0d093... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/236065/f18540d... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://objects.kaxmedia.com/auto/o/218223/a1c0eb9... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*15432ms total JS execution*

- **[WARNING]** https://www.gambling.com/br: 5920ms CPU time
- **[WARNING]** Unattributable: 2153ms CPU time
- **[WARNING]** https://gut.gambling.com/lib/gutloader.js?id=TJ32C...: 1786ms CPU time
- **[WARNING]** https://www.gambling.com/be: 1256ms CPU time
- **[WARNING]** https://www.gambling.com/cdn-cgi/challenge-platfor...: 1153ms CPU time
- **[INFO]** Third-party scripts: 4950ms (32% of total)

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

*2 fonts (61 KB)*

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

### JS Bundles (F — 20/100)

*94 scripts, 629 KB unused*

- **[WARNING]** https://objects2.kaxmedia.com/gambling.com-lambda/...: 61 KB unused (80%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://objects2.kaxmedia.com/gambling.com-lambda/...: 60 KB unused (80%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://objects2.kaxmedia.com/gambling.com-lambda/...: 59 KB unused (76%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://objects2.kaxmedia.com/gambling.com-lambda/...: 59 KB unused (77%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://objects2.kaxmedia.com/gambling.com-lambda/...: 57 KB unused (67%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 629 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)

*11 hints, 0 missing preconnects*

- **[PASS]** Page uses 11 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 (A+ — 100/100)

*Main response uses brotli*

- **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

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

*3 Server-Timing entries advertised*

- **[PASS]** Server-Timing header advertises 3 timing entries

### Server Response Intelligence (A — 87/100)

*2 server-response signal(s) detected*

- **[WARNING]** Compressed response missing `Vary` header — The page is served with `Content-Encoding: br` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.
- **[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 (F — 30/100)

*208 resources · 2.3 MB · 629 KB savings available*

- **[WARNING]** Page weight 2.3 MB exceeds 1 MB target by 1.3 MB
- **[INFO]** ~629 KB of savings available
- **[WARNING]** 170 third-party resources (73% of weight)

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

*2 JS blocking issue(s) detected*

- **[WARNING]** 1 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 15.4 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+ — 100/100)

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (F — 59/100)

*200 links checked, 190 healthy, 7 broken*

- **[CRITICAL]** 190 of 200 links are healthy
- **[WARNING]** Broken link: https://gut.gambling.com — Found in <link href>. Returns HTTP 400.
- **[WARNING]** Broken link: https://www.googletagmanager.com — Found in <link href>. Returns HTTP 404.
- **[CRITICAL]** Broken link: https://www.gambling.com/terms — Found in <a href>. Returns HTTP 404.
- **[INFO]** Long redirect chain: https://www.gambling.com/go/be/casino1/offer/83864 (3 hops)
- **[CRITICAL]** Broken link: https://www.gambling.com/go/be/bwin/offer/68906 — Found in <a href>. Returns HTTP 403.
- **[INFO]** Long redirect chain: https://www.gambling.com/go/be/777-be/offer/64719 (3 hops)
- **[CRITICAL]** Broken link: https://www.gambling.com/go/be/circus/offer/64710 — Found in <a href>. Returns HTTP 403.
- **[INFO]** Long redirect chain: https://www.gambling.com/go/be/loco-casino/offe... (3 hops)
- **[CRITICAL]** Broken link: https://www.gamingcommission.be/ — Found in <a href>. Get "https://www.gamingcommission.be/": EOF
- **[CRITICAL]** Broken link: https://www.instagram.com/gamblingdotcom/ — Found in <a href>. Returns HTTP 429.

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

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

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

### Open Graph (B — 85/100)

*Open Graph tags are partially configured — some improvements recommended.*

- **[CRITICAL]** og:image is not reachable — The og:image URL could not be fetched. Social platforms won't be able to display it.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.

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

*OG image dimensions and Twitter card configuration look healthy*

- **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

### Structured Data (C — 75/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.
- **[WARNING]** Missing required property "name" for Organization — The "name" property is required for the Organization schema type.
- **[INFO]** Missing recommended property "url" for Organization — Adding "url" can improve how search engines display your content.
- **[INFO]** Missing recommended property "logo" for Organization — Adding "logo" can improve how search engines display your content.
- **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content.
- **[PASS]** 2 JSON-LD blocks found

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

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

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

FAQPage, Organization, WebPage, WebSite

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

*5 issues found across 193 images*

- **[WARNING]** 5 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 121 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 37 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 55 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[INFO]** 6 image(s) wider than 400px without srcset (no responsive serving) — These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://www.gambling.com/cdn-cgi/image/w=420,format=webp/https://objects.kaxmedia.com/genesis/ballon-dor-2026-trofee-be-nl.jpg?v=e717e83c7a18a19e3174d46f57d50ab08a873274, https://www.gambling.com/cdn-cgi/image/w=420,format=webp/https://objects.kaxmedia.com/genesis/world-cup-trophy.png?v=4e4de7ce5443f96794cd380960c60e0149b2eed1, https://www.gambling.com/cdn-cgi/image/w=420,format=webp/https://objects.kaxmedia.com/genesis/vuelta-2026-peloton-hero-benl.jpg?v=433add70845f6147c76169fa212484324391d332 (+3 more).

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

*No autoplay media on the page*

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

---

## Infrastructure

### DNS Records (A — 90/100)

*2 A records, 17 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[INFO]** No IPv6 (AAAA) records
- **[INFO]** No NS records found
- **[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: 17 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 (C — 60/100)

*0/2 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 104.18.27.235: lookup 104.18.27.235: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 104.18.26.235: lookup 104.18.26.235: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (A+ — 100/100)

*Mean 2ms across 3 resolvers (spread 3ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 2ms
- **[PASS]** Google: 4ms

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

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 49 entries
- **[PASS]** Sitemap index with 49 child sitemaps
- **[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)

*gambling.com — via SafeNames Ltd., 30 years old, hosted on Cloudflare*

- **[PASS]** Domain registered until Oct 8, 2029 (3 years, 1 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: SafeNames Ltd.
- **[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 (B — 70/100)

*CookieYes detected, privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[PASS]** Consent banner detected (CookieYes)
- **[WARNING]** 3 non-essential cookie(s) set BEFORE consent (CMP misconfigured) — A consent banner is present but non-essential cookies were already set on the initial response, before the banner could be acknowledged. Configure the CMP to gate tag firing on user consent. Unrecognized (treated as non-essential): op_list_region_be, cf.bot_management.js.detection.passed, cf.bot_management.js.detection.score
- **[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)

*1 known tracker(s) detected*

- **[PASS]** 1 known tracker(s) detected — Inventory of trackers loaded by the page (matched against a curated SDK URL registry):

tag-manager: Google Tag Manager

Each entry maps a script URL pattern to a known vendor SDK. This is purely informational -- consent posture / pre-consent firing is graded by the consent analyzer.

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

*All 26 hreflang tag(s) look correct*

- **[PASS]** All 26 hreflang tag(s) look correct

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

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

*Font sizes and tap targets checked*


### Viewport Configuration (A+ — 100/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

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

*No accessibility statement detected*

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

### GDPR Article 13 Disclosures (A+ — 100/100)

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

- **[PASS]** GDPR Article 13 disclosure coverage: 8 / 8 categories — All 8 GDPR Article 13 disclosure categories matched (homepage + linked privacy policy).

### Third-Party Trackers (B — 75/100)

*3 trackers detected*

- **[INFO]** 3 third-party trackers detected — Found 1 analytics, 0 advertising, 0 marketing, 1 tag manager, 1 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 session-replay tool(s) detected (Microsoft Clarity) — Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.

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

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

- **[INFO]** 3 cookie(s) could not be classified
- **[INFO]** 3 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 SameSite=None cookies -- no cross-site travel surface*

- **[PASS]** No cookies opted in to cross-site travel (SameSite=None)

### Beacon Tracking (sendBeacon) (B — 90/100)

*1 sendBeacon call site(s) in inline scripts*

- **[INFO]** 1 navigator.sendBeacon call site(s) in inline scripts — navigator.sendBeacon() fires fire-and-forget POSTs in the background after page-unload -- typically used for last-second analytics (read-time, scroll depth, exit-intent). Ad-blockers' XHR/fetch interception often misses them (different API path); DevTools shows beacon requests typed as "ping" instead of "fetch", which is easy to overlook in privacy reviews. Audit each call site: what data is being sent? Is the recipient disclosed in the privacy policy? Is the call gated behind cookie-banner consent? Does the user have a way to opt out of the page-unload tracking specifically (separate from in-session analytics)? Detection is limited to inline scripts -- beacons in external SDKs aren't visible to this static scan.

---

## Legal

### Legal Page Ecosystem (C — 55/100)

*2 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacy-policy.
- **[PASS]** Terms of Service detected — Found at /terms.
- **[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 (A+ — 100/100)

*© 2006-2026 Gambling*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2006-2026 Gambling
- **[PASS]** Copyright holder: Gambling

### 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: .be; Text mentions: gdpr; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### 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: Tag Management (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Tag Manager (Tag Management) — Detected via script URL. Typically collects: Orchestrates other tracking scripts, Page views. Privacy policy: https://policies.google.com/privacy. 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]** Site is served via Cloudflare CDN (edge: GRU)

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

*15 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 3 <nav> landmark(s) found
- **[WARNING]** 2 of 3 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[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 — 85/100)

*24 headings, 1 skip(s)*

- **[PASS]** Single H1 present
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

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

*1 heading-text-quality issue(s) detected*

- **[INFO]** 1 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

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

*All 192 images OK*

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

### Form Accessibility (C — 61/100)

*4 of 6 controls have issues*

- **[CRITICAL]** 1 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[WARNING]** 3 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 2 control(s) properly labeled

### Link & Button Quality (C — 68/100)

*3 issue(s) across 268 links and 28 buttons*

- **[WARNING]** 24 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 3 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 244 link(s) with descriptive text

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

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

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

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

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

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

### Mobile Keyboard & Autofill (C — 75/100)

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

- **[WARNING]** 3 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, search.

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

*Lang attribute set to "nl-BE"*

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

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

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

- **[INFO]** tabindex="-1" on naturally-focusable <input id="super_secret_username"> — 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 (B — 80/100)

*2/2 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.
- **[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)

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

- **[WARNING]** 8 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 5 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)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page

### Favicon & Branding (C — 55/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 (D — 40/100)

*Not found*

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

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

*No PWA depth issues detected*

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

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

*Dark mode detected*

- **[PASS]** prefers-color-scheme CSS detected in inline styles
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

*No print styles*

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

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

*No navigation patterns*

- **[PASS]** 3 navigation landmark(s) detected
- **[PASS]** Hamburger menu detected (responsive design)
- **[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+ — 97/100)

*1 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

---

## SEO

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

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200

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

*Title: 7 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 7 characters — consider expanding
- **[INFO]** Meta description is 174 characters — truncated on mobile (~160 char limit)
- **[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 (A — 85/100)

*4036 words, Difficult*

- **[PASS]** Page has 4036 words — good depth for search engines
- **[INFO]** Text-to-HTML ratio is 2% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Difficult (grade 13)

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

*238 internal, 30 external*

- **[PASS]** 238 internal links (89%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** Page has 268 links — consider reducing
- **[INFO]** 238 internal / 30 external links

### Image SEO (B — 80/100)

*192 images, 5 descriptive filenames*

- **[WARNING]** 97% of images have non-descriptive filenames — Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.

### Hreflang

*0 hreflang tags*


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

*No hreflang tags on the page*

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

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

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

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

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

*Sitemap updated within 90 days (49/49 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: today

### 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 (49 URLs, 7 KB)*

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (B — 70/100)

*0.54g CO2 per view*

- **[INFO]** 0.54g CO2 per page view — This page transfers 2.3 MB, producing an estimated 0.54g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.01g, network 0.11g, end-user device 0.42g.
- **[INFO]** At 10,000 monthly views: 65.2 kg CO2/year — With 10,000 page views per month, this page would generate approximately 65.2 kg of CO2 annually — equivalent to charging 8153 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)

*84% cached*

- **[PASS]** 84% reduction on repeat visits — Returning visitors download only 366 KB (vs 2351 KB first visit). 206 of 208 resources are served from browser cache, saving 0.46g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.08g CO2 (first visit: 0.54g)

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

*44th percentile*

- **[INFO]** 0.54g CO2 — below the median website (0.60g) — Better than an estimated 56% of websites, but above the sustainability target of 0.50g. Reducing page weight would help reach the target.
- **[INFO]** Estimated 44th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (C — 60/100)

*73% efficient*

- **[WARNING]** Transfer efficiency: 73% — An estimated 628 KB (27%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 628 KB of unused JavaScript. This wasted data produces 0.15g 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/a0cb00a3-7156-4134-98d2-3fcb3d92fb37*