# BeaverCheck Audit Report — https://www.party-schlaudt.de

**Date:** August 20, 2026  
**URL:** https://www.party-schlaudt.de  
**Overall Grade:** B (82/100)  
**Report:** https://beavercheck.com/results/ecba7602-79cf-4bdd-b245-2cf3c5820772

## Top Findings

1. **[CRITICAL]** Page weighs 13.6 MB (9.6 MB transferred) — Performance > Page Weight Budget
2. **[CRITICAL]** No <main> landmark found — Accessibility > Landmark Structure
3. **[WARNING]** 105 HTTP requests — consider bundling or reducing — Performance > Page Weight Budget
4. **[WARNING]** 12 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
5. **[WARNING]** 6 `@font-face` rule(s) without `font-display` -- causes FOIT — Performance > CSS Performance Depth

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 38 |
| Accessibility | 98 |
| Best Practices | 100 |
| SEO | 92 |

---

## Security

### Security Headers (C — 55/100)

*5 of 10 headers properly configured*

- **[PASS]** Strict-Transport-Security is properly configured
- **[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.
- **[PASS]** Content-Security-Policy is present
- **[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 not present
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

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

*2 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[WARNING]** default-src directive is missing — default-src provides a fallback for other directives. Set it to restrict default resource loading.
- **[INFO]** No script-src or default-src to check for 'unsafe-inline'
- **[INFO]** No script-src or default-src to check for 'unsafe-eval'
- **[INFO]** No script-src or default-src to check for wildcard
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[PASS]** frame-ancestors directive is set
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

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

*No security.txt file found*

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

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

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

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

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

*1 inline style attribute(s) detected*

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

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

*Trusted Types not enabled*

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- **[WARNING]** SRI adoption: 0/23 third-party resources protected (0%) — Of 23 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://www.paypal.com/sdk/js?client-id=AfslQana4f4CQjHvRBnUc6vBJg5jgJuZFwM-SbrTiGKUAqB7MrxQv3QWFdQ6U1h7ogMDokT1DNBzRxMw&merchant-id=STNGP8K8YHW2N&currency=EUR&locale=de_DE&components=messages,buttons,funding-eligibility,hosted-fields,payment-fields,marks&enable-funding=paylater
  - https://www.google-analytics.com/analytics.js
  - https://www.googletagmanager.com/gtag/js?id=G-T1285RLNE8&cx=c&gtm=4e68i1h1
  - https://cdn02.plentyone.com/s8ix3rhxk064/plugin/69/ceres/css/ceres-icons.css
  - https://cdn02.plentyone.com/s8ix3rhxk064/plugin/69/ceres/css/ceres-base.css?v=1d3f05f0eecca4e3d2969f8da7a1b95a0f5cf293

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

*1 generator tag(s) without version info*

- **[INFO]** 1 generator tag(s) without version info: plentymarkets — Generator tags reveal the CMS / build tool but no version specifics. Attackers can't directly cross-reference CVEs but can probe known weaknesses for the named platform. Removing the tag entirely is preferable; most CMSes have a one-config-flag option to suppress it.

### 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 23 external resources have SRI*

- **[WARNING]** External script from www.paypal.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.google-analytics.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[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 cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pay.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from applepay.cdn-apple.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn02.plentyone.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 (F — 0/100)

*9.6 MB transferred, 105 requests*

- **[CRITICAL]** Page weighs 13.6 MB (9.6 MB transferred)
- **[WARNING]** Images are 8.0 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 1004 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 105 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 2.0 g CO2 per page load

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

*99% third-party, 0 ms blocking*

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

*44 images, 0 KB saveable*

- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.party-schlaudt.de/layout/callisto_3/im... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentymarkets.com/s8ix3rhxk064/front... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentymarkets.com/s8ix3rhxk064/front... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentymarkets.com/s8ix3rhxk064/front... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://payments.amazon.de/gp/widgets/button?selle... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.party-schlaudt.de/layout/callisto_3/im... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/item/imag... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*3005ms total JS execution*

- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/plugin/69...: 890ms CPU time
- **[WARNING]** https://www.party-schlaudt.de/: 779ms CPU time
- **[WARNING]** Unattributable: 635ms CPU time
- **[WARNING]** https://www.paypal.com/sdk/js?client-id=AfslQana4f...: 329ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtag/js?id=UA-108...: 153ms CPU time
- **[WARNING]** Third-party scripts: 1592ms (53% of total)

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

*6 fonts (162 KB)*

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

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

*29 scripts, 388 KB unused*

- **[WARNING]** https://cdn02.plentyone.com/s8ix3rhxk064/plugin/69...: 102 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.paypal.com/sdk/js?client-id=AfslQana4f...: 95 KB unused (60%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.paypal.com/sdk/js?client-id=AfslQana4f...: 95 KB unused (60%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=UA-108...: 66 KB unused (51%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://pay.google.com/gp/p/js/pay.js: 32 KB unused (54%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 388 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*1 hints, 0 missing preconnects*

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

### HTTP/3 (QUIC) (A+ — 100/100)

*HTTP/3 advertised via Alt-Svc*

- **[PASS]** HTTP/3 (QUIC) is supported — First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.

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

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

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

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

*No Server-Timing header found*

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

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

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (D — 40/100)

*105 resources · 9.6 MB · 388 KB savings available*

- **[WARNING]** Page weight 9.6 MB exceeds 1 MB target by 8.6 MB
- **[INFO]** ~388 KB of savings available
- **[WARNING]** 98 third-party resources (99% of weight)
- **[INFO]** 8 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


### JavaScript Blocking (B — 80/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** 12 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.

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

*1 CSS depth issue(s) detected*

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

---

## Content Quality

### Links (A — 90/100)

*200 links checked, 198 healthy, 2 broken*

- **[WARNING]** 198 of 200 links are healthy
- **[WARNING]** Broken link: https://www.googletagmanager.com/gtag/js?id=G-T1285RLNE8&... — Found in <script src>. Returns HTTP 404.
- **[CRITICAL]** Broken link: https://www.party-schlaudt.de/tisch-dekoration/blumen-gir... — Found in <a 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 (C — 75/100)

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

- **[WARNING]** Missing og:description — The og:description tag controls the description in social sharing previews.
- **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews.
- **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

*1 JSON-LD block(s) found — structured data is well configured.*

- **[WARNING]** Missing required property "name" for WebSite — The "name" property is required for the WebSite schema type.
- **[INFO]** Missing recommended property "description" for WebSite — Adding "description" can improve how search engines display your content.

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

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

- **[PASS]** SiteLinks Search Box markup detected — The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
- **[PASS]** 1 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

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

*6 issues found across 15 images*

- **[WARNING]** 2 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 15 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 13 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 14 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]** 1 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.party-schlaudt.de/layout/callisto_3/img/de-pp_plus-logo-quer_mit_PUI_540x60px.png.
- **[INFO]** 1 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://cdn02.plentymarkets.com/s8ix3rhxk064/frontend/Startseite/Slider/Ballons1last.jpg.

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

*No autoplay media on the page*

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

---

## Infrastructure

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

*4 A records, 37 ms lookup*

- **[PASS]** Resolves to 4 IPv4 address(es)
- **[PASS]** Has 8 IPv6 (AAAA) record(s)
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[PASS]** 4 nameserver(s) configured
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[PASS]** DNS resolution time: 37 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

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

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (B — 75/100)

*0/12 IPs match cert SAN*

- **[INFO]** PTR for 13.33.153.24 does not match any cert SAN: server-13-33-153-24.lhr3.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 13.33.153.29 does not match any cert SAN: server-13-33-153-29.lhr3.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 13.33.153.97 does not match any cert SAN: server-13-33-153-97.lhr3.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR for 13.33.153.123 does not match any cert SAN: server-13-33-153-123.lhr3.r.cloudfront.net — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR lookup failed for 2600:9000:2021:2c00:15:fa36:9e80:93a1: lookup 2600:9000:2021:2c00:15:fa36:9e80:93a1: 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 2600:9000:2021:a800:15:fa36:9e80:93a1: lookup 2600:9000:2021:a800:15:fa36:9e80:93a1: 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 2600:9000:2021:a000:15:fa36:9e80:93a1: lookup 2600:9000:2021:a000:15:fa36:9e80:93a1: 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 2600:9000:2021:5400:15:fa36:9e80:93a1: lookup 2600:9000:2021:5400:15:fa36:9e80:93a1: 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 2600:9000:2021:7000:15:fa36:9e80:93a1: lookup 2600:9000:2021:7000:15:fa36:9e80:93a1: 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 2600:9000:2021:7a00:15:fa36:9e80:93a1: lookup 2600:9000:2021:7a00:15:fa36:9e80:93a1: 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 2600:9000:2021:fc00:15:fa36:9e80:93a1: lookup 2600:9000:2021:fc00:15:fa36:9e80:93a1: 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 2600:9000:2021:c200:15:fa36:9e80:93a1: lookup 2600:9000:2021:c200:15:fa36:9e80:93a1: 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 (B — 80/100)

*Mean 119ms across 3 resolvers (spread 77ms)*

- **[PASS]** Google: 91ms
- **[PASS]** Cloudflare: 99ms
- **[PASS]** Quad9: 168ms

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

*No redirects — direct access*

- **[PASS]** No redirects — direct access

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

*IPv6 reachable (25 ms)*

- **[PASS]** IPv6 is configured and reachable at 2600:9000:2021:2c00:15:fa36:9e80:93a1, 2600:9000:2021:a800:15:fa36:9e80:93a1, 2600:9000:2021:a000:15:fa36:9e80:93a1, 2600:9000:2021:5400:15:fa36:9e80:93a1, 2600:9000:2021:7000:15:fa36:9e80:93a1, 2600:9000:2021:7a00:15:fa36:9e80:93a1, 2600:9000:2021:fc00:15:fa36:9e80:93a1, 2600:9000:2021:c200:15:fa36:9e80:93a1

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

*robots.txt present, sitemap with 3 URLs*

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

*party-schlaudt.de — hosted on AWS*

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

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A+ — 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)

*2 known tracker(s) detected*

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

analytics: Google Analytics 4, Google Analytics (UA)

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 2 hreflang tag(s) look correct*

- **[PASS]** All 2 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 (F — 25/100)

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 2 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 2 of 8 categories: Legal basis for processing, Right to lodge a complaint with a supervisory authority. 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, Recipients of personal data. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

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

*2 trackers detected*

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

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

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

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

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*3 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /privacy-policy, linked from footer.
- **[PASS]** Terms of Service detected — Found at /gtc, 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.
- **[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.
- **[PASS]** Refund / Returns Policy detected — Found at /cancellation-rights, linked from footer.
- **[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)

*Copyright 2026 | Alle Rechte vorbehalten*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: Copyright 2026 | Alle Rechte vorbehalten
- **[PASS]** Copyright holder: | Alle Rechte vorbehalten

### Regulatory Indicators

*2 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: .de; Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.
- **[INFO]** PCI-DSS indicators detected (moderate confidence) — Indicators suggesting PCI-DSS may be relevant: Payment processor detected: paypal.com. Payment Card Industry Data Security Standard — applies to organizations handling credit card data.

### Third-Party Data Sharing

*2 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]** 2 third-party services across 2 categories — 2 third-party services detected across 2 categories: Analytics (1), Payment (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.
- **[INFO]** PayPal (Payment) — Detected via script URL. Typically collects: Payment data, Transaction details, User identity. Privacy policy: https://www.paypal.com/us/legalhub/privacy-full. 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 (A — 85/100)

*AWS CloudFront (Miss from cloudfront)*

- **[PASS]** Site is served via AWS CloudFront CDN (edge: LHR3-P4)
- **[INFO]** CDN cache status: Miss from cloudfront

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

*no-cache*

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

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

- **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
- **[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: MISS*

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

---

## Accessibility

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

*2 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[PASS]** 1 <nav> landmark(s) found
- **[INFO]** No contentinfo (footer) landmark
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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

*14 headings*

- **[PASS]** Single H1 present

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

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

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

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

*All 15 images OK*

- **[PASS]** 15 image(s) with good alt text

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

*All 6 controls labeled*

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

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

*225 links, 7 buttons — all OK*

- **[WARNING]** 3 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 222 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)

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

- **[WARNING]** 1 field(s) would benefit from inputmode attribute — Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

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

*Lang attribute set to "de"*

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

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

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

- **[INFO]** tabindex="-1" on naturally-focusable <input id="input-username_35"> — 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/4 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="https://pay.google.com/gp/p/ui/payframe?origin=https%3A%2F%2Fwww.party-schlaudt…") — 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 (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 (C — 75/100)

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

- **[WARNING]** 10 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.2px ("Anmelden"); <span> 11.2px ("Registrieren"); <span> 11.2px ("EUR"); <span> 11.2px ("0,00\u00a0EUR"); <label> 7.8px ("E-Mail **").

---

## UX

### 404 Error Page (B — 80/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page
- **[PASS]** Navigation links present on 404 page
- **[PASS]** Homepage link present on 404 page

### Favicon & Branding (F — 30/100)

*2 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

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

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

*No print styles*

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

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

*No navigation patterns*

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

*2 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.
- **[INFO]** iOS auto-link for phone numbers disabled (`format-detection: telephone=no`) — The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

---

## 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 optimized*

- **[PASS]** Page title is set
- **[PASS]** Title length (48 chars) is optimal
- **[WARNING]** No meta description tag found — Without a meta description, Google auto-generates a snippet from page content -- usually less click-attractive than a hand-written summary. Add `<meta name="description" content="...">` with a 70-160 char summary.
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

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

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

### Content Depth (C — 65/100)

*931 words, Very Difficult*

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

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

*225 internal, 0 external*

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

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

*7 images, 7 descriptive filenames*

- **[PASS]** All images have descriptive 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 (3/3 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 (3 URLs, 596 bytes)*

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

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

*1 markup-quality issue(s) detected*

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

---

## Sustainability

### CO2 Per Page Load (F — 30/100)

*2.73g CO2 per view*

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

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

*Not green*

- **[INFO]** No confirmed renewable energy commitment detected — Consider providers like Cloudflare, Google Cloud, or Vercel that match 100% of their energy use with renewables.
- **[INFO]** AWS: Renewable energy varies by region; committed to 100% by 2025
- **[INFO]** AWS CloudFront: Renewable varies by edge location
- **[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)

*99% cached*

- **[PASS]** 99% reduction on repeat visits — Returning visitors download only 58 KB (vs 9858 KB first visit). 102 of 105 resources are served from browser cache, saving 2.71g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.02g CO2 (first visit: 2.73g)

### Carbon Budget (F — 15/100)

*95th percentile*

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

### Transfer Efficiency (A+ — 100/100)

*96% efficient*

- **[PASS]** Transfer efficiency: 96% — Only 388 KB of potential savings identified. Your page is well-optimized for size.

### 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/ecba7602-79cf-4bdd-b245-2cf3c5820772*