marham.pk

Readiness by lane

Green: marham.pk. Thin bar: Fitness & Health peer median.

Priority fixes for marham.pk

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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for marham.pk was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   44% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 44 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   68% of Fitness & Health peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   7.3% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

What marham.pk already does well

Practices fewer than half of Fitness & Health peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.11% of peers
• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• Reachable over IPv6IPv6 address published.36% of peers

What we saw

Homepage checked

https://www.marham.pk/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-10

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 180 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

1,254 KB, br

Images on homepage

44 (avif 39, png 4, gif 1)

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

• bigmusclesnutrition.com80
• diag.pl81
• halodoc.com81
• helsenorge.no80
• womenshealthmag.com82

Fitness & Health readiness benchmark