zeffy.com

Readiness by lane

Green: zeffy.com. Thin bar: Crowdfunding Platforms peer median.

Priority fixes for zeffy.com

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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   35% of Crowdfunding Platforms 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 · 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.

   65% of Crowdfunding Platforms peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · 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.

   42% of Crowdfunding Platforms peers do this.

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

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 Crowdfunding Platforms peers do this.

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

What zeffy.com already does well

Practices fewer than half of Crowdfunding Platforms peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
• Modern image formats in useWebP or AVIF images detected.40% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://www.zeffy.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-11-25

CDN or edge

Cloudflare

Platform or framework

Webflow

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

426 KB, br

Images on homepage

244 (webp 316, svg 147, png 66, avif 10, jpg 2)

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 Crowdfunding Platforms sites

• cafecito.app69
• camp-fire.jp70
• justgiving.com73
• patreon.com72
• rifa.digital73

Crowdfunding Platforms readiness benchmark