writing.com

Readiness by lane

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

Priority fixes for writing.com

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   87% of Forums & Communities peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   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.

   30% of Forums & Communities peers do this.

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

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.

   33% of Forums & Communities peers do this.

   Guide: CDN Guide for Website Owners

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.

   17% of Forums & Communities peers do this.

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

What writing.com already does well

Practices fewer than half of Forums & Communities peers use.

• Referrer-Policy setReferrer-Policy present.25% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.28% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.31% of peers

What we saw

Homepage checked

https://www.writing.com/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

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

DNS operators

Linode/Akamai DNS

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

38 KB, gzip

Images on homepage

15 (svg 10, png 5)

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

• cocoland.cc71
• furaffinity.net72
• gumpla.jp71
• kadinlarkulubu.com72
• urbandictionary.com73

Forums & Communities readiness benchmark