zinzino.com

Readiness by lane

Green: zinzino.com. Thin bar: Fitness & Health peer median.

Priority fixes for zinzino.com

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (420 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   90% of Fitness & Health peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

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.

   On Azure Front Door/CDN: Add a response header action in a Front Door rule set.

   43% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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 Next.js: Use the next/script component with an appropriate loading strategy.

   45% of Fitness & Health peers do this.

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

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   58% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

What zinzino.com already does well

Practices fewer than half of Fitness & Health peers use.

• Reachable over IPv6IPv6 address published.36% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.44% of peers
• Modern image formats in useWebP or AVIF images detected.45% of peers

What we saw

Homepage checked

https://www.zinzino.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 365-day validity, expiring 2027-02-26

CDN or edge

Azure Front Door/CDN

Platform or framework

Next.js

DNS operators

Azure DNS

DMARC policy

p=quarantine

Homepage HTML

420 KB, uncompressed

Images on homepage

31 (png 20, jpg 8, 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 Fitness & Health sites

• invisalign.in61
• lemedecin.fr61
• medicaldoc.jp62
• shape.gr62
• tamanhhospital.vn62

Fitness & Health readiness benchmark