Website readiness profile · Snapshot 23 October 2026
luma.com
luma.com's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.
- Readiness index
- 82/100
- Ahead of
- 94%
- Practices observed
- 22/29
- Popularity band
- Top 50K
Events & Online Ticketing median 63
of measured Events & Online Ticketing sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: luma.com. Thin bar: Events & Online Ticketing peer median.
Enable
92/100
Peers 78
Harden
69/100
Peers 57
Accelerate
100/100
Peers 59
Recover
0/100
Peers 7
Priority fixes for luma.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 0 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
42% of Events & Online Ticketing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · 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.
Priority 3 · 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.
On Next.js: Next.js documents nonce-based CSP with middleware.
30% of Events & Online Ticketing peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for luma.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
11% of Events & Online Ticketing peers do this.
What luma.com already does well
Practices fewer than half of Events & Online Ticketing peers use.
- security.txt publishedsecurity.txt with a contact found.4.3% of peers
- HTTP/3 advertisedHTTP/3 advertised.24% of peers
- Reachable over IPv6IPv6 address published.35% of peers
What we saw
- Homepage checked
- https://luma.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-02
- CDN or edge
- Cloudflare, Vercel
- Platform or framework
- Next.js
- DNS operators
- Cloudflare
- HSTS
- max-age 0 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 44 KB, br
- Images on homepage
- 0
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
Not observed 7
Observed 22
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own luma.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: luma.com. This profile covers configuration only.