setlist.fm

Readiness by lane

Green: setlist.fm. Thin bar: Forums & Communities peer median.

Priority fixes for setlist.fm

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for setlist.fm was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   31% of Forums & Communities peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 5 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

   No render-blocking scripts in <head>

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

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   61% of Forums & Communities peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What setlist.fm 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 covering subdomains.28% of peers
• HTTP/3 advertisedHTTP/3 advertised.33% of peers

What we saw

Homepage checked

https://www.setlist.fm/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2026-12-08

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

159 KB, gzip

Images on homepage

5 (jpg 2, png 1, gif 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

• iceout.org63
• notalwaysright.com63
• samequizy.pl63
• tigerdroppings.com63
• xamvn.courses63

Forums & Communities readiness benchmark