# BeaverCheck Audit Report — https://www.madcoinvlog.de

**Date:** August 9, 2026  
**URL:** https://www.madcoinvlog.de  
**Overall Grade:** C (78/100)  
**Report:** https://beavercheck.com/results/513cbd41-0e13-4732-93c0-f39e188a7a81

## Top Findings

1. **[CRITICAL]** HSTS header is missing — Security > Security Headers
2. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality
3. **[CRITICAL]** 12 image-in-link without alt text — Accessibility > Alt Text Quality
4. **[CRITICAL]** 16 image(s) missing alt attribute — Accessibility > Alt Text Quality
5. **[CRITICAL]** 23 link(s) with no accessible text — Accessibility > Link & Button Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 47 |
| Accessibility | 75 |
| Best Practices | 96 |
| SEO | 92 |

---

## Security

### Security Headers (F — 35/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
- **[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 present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (C — 65/100)

*2 of 11 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'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[PASS]** upgrade-insecure-requests is enabled
- **[INFO]** Content-Security-Policy-Report-Only is also set — A report-only policy is active alongside the enforcing policy for monitoring.

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

*TLS 1.3, 7 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 43 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 1 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

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

*No cookies set — no cookie security risks*

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

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

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

- **[PASS]** No cookies set

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

*No WAF detected via response headers*

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

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

*No security.txt file found*

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

### Cross-Origin Tab Safety (D — 60/100)

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

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

### CSP Inline-Style Readiness (D — 60/100)

*125 inline style attribute(s) detected*

- **[WARNING]** 125 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. 125 inline style(s) is high. Affected element types include: div, a, img, p, span. 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/21 third-party resources)*

- **[WARNING]** SRI adoption: 0/21 third-party resources protected (0%) — Of 21 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.blogger.com/static/v1/widgets/2872013778-css_bundle_v2.css
  - https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202608040101/show_ads_impl.js
  - https://apis.google.com/_/scs/abc-static/_/js/k=gapi.lb.en.9vdPKhB0RUg.O/m=gapi_iframes/rt=j/sv=1/d=1/ed=1/rs=AHpOoo97anj7zZ432JcN58tqJJp_A6WeOw/cb=gapi.loaded_0?le=scs,fedcm_migration_mod
  - https://www.googletagmanager.com/gtag/js?id=G-BQC7BZVYVF
  - https://www.blogger.com/dyn-css/authorization.css?targetBlogID=1243776478934316194&zx=20073f8a-6817-4366-8d3c-f14dc9fb336d

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

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

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

*1 generator tag(s) without version info*

- **[INFO]** 1 generator tag(s) without version info: blogger — 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 (B — 80/100)

*50 link(s) carry redirect-shaped query parameter(s)*

- **[INFO]** 50 link(s) carry redirect-shaped query parameter(s) — Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.

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

- **[WARNING]** External link from www.blogger.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from apis.google.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 www.blogger.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from pagead2.googlesyndication.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from translate.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from apis.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from translate.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.gstatic.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.blogger.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from www.blogger.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.blogger.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 (D — 46/100)

*2.4 MB transferred, 160 requests*

- **[INFO]** Page weighs 5.9 MB (2.4 MB transferred)
- **[WARNING]** JavaScript is 1.4 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 160 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.49 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 (2.3 MiB of 2.4 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)

*42 images, 0 KB saveable*

- **[WARNING]** https://blogger.googleusercontent.com/img/b/R29vZ2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://resources.blogblog.com/img/widgets/arrow_d... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://blogger.googleusercontent.com/img/b/R29vZ2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://resources.blogblog.com/img/icon_feed12.png is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://blogger.googleusercontent.com/img/b/R29vZ2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://all-inkl.com/banner/all-inkl_banner_468x60... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://blogger.googleusercontent.com/img/b/R29vZ2... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://resources.blogblog.com/img/widgets/icon_wi... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

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

*7543ms total JS execution*

- **[WARNING]** https://www.madcoinvlog.de/?m=1: 3859ms CPU time
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-BQC7...: 830ms CPU time
- **[WARNING]** Unattributable: 712ms CPU time
- **[WARNING]** https://pagead2.googlesyndication.com/pagead/manag...: 651ms CPU time
- **[WARNING]** https://translate.googleapis.com/_/translate_http/...: 395ms CPU time
- **[INFO]** Third-party scripts: 2972ms (39% of total)

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

*1 fonts (34 KB)*

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

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

