roll20.net

Readiness by lane

Green: roll20.net. Thin bar: Gaming Platforms & Consoles peer median.

Priority fixes for roll20.net

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 15 days, 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.

   46% of Gaming Platforms & Consoles 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.

   30% of Gaming Platforms & Consoles peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   XML sitemap discoverable

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

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

   61% of Gaming Platforms & Consoles peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 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.

   49% of Gaming Platforms & Consoles peers do this.

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

What roll20.net already does well

Practices fewer than half of Gaming Platforms & Consoles peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.6.4% of peers
• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.11% of peers
• Content Security Policy presentContent-Security-Policy present.22% of peers

What we saw

Homepage checked

https://roll20.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

74 KB, gzip

Images on homepage

76 (png 50, svg 18, jpg 5, webp 3)

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 Gaming Platforms & Consoles sites

• lootbar.com67
• myhorsez.com67
• rockstargames.com67
• sims4pack.ru67
• supercell.com67

Gaming Platforms & Consoles readiness benchmark