# BeaverCheck Audit Report — https://Www.donaubad.de

**Date:** May 10, 2026  
**URL:** https://Www.donaubad.de  
**Overall Grade:** B (82/100)  
**Report:** https://beavercheck.com/results/b224933a-4ae5-4ac2-8f69-d1892ba8e0fd

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
3. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality
4. **[CRITICAL]** 7 link(s) with no accessible text — Accessibility > Link & Button Quality
5. **[CRITICAL]** No H1 heading found — Accessibility > Heading Hierarchy

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 46 |
| Accessibility | 92 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*2 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured
- **[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.
- **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
- **[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 77 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: 9f9914771d249e5b-CDG

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

*119 inline style attribute(s) detected*

- **[WARNING]** 119 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. 119 inline style(s) is high. Affected element types include: html, div, nav, span, svg. 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)

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

- **[WARNING]** SRI adoption: 0/7 third-party resources protected (0%) — Of 7 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://cloud.ccm19.de/app.js?apiKey=b0d87f14718336d7e766981ccbd1e6d1a0ec9ddfdd41013f
  - https://cloud.ccm19.de/app.css?apiKey=b0d87f14718336d7e766981ccbd1e6d1a0ec9ddfdd41013f&domain=64b01dc1cd05a6439f01e662&gen=2&theme=64b01dc1cd05a6439f01e66f&v=1778171400
  - https://cloud.ccm19.de/plugins/Ccm19ScriptPlaceholder/module.js?apiKey=b0d87f14718336d7e766981ccbd1e6d1a0ec9ddfdd41013f&domain=64b01dc1cd05a6439f01e662&gen=2&theme=64b01dc1cd05a6439f01e66f&lang=de_DE&v=1778171400
  - https://static.elfsight.com/platform/platform.js
  - https://cdn.eye-able.com/configs/www.donaubad.de.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)

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

- **[PASS]** No source maps accessible across 6 probed candidate(s)

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

*No software-version disclosures in HTML*

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

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

*No redirect-shaped query parameters in DOM links*

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

### Auth Security (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 7 external resources have SRI*

- **[WARNING]** External script from cloud.ccm19.de lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cloud.ccm19.de lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cloud.ccm19.de lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.elfsight.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.eye-able.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.eye-able.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from translate-cdn.eye-able.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

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

### Email Security (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 — 67/100)

*1.6 MB transferred, 43 requests*

- **[INFO]** Page weighs 4.6 MB (1.6 MB transferred)
- **[WARNING]** JavaScript is 831 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[PASS]** 43 HTTP requests
- **[INFO]** Estimated 0.34 g CO2 per page load

### Third-Party Impact (A — 85/100)

*39% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 39% of page weight (657.6 KiB of 1.6 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

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

*All text resources are compressed*

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

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

*12 images, 0 KB saveable*

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

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

*2109ms total JS execution*

- **[WARNING]** https://www.donaubad.de/de: 523ms CPU time
- **[WARNING]** https://translate-cdn.eye-able.com/eye-able-transl...: 355ms CPU time
- **[WARNING]** https://www.donaubad.de/build/app.002717c6.js: 336ms CPU time
- **[WARNING]** https://www.donaubad.de/build/400.56e391c9.js: 297ms CPU time
- **[INFO]** https://cloud.ccm19.de/app.js?apiKey=b0d87f1471833...: 221ms CPU time
- **[INFO]** Third-party scripts: 952ms (45% of total)

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

*3 fonts (87 KB)*

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

### JS Bundles (C — 60/100)

*15 scripts, 254 KB unused*

- **[WARNING]** https://cdn.eye-able.com/public/js/eyeAble.js: 102 KB unused (71%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.donaubad.de/build/73.fe332c54.js: 93 KB unused (96%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.donaubad.de/build/400.56e391c9.js: 59 KB unused (61%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 254 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)

*2 hints, 0 missing preconnects*

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

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

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

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

*No Server-Timing header found*

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

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

*1 server-response signal(s) detected*

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

*43 resources · 1.6 MB · 254 KB savings available*

- **[WARNING]** Page weight 1.6 MB exceeds 1 MB target by 654 KB
- **[INFO]** ~254 KB of savings available
- **[INFO]** 21 third-party resources (39% of weight)
- **[INFO]** 1 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


### JavaScript Blocking (A+ — 100/100)

*No render-blocking JS or document.write usage detected*

- **[PASS]** No JavaScript blocking issues detected

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

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (A — 95/100)

*142 links checked, 141 healthy, 1 broken*

- **[WARNING]** 141 of 142 links are healthy
- **[WARNING]** Broken link: https://core.service.elfsight.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 (F — 0/100)

*No Open Graph tags found — social sharing previews will be generic.*

- **[WARNING]** No Open Graph meta tags found — Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

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

*No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)*

- **[PASS]** No OG image / Twitter card to evaluate

### Structured Data (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

### Image Optimization (F — 40/100)

*6 issues found across 66 images*

- **[WARNING]** 4 images significantly larger than display size — Resizing to display dimensions could save approximately 287 KB.
- **[WARNING]** 1 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 61 of 66 images use legacy formats
- **[WARNING]** 10 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[INFO]** 5 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://www.donaubad.de/Gesamtanlage/1427/image-thumb__1427__hero_banner_image/Donaubad%20Juni%202024%2002~-~media--ab6a433c--query.avif, https://www.donaubad.de/Erlebnisbad/Rutschen/RAINBOW%20RIVER/Bildergalerie/657/image-thumb__657__card_image_card_carousel__variant_2/2023-11-24_Donaubad-Ulm_Lars-Maurer-JU8A1951-Enhanced-NR_Farbkorrektur.avif, https://www.donaubad.de/Sauna/Menschenbilder%202/364/image-thumb__364__card_image_card_carousel__variant_2/2023-03-06_Donaubad-Ulm-0S3A9486.avif (+2 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)

*3 A records, 44 ms lookup*

- **[PASS]** Resolves to 3 IPv4 address(es)
- **[PASS]** Has 3 IPv6 (AAAA) record(s)
- **[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: 44 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/6 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 104.26.3.194: lookup 104.26.3.194: 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 172.67.71.190: lookup 172.67.71.190: 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.26.2.194: lookup 104.26.2.194: 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 2606:4700:20::681a:2c2: lookup 2606:4700:20::681a:2c2: 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 2606:4700:20::681a:3c2: lookup 2606:4700:20::681a:3c2: 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 2606:4700:20::ac43:47be: lookup 2606:4700:20::ac43:47be: 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 — 90/100)

*Mean 47ms across 3 resolvers (spread 67ms)*

- **[PASS]** Cloudflare: 23ms
- **[PASS]** Google: 30ms
- **[PASS]** Quad9: 90ms

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

*1 redirect(s), 313 ms total*

- **[PASS]** Single redirect
- **[INFO]** Uses 302 (temporary) redirect — If permanent, use 301 instead.

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

*IPv6 reachable (16 ms)*

- **[PASS]** IPv6 is configured and reachable at 2606:4700:20::681a:2c2, 2606:4700:20::681a:3c2, 2606:4700:20::ac43:47be

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 73 URLs*

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

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

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

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

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

*donaubad.de*

- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

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

*No testable criteria*


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

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[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+ — 100/100)

*Lang attribute + Content-Language header*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[PASS]** Content-Language header is set
- **[PASS]** Language signals are consistent

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

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

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

*No additional i18n signals detected*

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

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

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

### Accessibility Statement (A — 85/100)

*Statement found, no conformance level*

- **[INFO]** Accessibility statement found but lacks WCAG conformance level — Mature accessibility statements declare a target conformance level (e.g., WCAG 2.1 AA). Without a stated level, users and reviewers cannot tell what the statement actually commits to.

### 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 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: this scan does not fetch the privacy policy sub-page; if Article 13 disclosures live there, they are not visible to this check.

### Third-Party Trackers (A+ — 95/100)

*1 trackers detected*

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

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

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

- **[INFO]** 1 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 (B — 70/100)

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /de/rechtliche-hinweise/datenschutz, linked from footer.
- **[PASS]** Terms of Service detected — Found at /de/rechtliche-hinweise/agb, linked from footer.
- **[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.
- **[PASS]** Accessibility Statement detected — Found at /de/rechtliche-hinweise/Barrierefreiheit, linked from footer.
- **[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)

*© 2026 Donaubad Ulm / Neu-Ulm GmbH Wir nutzen Cookies und*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 Donaubad Ulm / Neu-Ulm GmbH Wir nutzen Cookies und
- **[PASS]** Copyright holder: Donaubad Ulm / Neu-Ulm GmbH Wir nutzen Cookies und

### 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 language detected: de; European TLD detected: .de; 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 (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 (A — 85/100)

*Cloudflare (DYNAMIC)*

- **[PASS]** Site is served via Cloudflare CDN (edge: CDG)
- **[INFO]** CDN cache status: DYNAMIC

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

*no-cache, private*

- **[PASS]** Cache-Control header is set
- **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

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

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[PASS]** HSTS enabled (includeSubDomains, preload)
- **[PASS]** HSTS preload enabled
- **[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 (A+ — 100/100)

*Cache state: DYNAMIC*

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

---

## Accessibility

### Landmark Structure (B — 75/100)

*6 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 1 <nav> landmark(s) 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 (F — 25/100)

*40 headings, 3 skip(s)*

- **[CRITICAL]** No H1 heading found — Every page should have one H1 that describes the page content.
- **[WARNING]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** 1 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

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

- **[INFO]** 8 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 66 images OK*

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

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

*All 5 controls labeled*

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

### Link & Button Quality (D — 48/100)

*8 issue(s) across 139 links and 13 buttons*

- **[CRITICAL]** 7 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 12 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 1 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 120 link(s) with descriptive text

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

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

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

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

*5 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 "de"*

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

### Tabindex Anti-Patterns (D — 40/100)

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

- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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.)
- **[INFO]** tabindex="-1" on naturally-focusable <a> — 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+ — 100/100)

*No iframes on this page*

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

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

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

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

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

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

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

---

## UX

### 404 Error Page (F — 35/100)

*HTTP 404, bare page*

- **[PASS]** Correct 404 status code returned
- **[WARNING]** Bare server default 404 page — The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

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

*6 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

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

*Valid manifest*

- **[PASS]** Name present: Donaubad
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*No navigation patterns*

- **[PASS]** 1 navigation landmark(s) detected
- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

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

*1 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

---

## SEO

### Canonical URL (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 (A — 85/100)

*Title: 10 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 10 characters — consider expanding
- **[INFO]** Meta description is 175 characters — truncated on mobile (~160 char limit)

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

*3850 words, Difficult*

- **[PASS]** Page has 3850 words — good depth for search engines
- **[INFO]** Reading level: Difficult (grade 11)

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

*124 internal, 15 external*

- **[PASS]** 124 internal links (89%)
- **[PASS]** 95% of links use descriptive anchor text
- **[INFO]** 124 internal / 15 external links

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

*66 images, 56 descriptive filenames*

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

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

- **[PASS]** Sitemap actively maintained — newest lastmod: 1 days ago

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

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

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

*No markup-quality issues detected*

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

---

## Sustainability

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

*0.39g CO2 per view*

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

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

*Green (cdn)*

- **[PASS]** Cloudflare CDN uses renewable energy — Since most traffic is served through the CDN, the majority of data transfer energy is renewable.
- **[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)

*96% cached*

- **[PASS]** 96% reduction on repeat visits — Returning visitors download only 67 KB (vs 1677 KB first visit). 42 of 43 resources are served from browser cache, saving 0.37g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.02g CO2 (first visit: 0.39g)

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

*28th percentile*

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

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

*85% efficient*

- **[INFO]** Transfer efficiency: 85% — An estimated 253 KB (15%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 253 KB of unused JavaScript. This wasted data produces 0.06g 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/b224933a-4ae5-4ac2-8f69-d1892ba8e0fd*