runsignup.com

Readiness by lane

Green: runsignup.com. Thin bar: Events & Online Ticketing peer median.

Priority fixes for runsignup.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   42% of Events & Online Ticketing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

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

   35% of Events & Online Ticketing peers do this.

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

3. Priority 3 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   65% of Events & Online Ticketing peers do this.

   Guide: SEO Checklist for a New Website

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.

   30% of Events & Online Ticketing peers do this.

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

What runsignup.com already does well

Practices fewer than half of Events & Online Ticketing peers use.

• Modern image formats in useWebP or AVIF images detected.42% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.43% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.44% of peers

What we saw

Homepage checked

https://runsignup.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

DNS operators

Amazon Route 53

HSTS

max-age 183 days

DMARC policy

p=quarantine

Homepage HTML

120 KB, gzip

Images on homepage

55 (webp 129, jpg 88, png 81, gif 12, svg 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 Events & Online Ticketing sites

• asoview.com71
• buyticketbrasil.com71
• santafe2026.ar71
• teket.jp71
• ticketmaster.it72

Events & Online Ticketing readiness benchmark