wizaz.pl

Readiness by lane

Green: wizaz.pl. Thin bar: Forums & Communities peer median.

Priority fixes for wizaz.pl

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 14 days, 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.

   51% of Forums & Communities 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

   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.

   28% of Forums & Communities peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   85% of Forums & Communities peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for wizaz.pl 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.

   31% of Forums & Communities peers do this.

   Guide: A Practical Website Health Check for Owners

What wizaz.pl already does well

Practices fewer than half of Forums & Communities peers use.

• Modern image formats in useWebP or AVIF images detected.30% of peers
• Structured data presentJSON-LD structured data found.37% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.41% of peers

What we saw

Homepage checked

https://wizaz.pl/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Bunny CDN

DNS operators

Bunny DNS

DMARC policy

p=none

Homepage HTML

364 KB, br

Images on homepage

99 (jpg 354, png 105, svg 4)

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 Forums & Communities sites

• flyteam.jp61
• jkforum.net61
• sfsforum.com62
• trucksbook.eu62
• v2ex.com62

Forums & Communities readiness benchmark