guard.io

Readiness by lane

Green: guard.io. Thin bar: Security & Monitoring peer median.

Priority fixes for guard.io

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://guard.io/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On Cloudflare: Turn on Always Use HTTPS under SSL/TLS > Edge Certificates.

   88% of Security & Monitoring peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 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.

   47% of Security & Monitoring peers do this.

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

3. Priority 3 · 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 Cloudflare: Add the header with a response header transform rule.

   62% of Security & Monitoring peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Webflow: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   33% of Security & Monitoring peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What guard.io already does well

Practices fewer than half of Security & Monitoring peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.40% of peers
• HTTP/3 advertisedHTTP/3 advertised.40% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.42% of peers

What we saw

Homepage checked

https://guard.io/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-29

CDN or edge

Cloudflare, Google edge

Platform or framework

Webflow

DNS operators

Google Cloud DNS

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

141 KB, gzip

Images on homepage

52 (webp 44, svg 17, avif 9)

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 Security & Monitoring sites

• feedly.com86
• osirisai.live77
• spappmonitoring.com65
• tabangohar.com64
• truecaller.com79

Security & Monitoring readiness benchmark