egeszsegkalauz.hu

Readiness by lane

Green: egeszsegkalauz.hu. Thin bar: Fitness & Health peer median.

Priority fixes for egeszsegkalauz.hu

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   43% of Fitness & Health 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 59 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   45% of Fitness & Health 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 1 external script 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 Fitness & Health peers do this.

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

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Amazon CloudFront: Enable it in a response headers policy (security headers section).

   56% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

What egeszsegkalauz.hu already does well

Practices fewer than half of Fitness & Health peers use.

• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• Content Security Policy presentContent-Security-Policy present.38% of peers

What we saw

Homepage checked

https://www.egeszsegkalauz.hu/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-14

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 180 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

202 KB, gzip

Images on homepage

59 (png 17)

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 Fitness & Health sites

• esanj.ir75
• helios-gesundheit.de75
• plannedparenthood.org76
• simple.life76
• traya.health76

Fitness & Health readiness benchmark