*64 scripts, 512 KB unused*

- **[WARNING]** https://pagead2.googlesyndication.com/pagead/manag...: 123 KB unused (74%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.gstatic.com/charts/51/js/jsapi_compile...: 113 KB unused (68%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.blogger.com/static/v1/jsbin/1860843701...: 102 KB unused (84%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-BQC7...: 66 KB unused (40%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.gstatic.com/charts/51/js/jsapi_compile...: 47 KB unused (57%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 512 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)

*No optimization needed*

- **[PASS]** No resource hint issues

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Compression Algorithm (B — 80/100)

*Main response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### 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 max-age=0 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate

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

*2 server-response signal(s) detected*

- **[WARNING]** Compressed response missing `Vary` header — The page is served with `Content-Encoding: gzip` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.
- **[PASS]** Both `ETag` and `Last-Modified` present -- efficient revalidation supported — The page returns both `ETag` (content hash) and `Last-Modified` (timestamp) headers. Browsers can issue conditional GETs with `If-None-Match` or `If-Modified-Since`; the server returns 304 Not Modified for unchanged content, saving bandwidth. ETag is the more reliable of the two (timestamps fail in DST transitions and clock skew).

### Page Weight Inventory (F — 35/100)

*160 resources · 2.4 MB · 512 KB savings available*

- **[WARNING]** Page weight 2.4 MB exceeds 1 MB target by 1.4 MB
- **[INFO]** ~512 KB of savings available
- **[WARNING]** 153 third-party resources (99% of weight)
- **[INFO]** 1 resources over 200KB

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

*No render-blocking resources detected*

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

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

*No third-party resources detected*


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

*2 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.
- **[WARNING]** Total JS execution time is 7.5 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

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

*1 CSS depth issue(s) detected*

- **[WARNING]** 6 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (A — 90/100)

*200 links checked, 147 healthy, 0 broken*

