partiful.com

Readiness by lane

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

Priority fixes for partiful.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 30 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.

   On Vercel: Declare the header in the headers section of vercel.json.

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

   64% of Events & Online Ticketing peers do this.

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

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   51% of Events & Online Ticketing peers do this.

   Guide: Structured Data Basics for Website Owners

What partiful.com already does well

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

• DNSSEC signedDNSSEC delegation (DS record) present.9% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers

What we saw

Homepage checked

https://partiful.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-11

CDN or edge

Vercel

DNS operators

Google Cloud DNS

HSTS

max-age 30 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

1,002 KB, br

Images on homepage

69 (png 96, jpg 38, webp 24, svg 4)

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

• blizzcon.com73
• ebilet.pl74
• ticketpro.by74
• ticketsports.com.br75
• tixel.com75

Events & Online Ticketing readiness benchmark