carwow.co.uk

Readiness by lane

Green: carwow.co.uk. Thin bar: Cars & Automotive peer median.

Priority fixes for carwow.co.uk

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   91% of Cars & Automotive peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

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

   31% of Cars & Automotive peers do this.

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

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

   30% of Cars & Automotive peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   8.9% of Cars & Automotive peers do this.

   Guide: A Practical Website Health Check for Owners

What carwow.co.uk already does well

Practices fewer than half of Cars & Automotive peers use.

• Nameservers spread across providersNameservers spread across more than one operator.14% of peers
• Referrer-Policy setReferrer-Policy present.26% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.41% of peers

What we saw

Homepage checked

https://www.carwow.co.uk/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Certainly, 29-day validity, expiring 2026-11-12

CDN or edge

Fastly, Heroku

DNS operators

4 self-run or other nameserver domains

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

351 KB, gzip

Images on homepage

135 (svg 71, jpg 37, avif 4)

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

• anwb.nl83
• carbuzz.com83
• cardekho.com83
• carwow.de83
• carwow.es83

Cars & Automotive readiness benchmark