efteling.com

Readiness by lane

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

Priority fixes for efteling.com

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

1. 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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 23 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.

   On Next.js: The next/image component serves optimized formats automatically.

   42% of Events & Online Ticketing peers do this.

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

3. Priority 3 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

   97% of Events & Online Ticketing peers do this.

   Guide: Technical SEO Audit: A Practical Owner’s Guide

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

   Guide: Control Third-Party Scripts Before They Control Your Page

What efteling.com 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
• DNSSEC signedDNSSEC delegation (DS record) present.9% of peers
• Content Security Policy presentContent-Security-Policy present.30% of peers

What we saw

Homepage checked

https://www.efteling.com/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 396-day validity, expiring 2027-03-22

CDN or edge

Amazon CloudFront

Platform or framework

Next.js, Sitecore

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

254 KB, gzip

Images on homepage

23

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

• beauty-istanbul.com70
• cinema-city.co.il70
• ingresso.com70
• tablecheck.com70
• tuboleta.com71

Events & Online Ticketing readiness benchmark