Website readiness profile · Snapshot 23 October 2026
vivaticket.com
vivaticket.com's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.
- Readiness index
- 49/100
- Ahead of
- 15%
- Practices observed
- 11/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: vivaticket.com. Thin bar: Events & Online Ticketing peer median.
Enable
49/100
Peers 78
Harden
49/100
Peers 57
Accelerate
50/100
Peers 59
Recover
0/100
Peers 7
Priority fixes for vivaticket.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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.
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
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for vivaticket.com was p=none, which asks receivers to take no action on failing mail.
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.
44% of Events & Online Ticketing peers do this.
Priority 4 · Enable
Meta description written
Observed: The homepage had no meta description.
What to do: Write a short, specific description of the page for people, not a list of keywords.
91% of Events & Online Ticketing peers do this.
Guide: Meta Titles and Descriptions That Match Search Intent
What vivaticket.com already does well
Practices fewer than half of Events & Online Ticketing peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, certigna.fr, globalsign.com and others.11% of peers
What we saw
- Homepage checked
- https://www.vivaticket.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 90-day validity, expiring 2027-01-20
- CDN or edge
- Google edge, Imperva
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 10 KB, gzip
- 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 18
- HSTS kept for at least a year
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Reachable over IPv6
- Meta description written
- Structured data present
- Social preview image set
- Page language declared
- Nameservers spread across providers
Observed 11
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- HTTP/2 negotiated
- HTML compressed
- robots.txt published
- Canonical URL declared
- Mobile viewport configured
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own vivaticket.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: vivaticket.com. This profile covers configuration only.