blender.org

Readiness by lane

Green: blender.org. Thin bar: Design & Content Creation peer median.

Priority fixes for blender.org

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.

   57% of Design & Content Creation 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

   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.

   37% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   43% of Design & Content Creation peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   64% of Design & Content Creation peers do this.

   Guide: Structured Data Basics for Website Owners

What blender.org already does well

Practices fewer than half of Design & Content Creation peers use.

• security.txt publishedsecurity.txt with a contact found.9.1% of peers
• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.17% of peers
• Referrer-Policy setReferrer-Policy present.26% of peers

What we saw

Homepage checked

https://www.blender.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-16

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

114 KB, br

Images on homepage

29 (jpg 18, webp 8, png 7)

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 Design & Content Creation sites

• 99designs.com81
• creators.google81
• flowaivideo.org81
• joliecarte.com82
• unlucid.ai82

Design & Content Creation readiness benchmark