sportstiming.dk

Readiness by lane

Green: sportstiming.dk. Thin bar: Events & Online Ticketing peer median.

Priority fixes for sportstiming.dk

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

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

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

   42% of Events & Online Ticketing peers do this.

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

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   65% of Events & Online Ticketing peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What sportstiming.dk 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
• DNSSEC signedDNSSEC delegation (DS record) present.9% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers

What we saw

Homepage checked

https://www.sportstiming.dk/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-23

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 30 days

DMARC policy

p=quarantine

Homepage HTML

109 KB, gzip

Images on homepage

23 (png 16, jpg 3, gif 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

Compare with other Events & Online Ticketing sites

• brocabrac.fr64
• estatesales.net64
• resy.com65
• ticketmaster.de66
• ticketmaster.nl66

Events & Online Ticketing readiness benchmark