bilbasen.dk

Readiness by lane

Green: bilbasen.dk. Thin bar: Cars & Automotive peer median.

Priority fixes for bilbasen.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: 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.

   41% of Cars & Automotive 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 21 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.

   47% of Cars & Automotive peers do this.

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

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   63% of Cars & Automotive peers do this.

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   31% of Cars & Automotive peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What bilbasen.dk already does well

Practices fewer than half of Cars & Automotive peers use.

• security.txt publishedsecurity.txt with a contact found.8.9% of peers
• HTTP/3 advertisedHTTP/3 advertised.30% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers

What we saw

Homepage checked

https://www.bilbasen.dk/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-01-11

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

98 KB, gzip

Images on homepage

21 (jpg 16, svg 3, png 2)

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 Cars & Automotive sites

• autoscout24.de73
• autoscout24.fr73
• autoscout24.nl73
• caminhoesecarretas.com.br73
• cupraoficial.mx73

Cars & Automotive readiness benchmark