gaumenfreundin.de

Readiness by lane

Green: gaumenfreundin.de. Thin bar: Online Publishing peer median.

Priority fixes for gaumenfreundin.de

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   27% of Online Publishing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 75 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   38% of Online Publishing peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 14 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   45% of Online Publishing peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Enable

   Page language declared

   Observed: The homepage <html> element had no lang attribute.

   What to do: Set lang on the html element (for example lang="en") and on any sections in another language.

   92% of Online Publishing peers do this.

   Guide: Website Accessibility Checklist for Owners

What gaumenfreundin.de already does well

Practices fewer than half of Online Publishing peers use.

• HTTP/3 advertisedHTTP/3 advertised.41% of peers
• Reachable over IPv6IPv6 address published.48% of peers

What we saw

Homepage checked

https://www.gaumenfreundin.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-16

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

176 KB, br

Images on homepage

75 (jpg 219, svg 20, png 6)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Online Publishing sites

• alamto.com62
• apetitonline.cz62
• manhuahot.com62
• mi-mollet.com62
• yaoiscan.me63

Online Publishing readiness benchmark