ravelry.com

Readiness by lane

Green: ravelry.com. Thin bar: Forums & Communities peer median.

Priority fixes for ravelry.com

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   61% of Forums & Communities peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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.

   41% of Forums & Communities peers do this.

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

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Sectigo Limited had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   81% of Forums & Communities peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   33% of Forums & Communities peers do this.

   Guide: CDN Guide for Website Owners

What ravelry.com already does well

Practices fewer than half of Forums & Communities peers use.

• Content Security Policy presentContent-Security-Policy present.17% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.28% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.31% of peers

What we saw

Homepage checked

https://www.ravelry.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2027-01-27

DNS operators

Bunny DNS

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

6 KB, gzip

Images on homepage

1 (svg 1)

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 Forums & Communities sites

• hiveworkshop.com68
• mumsnet.com68
• nodzway.com68
• resetera.com68
• senang.top68

Forums & Communities readiness benchmark