rifa.digital

Readiness by lane

Green: rifa.digital. Thin bar: Crowdfunding Platforms peer median.

Priority fixes for rifa.digital

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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 Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   60% of Crowdfunding Platforms peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for rifa.digital 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.

   54% of Crowdfunding Platforms peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   35% of Crowdfunding Platforms peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   42% of Crowdfunding Platforms peers do this.

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

What rifa.digital already does well

Practices fewer than half of Crowdfunding Platforms peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• Modern image formats in useWebP or AVIF images detected.40% of peers

What we saw

Homepage checked

https://rifa.digital/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

122 KB, br

Images on homepage

18 (webp 11, svg 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 Crowdfunding Platforms sites

• furuke.com74
• givebutter.com74
• justgiving.com73
• patreon.com72
• zeffy.com72

Crowdfunding Platforms readiness benchmark