chiesadimilano.it

Readiness by lane

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

Priority fixes for chiesadimilano.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 1800 seconds, 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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 69 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.

   33% of Uncategorized peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 31 external scripts 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.

   37% of Uncategorized peers do this.

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

What chiesadimilano.it already does well

Practices fewer than half of Uncategorized peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers

What we saw

Homepage checked

https://www.chiesadimilano.it/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoGetSSL, 395-day validity, expiring 2027-01-06

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

475 KB, gzip

Images on homepage

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

• atrungroi.com60
• btimes.jp60
• patriarchia.ru60
• xosomiennam.me60
• xsmn247.me62

Uncategorized readiness benchmark