ticketpro.by

Readiness by lane

Green: ticketpro.by. Thin bar: Events & Online Ticketing peer median.

Priority fixes for ticketpro.by

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   90% of Events & Online Ticketing peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 176 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   42% of Events & Online Ticketing peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 176 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   54% of Events & Online Ticketing peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   24% of Events & Online Ticketing peers do this.

   Guide: CDN Guide for Website Owners

What ticketpro.by already does well

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

• Referrer-Policy setReferrer-Policy present.28% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.35% of peers

What we saw

Homepage checked

https://www.ticketpro.by/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Google Trust Services, 89-day validity, expiring 2026-11-25

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

814 KB, gzip

Images on homepage

176 (png 168, jpg 7)

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
• eventticketscenter.com73
• partiful.com74
• tixel.com75

Events & Online Ticketing readiness benchmark