chiesacattolica.it

Readiness by lane

Green: chiesacattolica.it. Thin bar: Uncategorized peer median.

Priority fixes for chiesacattolica.it

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.

   34% of Uncategorized 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

   Static files cached for 30 days or more

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

   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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   44% of Uncategorized peers do this.

   Guide: Browser Caching 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.

   90% of Uncategorized 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 chiesacattolica.it 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.

   39% of Uncategorized peers do this.

   Guide: A Practical Website Health Check for Owners

What chiesacattolica.it already does well

Practices fewer than half of Uncategorized peers use.

• Modern image formats in useWebP or AVIF images detected.33% of peers
• Framing restrictedFraming controls present.43% of peers

What we saw

Homepage checked

https://www.chiesacattolica.it/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoGetSSL, 198-day validity, expiring 2026-11-18

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

502 KB, gzip

Images on homepage

69 (jpg 27, png 9, webp 9, svg 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 Uncategorized sites

• fondoambiente.it53
• kqxs.vn53
• minhchinh.com56
• mitsubishielectric.co.jp56
• unkoi.com56

Uncategorized readiness benchmark