# BeaverCheck Audit Report — https://www.urimat.com/de/

**Date:** September 9, 2026  
**URL:** https://www.urimat.com/de/  
**Overall Grade:** C (78/100)  
**Report:** https://beavercheck.com/results/cdf22e08-4ba2-4af2-8805-08b8cbb0bfb4

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** HSTS header is missing — Security > Security Headers
3. **[CRITICAL]** Page weighs 8.8 MB (6.2 MB transferred) — Performance > Page Weight Budget
4. **[CRITICAL]** 18 link(s) with no accessible text — Accessibility > Link & Button Quality
5. **[CRITICAL]** 2 image-only link(s) without alt text — Accessibility > Link & Button Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 47 |
| Accessibility | 86 |
| Best Practices | 100 |
| SEO | 92 |

---

## Security

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

*4 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is 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 (F — 0/100)

*No enforcing CSP policy found*

- **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 68 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 84 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 (D — 60/100)

*6 of 9 new-tab link(s) missing rel=noopener*

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

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

*15 inline style attribute(s) detected*

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### Subresource Integrity Adoption (D — 50/100)

*8% SRI adoption (1/12 third-party resources)*

- **[WARNING]** SRI adoption: 1/12 third-party resources protected (8%) — Of 12 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (8%) 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://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.0/css/all.min.css
  - https://scripts.clarity.ms/0.8.69/clarity.js
  - https://www.google-analytics.com/plugins/ua/linkid.js
  - https://buttons-config.sharethis.com/js/5bf5619da0286b00115a8ae4.js
  - https://www.clarity.ms/tag/93108cox5u

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 2 candidate URL(s))*

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

### HTML Version Disclosure (B — 90/100)

*1 generator tag(s) without version info*

- **[INFO]** 1 generator tag(s) without version info: TYPO3 CMS — 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 (D — 40/100)

*1 of 12 external resources have SRI*

- **[WARNING]** External link from cdnjs.cloudflare.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[PASS]** script from www.gstatic.com has SRI protection
- **[WARNING]** External script from scripts.clarity.ms 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 buttons-config.sharethis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.clarity.ms 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 platform-api.sharethis.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 cdnjs.cloudflare.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdnjs.cloudflare.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from ajax.googleapis.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 — 20/100)

*no DMARC, SPF: -all*

