port.hu

Readiness by lane

Green: port.hu. Thin bar: Events & Online Ticketing peer median.

Priority fixes for port.hu

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (556 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

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

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Accelerate

   HTTP/2 negotiated

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

   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.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for port.hu 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.

   Guide: A Practical Website Health Check for Owners

What port.hu already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.7.2% of peers
• Modern image formats in useWebP or AVIF images detected.42% of peers

What we saw

Homepage checked

https://port.hu/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-19

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=none

Homepage HTML

556 KB, uncompressed

Images on homepage

143 (webp 242, jpg 58, svg 3, png 1)

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

• agilityplaza.com46
• jegy.hu46
• ticket.co.jp46
• tonamel.com46
• veloxtickets.com47

Events & Online Ticketing readiness benchmark