- **[PASS]** 147 of 200 links are healthy
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (4 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (5 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com/share-post.g?blogID=124... (3 hops)
- **[INFO]** Long redirect chain: https://add.my.yahoo.com/content?url=https%3A%2... (3 hops)
- **[INFO]** Long redirect chain: https://add.my.yahoo.com/content?url=https%3A%2... (3 hops)
- **[INFO]** Long redirect chain: https://wikipedia.org/wiki/ (3 hops)
- **[INFO]** Long redirect chain: https://www.blogger.com (4 hops)

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

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

- **[WARNING]** Missing og:image — The og:image tag provides a preview image for social sharing.
- **[INFO]** Missing og:type — The og:type tag helps social platforms categorize the content.
- **[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)

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

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

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

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

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

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

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

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

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

*7 issues found across 33 images*

- **[WARNING]** 22 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 21 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 31 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]** 16 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[WARNING]** 1 above-fold image(s) marked loading="lazy" (LCP anti-pattern) — Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiG5wRHOFy0R-XJg6-wffc-gkfbU3NPSjhqiWdh2AXrS3NXKD8d7-uback8zTGGrtE4MH1uISQmUbcsGbjBxCBWjfink2MUFq3AMv1FnsJVeAw0pQCu1q9gX97pHRwNYNUOwOYaj1PLM_EZIEfH12rJ_YJhSQ2P-wMBO8k2jykebQVUTp6aybLTVn455CeF/w181-h200-rw/IMG_0941.jpeg.
- **[INFO]** 2 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://blogger.googleusercontent.com/img/a/AVvXsEjEpiqNdlHWVuviZW6rdD86RLkYJm12N-HEPsLQbQMOLnxWWMELkvNEjavYsBcFvQMKFesY4tFApENttyzkliO7aPy3vhQnFfxMVardWFAZcbK0YOaPrM9h52hmVn2dXzhKoxhbbQcMYsbWJb5COo-aW7eVzYsPerJR73ZsJHFOU7BvPIrMA-5K3nbET1zw=s1100, https://all-inkl.com/banner/all-inkl_banner_468x60_black.jpg.
- **[INFO]** 3 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://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvmOPdGeW8a7wPULLh_99a2waBAaaW6NzhTOLgv_6vey5fq0Jypmw-pex_y0F3uq4hfv6bhNIQE0dux6fXnWWoJGaqEcEXYsOuB2jABeA0OBnhqTWcAhrkXh9QEziMenizCpr88e2QJRCmChKXjHQpMPsWBzor2twy1C7j892tHVHnYcFD23_01S8RyDlv/w72-h72-p-k-no-nu/madcoinvlog_bitcoin_zinsen_og_1200x630%202.png, https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBuWzk23bCpg4GuW9UgcobeJd4XkiHJ6Dfqy_65uV1rF8Ingx0qHLbEO2s2RseBMx5PpVqa5dlb3OJvaVUfm0PeB5IjZeif3uj3azHhGZy1I66DhA0j5WZjb2U3lq1_BinaiTmuie7x21M7NB3LreS5CzE7m_oi7EdgKnQzS09l6Ntvbd8i_A4FdiZxjwK/w72-h72-p-k-no-nu/bitcoin-picture.jpg, https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEit87rXeRkk6Xgo45EvS_1n2Z3xSWuIKfSr8YwxTVhIAYxE5MieiWdnlwtm4LYGkf0nHAjDx_yxe5_YmW6ojClexH3xsvWbLgnM4vS9mtH21Jqgq2POz81mlQq0I5ObIXqVOvswR5rbXaPOR0t0_ib4iq40S4OlYy5MhgZ4CGT7DTn4YhaOJ3eWh0ftCr2s/w72-h72-p-k-no-nu/ETH.jpg.

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

*No autoplay media on the page*

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

---

## Infrastructure

### DNS Records (C — 65/100)

*1 A records, 476 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.
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[WARNING]** DNS resolution is slow (476 ms) — Slow DNS adds latency to every page load. Consider a faster DNS provider.

### 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 172.217.162.19 does not match any cert SAN: eze04s07-in-f19.1e100.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 2800:3f0:4001:83b::2013: lookup 2800:3f0:4001:83b::2013: 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 (C — 65/100)

*Mean 247ms across 3 resolvers (spread 78ms)*

- **[PASS]** Quad9: 200ms
- **[PASS]** Cloudflare: 263ms
- **[PASS]** Google: 278ms

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

*No redirects — direct access*

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

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

*IPv6 reachable (2 ms)*

- **[PASS]** IPv6 is configured and reachable at 2800:3f0:4001:83b::2013

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

*robots.txt present, sitemap with 17 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 17 entries
- **[INFO]** robots.txt does not reference a sitemap — Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 301-redirects to HTTPS

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

*madcoinvlog.de — hosted on Google Cloud*

- **[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: Google Cloud

---

## 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 — A privacy policy page is recommended for transparency and may be legally required.
- **[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)

*1 known tracker(s) detected*

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

analytics: Google Analytics 4

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)

*No hreflang tags on this page*

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

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

*1 i18n signal(s) detected*

- **[PASS]** Mixed-language content: 1 subtree language(s) declared (en) — The page has elements with `lang="X"` attributes that differ from the root `<html lang>`. Per WCAG 3.1.2 (Level AA), this is the correct way to mark language-of-parts: a screen reader switches pronunciation when entering a `lang="fr"` block on an English page. The catalog is informational -- presence of subtree lang attributes is a positive a11y signal.

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[WARNING]** width=device-width is not 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)

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

*3 trackers detected*

- **[INFO]** 3 third-party trackers detected — Found 1 analytics, 1 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** 1 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 3 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 · 3 trackers · 0 pre-consent*

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

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

*No tracking pixels detected*

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

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

*No browser-fingerprinting libraries detected*

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

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

*No cookies on the page*

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

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

*No navigator.sendBeacon usage detected in inline scripts*

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

---

## Legal

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

*0 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (A+ — 100/100)

*Copyright 2026 MadCoinVlog*

- **[PASS]** Copyright notice is up to date — Copyright notice is up to date: Copyright 2026 MadCoinVlog
- **[PASS]** Copyright holder: MadCoinVlog

### 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 (moderate confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .de. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*1 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: Analytics (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.

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

*No CDN detected*

- **[WARNING]** No CDN detected — A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

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

*private, max-age=0*

- **[PASS]** Cache-Control header is set
- **[PASS]** ETag present — enables conditional (304) responses
- **[PASS]** Last-Modified header present

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

*No status page link detected*

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

### Transport Security (B — 75/100)

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

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

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

*No conventional health endpoint found*

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

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

*No CDN cache-status headers in the response*

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

---

## Accessibility

### Landmark Structure (D — 50/100)

*4 landmarks*

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

*43 headings, 2 skip(s)*

