collective.world

Readiness by lane

Green: collective.world. Thin bar: Online Publishing peer median.

Priority fixes for collective.world

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 29 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   38% of Online Publishing peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.collective.world.

   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.

   20% of Online Publishing peers do this.

   Guide: A Practical Website Health Check for 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 Shopify: 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.

   41% of Online Publishing peers do this.

   Guide: CDN Guide for Website Owners

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 Shopify: 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.

   37% of Online Publishing peers do this.

   Guide: A Practical Website Health Check for Owners

What collective.world already does well

Practices fewer than half of Online Publishing peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.27% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://collective.world/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-28

CDN or edge

WordPress VIP

Platform or framework

WordPress, Shopify

DNS operators

Amazon Route 53

HSTS

max-age 365 days

Homepage HTML

355 KB, br

Images on homepage

29 (png 111, jpg 84)

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 Online Publishing sites

• brightside.me70
• capibaratraductor.com70
• kbm.id70
• maison-travaux.fr70
• tennenseikatsu.jp71

Online Publishing readiness benchmark