- **[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.
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[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)

*6.2 MB transferred, 55 requests*

- **[CRITICAL]** Page weighs 8.8 MB (6.2 MB transferred)
- **[WARNING]** Images are 5.1 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[WARNING]** JavaScript is 944 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[INFO]** 55 HTTP requests
- **[INFO]** Estimated 1.3 g CO2 per page load

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

*12% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 12% of page weight (783.3 KiB of 6.2 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 — 75/100)

*25 images, 0 KB saveable*

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

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

*3057ms total JS execution*

- **[WARNING]** https://www.urimat.com/typo3temp/assets/compressed...: 905ms CPU time
- **[WARNING]** https://www.urimat.com/de/: 625ms CPU time
- **[WARNING]** Unattributable: 509ms CPU time
- **[WARNING]** https://scripts.clarity.ms/0.8.69/clarity.js: 260ms CPU time
- **[INFO]** https://www.googletagmanager.com/gtag/js?id=G-YN4M...: 242ms CPU time
- **[INFO]** Third-party scripts: 1018ms (33% of total)

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

*3 fonts (172 KB)*

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

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

*12 scripts, 517 KB unused*

- **[WARNING]** https://www.gstatic.com/recaptcha/releases/8x-4t2p...: 247 KB unused (72%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.urimat.com/typo3temp/assets/compressed...: 157 KB unused (53%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.urimat.com/typo3temp/assets/compressed...: unminified — 109 KB could be saved
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-YN4M...: 70 KB unused (43%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://platform-api.sharethis.com/js/sharethis.js: 22 KB unused (44%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://platform-api.sharethis.com/js/sharethis.js: unminified — 15 KB could be saved
- **[WARNING]** https://ajax.googleapis.com/ajax/libs/jquery/3.2.1...: 22 KB unused (74%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 517 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)

*3 hints, 0 missing preconnects*

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

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

*Document 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.

### Asset Compression (B — 75/100)

*1 of 2 asset hosts serve text uncompressed*

- **[WARNING]** platform-cdn.sharethis.com serves text assets uncompressed (assets: 6) — The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
- **[PASS]** cdnjs.cloudflare.com serves assets with brotli (assets: 5)

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

*Main HTML max-age=86400 (~1440min) is aggressive*

- **[WARNING]** Main HTML cached for 1440 minutes -- risks stale auth / SPA state — Long max-age on the main HTML document means users may see outdated auth state, SPA shells, or A/B variants until the cache expires. Consider Cache-Control: no-cache (or max-age=300) for HTML and let your hashed assets (JS/CSS/images) carry the long cache instead.

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

*55 resources · 6.2 MB · 517 KB savings available*

- **[WARNING]** Page weight 6.2 MB exceeds 1 MB target by 5.2 MB
- **[INFO]** ~517 KB of savings available
- **[INFO]** 29 third-party resources (12% of weight)
- **[INFO]** 14 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 — 88/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** 4 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

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

*No CSS performance depth issues detected*

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

---

## Content Quality

### Links (F — 40/100)

*84 links checked, 28 healthy, 56 broken*

- **[CRITICAL]** 28 of 84 links are healthy
- **[WARNING]** Broken link: https://www.urimat.com/typo3temp/assets/compressed/merged... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://fonts.googleapis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://platform-api.sharethis.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.urimat.com/de/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/en/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fr/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/it/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/es/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/pt/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/hu/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/jp/ — Found in <link href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/meta/datenschutzrichtlinien — Found in <a href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3conf/ext/threeme/Resources/Pu... — Found in <img src>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/urinale — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/haendetrockner — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/mb-activetrap — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/sanitaerreiniger — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/reinigungstablette — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/threeinone-waschplatz-... — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/trennwaende — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/unterputzrahmen — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/green-drain — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/kiddy-step-pro — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/urimat-connect — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/produkte/desinfektion — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services/videoanleitungen — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services/news-updates — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services/downloads — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services/einsparung-1 — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/services/haeufig-gestellte-frag... — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/ueber-uns — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/ueber-uns/leitbild — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/ueber-uns/nachhaltigkeit — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/ueber-uns/referenzen — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/ueber-uns/karriere — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/kontakt — Found in <a href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/_processed_/c/2/csm_berg... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/teaser/startseite/202003... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/_processed_/8/5/csm_ch.m... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/_processed_/e/a/csm_sif_... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/_processed_/d/9/csm_meda... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/_processed_/9/0/csm_u.s.... — Found in <img src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/produkte/urinale/header-... — Found in <img src>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/meta/agb — Found in <a href>. Returns HTTP 415.
- **[CRITICAL]** Broken link: https://www.urimat.com/de/meta/impressum — Found in <a href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://urimat.com/ — Found in <link href>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3temp/assets/compressed/merged... — Found in <script src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/typo3temp/assets/compressed/merged... — Found in <script src>. Returns HTTP 415.
- **[WARNING]** Broken link: https://www.urimat.com/fileadmin/user_upload/start-seite-... — Found in <meta og:image>. Returns HTTP 415.

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

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

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

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

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

- **[CRITICAL]** og:image is not reachable — The og:image URL could not be fetched. Social platforms won't be able to display it.
- **[INFO]** og:title is long (75 characters) — Titles over 60 characters may be truncated in social sharing previews.
- **[INFO]** og:description is long (304 characters) — Descriptions over 200 characters may be truncated in social sharing previews.
- **[INFO]** Missing og:url — The og:url tag specifies the canonical URL for the shared content.

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

*OG image dimensions and Twitter card configuration look healthy*

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

### Structured Data (C — 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 — 25/100)

*7 issues found across 15 images*

- **[WARNING]** 6 images significantly larger than display size — Resizing to display dimensions could save approximately 1164 KB.
- **[WARNING]** 6 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 9 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 7 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.
- **[WARNING]** Total image weight: 1551 KB (1.5 MB) — Consider compressing images, using modern formats, and serving appropriately sized images.
- **[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.urimat.com/fileadmin/_processed_/c/2/csm_bergsee-header-1920x1080_834adf7769.jpg.
- **[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://www.urimat.com/fileadmin/_processed_/c/2/csm_bergsee-header-1920x1080_834adf7769.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)

*1 A records, 42 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[PASS]** Has 1 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]** 2 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 42 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/2 IPs match cert SAN*

- **[INFO]** PTR for 149.126.6.123 does not match any cert SAN: vsa-vatmio.cyon.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 2a01:ab20:0:6::123 does not match any cert SAN: vsa-vatmio.cyon.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.

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

*Mean 32ms across 3 resolvers (spread 64ms)*

- **[PASS]** Quad9: 0ms
- **[PASS]** Google: 34ms
- **[PASS]** Cloudflare: 64ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (27 ms)*

- **[PASS]** IPv6 is configured and reachable at 2a01:ab20:0:6::123

### Crawlability (B — 75/100)

*no robots.txt, no sitemap*

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

### URL Variants (B — 75/100)

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

- **[CRITICAL]** HTTP version does not redirect to HTTPS

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

*urimat.com — via IONOS SE, 28 years, 3 months old*

- **[WARNING]** Domain expires in 51 days — Consider enabling auto-renewal to prevent accidental expiration.
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[PASS]** Registrar: IONOS SE
- **[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 — 85/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected in the page — No link matching the privacy-policy vocabulary was found in the rendered page. The common privacy-policy paths were not probed for this scan, so this is an unconfirmed absence and is excluded from the regulatory-risk estimate.
- **[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 (F — 10/100)

*Missing <html lang>*

- **[WARNING]** <html lang> attribute is missing — The lang attribute on <html> is required for screen readers and WCAG 3.1.1 compliance.
- **[PASS]** Content-Language header is set
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

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

*All 9 hreflang tag(s) look correct*

- **[PASS]** All 9 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. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (F — 25/100)

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

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

### Third-Party Trackers (F — 35/100)

*4 trackers detected*

- **[INFO]** 4 third-party trackers detected — Found 2 analytics, 0 advertising, 0 marketing, 1 tag manager, 1 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 session-replay tool(s) detected (Microsoft Clarity) — Session-replay tools record what users type, click, and scroll. Under GDPR these are high-risk processing requiring explicit consent and (per UK ICO and French CNIL guidance) often a Data Protection Impact Assessment. Mask sensitive form fields and gate firing on user consent.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 4 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

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

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

- **[INFO]** 4 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 — 60/100)

*2 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at /de/meta/datenschutzrichtlinien, linked from footer.
- **[PASS]** Terms of Service detected — Found at /de/meta/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.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (strong confidence) — Indicators suggesting GDPR may be relevant: European language 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

*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), CDN (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]** Cloudflare (CDN) — Detected via script URL. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. 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 (C — 65/100)

*Assets on AWS CloudFront (host platform-cdn.sharethis.com, 6 assets); document served directly from origin*

- **[WARNING]** Document not behind existing CDN (AWS CloudFront serves the assets) — The page's subresources are delivered by AWS CloudFront (platform-cdn.sharethis.com, 6 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
- **[PASS]** Assets on AWS CloudFront: platform-cdn.sharethis.com (assets: 6), cache Hit from cloudfront
- **[PASS]** Assets on Cloudflare: cdnjs.cloudflare.com (assets: 5), cache BYPASS

### HTTP Caching (A — 90/100)

*max-age=86400 (1 day)*

- **[PASS]** Cache-Control header is set
- **[PASS]** Effective TTL: 1 day (max-age=86400)
- **[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 — 85/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.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 415, /health: 415, /healthz: 415, /ping: 415, /status: 415.

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

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

*14 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 11 <nav> landmark(s) found
- **[WARNING]** 11 of 11 <nav> elements are unlabeled — Multiple navigations need aria-label to distinguish them for screen readers.
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (D — 40/100)

*25 headings, 4 skip(s)*

- **[PASS]** Single H1 present
- **[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]** Heading level skipped: H2 → H4 (missing H3) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

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

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

- **[INFO]** 2 heading(s) are too short (≤2 characters) to convey meaning — Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected:
  - H2: "l"
  - H2: "g"

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

*All 15 images OK*

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

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

*All 3 controls labeled*

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

### Link & Button Quality (F — 38/100)

*18 issue(s) across 124 links and 8 buttons*

- **[CRITICAL]** 18 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[CRITICAL]** 2 image-only link(s) without alt text — Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
- **[WARNING]** 9 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 95 link(s) with descriptive text

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

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

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

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

*3 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 (F — 40/100)

*Missing <html lang> attribute (WCAG 3.1.1)*

- **[CRITICAL]** Missing <html lang> attribute (WCAG 3.1.1) — Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

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

*0 positive, 10 -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 <button id="slick-slide-control01"> — 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 <button id="slick-slide-control02"> — 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 <button id="slick-slide-control03"> — 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 106 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 — 0/100)

*HTTP 415, bare page*

- **[WARNING]** Unexpected status code: HTTP 415 — Expected HTTP 404 but received 415. This may confuse search engine crawlers.
- **[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 (C — 55/100)

*3 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (D — 40/100)

*Not found*

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

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

*No PWA depth issues detected*

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

### Dark Mode Support (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]** 11 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)

*2 mobile-depth signal(s) detected*

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

*Minor issues*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[CRITICAL]** Canonical target returns 415 — Search engines cannot follow this canonical, effectively orphaning this page.

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

*Title: 98 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is 98 characters — will be truncated in search results
- **[INFO]** Meta description is 311 characters — truncated on mobile (~160 char limit)
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

*1 title-style issue(s) detected*

- **[INFO]** Title uses 2 different separator characters: :, - — The page title `URIMAT: Innovative wasserlose Urinale und umweltfreundliche ...` uses multiple separator characters (:, -). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.

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

*1167 words, Very Difficult*

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

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

*115 internal, 9 external*

- **[PASS]** 115 internal links (93%)
- **[PASS]** 85% of links use descriptive anchor text
- **[INFO]** 115 internal / 9 external links

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

*15 images, 15 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 (C — 75/100)

*No sitemap.xml found*

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

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

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

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

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

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

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

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

*No markup-quality issues detected*

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

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*1.48g CO2 per view*

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

### Green Hosting (B — 80/100)

*Green (hosting)*

- **[PASS]** cyon uses renewable energy
- **[INFO]** cyon: Verified by the Green Web Foundation
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

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

*100% cached*

- **[PASS]** 100% reduction on repeat visits — Returning visitors download only 19 KB (vs 6399 KB first visit). 54 of 55 resources are served from browser cache, saving 1.47g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 1.48g)

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

*75th percentile*

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

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

*92% efficient*

- **[PASS]** Transfer efficiency: 92% — Only 517 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/cdf22e08-4ba2-4af2-8805-08b8cbb0bfb4*