karzar.net

Readiness by lane

Green: karzar.net. Thin bar: Crowdfunding Platforms peer median.

Priority fixes for karzar.net

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   60% of Crowdfunding Platforms peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for karzar.net 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.

   54% of Crowdfunding Platforms peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   71% of Crowdfunding Platforms peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

4. Priority 4 · Harden

   HSTS kept for at least a year

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

   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.

   35% of Crowdfunding Platforms peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What karzar.net already does well

Practices fewer than half of Crowdfunding Platforms peers use.

• Content Security Policy presentContent-Security-Policy present.33% of peers
• Modern image formats in useWebP or AVIF images detected.40% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://www.karzar.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-29

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

215 KB, gzip

Images on homepage

179 (png 91, jpg 51, svg 31, webp 3)

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 Crowdfunding Platforms sites

• americasfavoritephotos.com60
• animalwebaction.com64
• dreammail.jp58
• gofundme.com63
• tsunagu.cloud51

Crowdfunding Platforms readiness benchmark