STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

zola.com

zola.com's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.

Readiness index
86/100

Events & Online Ticketing median 63

Ahead of
99%

of measured Events & Online Ticketing sites

Practices observed
25/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:40:55 UTC from one location. How we measure

Readiness by lane

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

Enable

95/100

Peers 78

Harden

91/100

Peers 57

Accelerate

73/100

Peers 59

Recover

0/100

Peers 7

Priority fixes for zola.com

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

  1. Priority 1 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

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

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

    On Next.js: Use the next/script component with an appropriate loading strategy.

    35% of Events & Online Ticketing peers do this.

  3. Priority 3 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    52% of Events & Online Ticketing peers do this.

  4. Priority 4 · Harden

    DNSSEC signed

    Observed: No DS record was found for zola.com at its parent zone, so its DNS answers are not DNSSEC-signed.

    What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

    On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.

    9% of Events & Online Ticketing peers do this.

What zola.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
  • CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.11% of peers
  • HTTP/3 advertisedHTTP/3 advertised.24% of peers

What we saw

Homepage checked
https://www.zola.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-04-17
CDN or edge
Amazon CloudFront
Platform or framework
Next.js
DNS operators
Amazon Route 53
HSTS
max-age 365 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
541 KB, gzip
Images on homepage
55 (webp 211, png 9, 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

Observed 25

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • security.txt published
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own zola.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: zola.com. This profile covers configuration only.

Compare with other Events & Online Ticketing sites