- **[WARNING]** Multiple H1 headings (5 found) — A page should have only one H1. Multiple H1s dilute the document outline.
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** 1 empty heading(s) — Empty headings appear in the document outline but provide no information.

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

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

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

### Alt Text Quality (F — 30/100)

*16 of 33 images have issues*

- **[CRITICAL]** 16 image(s) missing alt attribute — Images without alt text are invisible to screen readers.
- **[CRITICAL]** 12 image-in-link without alt text — An image inside a link with no alt creates an empty link.
- **[PASS]** 9 decorative image(s) correctly marked
- **[PASS]** 8 image(s) with good alt text

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

*9 of 10 controls have issues*

- **[CRITICAL]** 9 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[PASS]** 1 control(s) properly labeled

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

*24 issue(s) across 246 links and 4 buttons*

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

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

*2 input(s) using type=text where a specific type would help*

- **[INFO]** Input "Wikipedia1_wikipedia-search-input" should use type="search" (currently type="text") — Field name "Wikipedia1_wikipedia-search-input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
- **[INFO]** Input "query" should use type="search" (currently type="text") — Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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

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

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

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

*No autofill-eligible form controls*

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

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

*Lang attribute set to "de"*

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

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

*2 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (C — 60/100)

*4/9 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="#") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://www.blogger.com/followers/frame/1243776478934316194?colors=Cgt0cmFuc3Bh…") — 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.
- **[WARNING]** <iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20260805/r20190131/zrt_lookup.…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

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

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

### Mobile-Readable Font Sizes (B — 90/100)

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

- **[INFO]** 2 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> 10.0px ("MadCoinVlog.de | App: BlockDAG X1 | Mark..."); <span> 10.0px ("Stand: 26. März 2026 | Redaktion: MadCoi...").

---

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

*No navigation patterns*

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

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

*1 mobile-depth signal(s) detected*

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

---

## SEO

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

*Properly configured*

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

### Meta Tags (A+ — 95/100)

*Title: 65 chars*

- **[PASS]** Page title is set
- **[INFO]** Title is 65 characters — may be truncated in search results
- **[PASS]** Meta description length (130 chars) is optimal
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

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

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

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

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

*1931 words, Very Difficult*

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

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

*169 internal, 77 external*

- **[PASS]** 169 internal links (69%)
- **[PASS]** 91% of links use descriptive anchor text
- **[INFO]** Page has 246 links — consider reducing
- **[INFO]** 169 internal / 77 external links
- **[WARNING]** 3 internal links have no anchor text

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

*33 images, 32 descriptive filenames*

- **[INFO]** 1 image(s) have hash/generic filenames
- **[INFO]** 16 image(s) missing alt text — see Accessibility tab

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

*Sitemap updated within the last year*

- **[INFO]** Newest sitemap lastmod is 3 months ago -- stale beyond 90 days — No URL in the sitemap has been updated in the last 90 days. The sitemap is technically valid but signals to crawlers that the site isn't actively changing.

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

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

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

*1 markup-quality issue(s) detected*

- **[WARNING]** No `<meta charset>` declaration in HTML — The page has no `<meta charset="...">` tag. Browsers fall back to a default encoding (typically UTF-8 in modern browsers, but not guaranteed). Add `<meta charset="utf-8">` as the first child of `<head>` to make the encoding explicit.

---

## Sustainability

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

*0.56g CO2 per view*

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

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

*Green (hosting)*

- **[PASS]** OpenGSE uses renewable energy
- **[INFO]** OpenGSE: 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)

*97% cached*

- **[PASS]** 97% reduction on repeat visits — Returning visitors download only 65 KB (vs 2411 KB first visit). 152 of 160 resources are served from browser cache, saving 0.54g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.02g CO2 (first visit: 0.56g)

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

*45th percentile*

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

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

*79% efficient*

- **[INFO]** Transfer efficiency: 79% — An estimated 512 KB (21%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 512 KB of unused JavaScript. This wasted data produces 0.12g of unnecessary CO2 per page view.

### Web Font Weight Variants (B — 90/100)

*No detectable Google Fonts weights*

- **[INFO]** No detectable Google Fonts weights — The analyzer detects font weights via Google Fonts URL parameters (~70% of font-using sites). Self-hosted fonts and non-Google CDN fonts aren't visible to URL-based detection. If you self-host fonts, manually audit how many @font-face weights you ship -- 2-3 weights per family is typically enough; 5+ is usually unused payload.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/513cbd41-0e13-4732-93c0-f39e188a7a81*