carfax.com

Readiness by lane

Green: carfax.com. Thin bar: Cars & Automotive peer median.

Priority fixes for carfax.com

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   83% of Cars & Automotive peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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

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

   41% of Cars & Automotive peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   45% of Cars & Automotive peers do this.

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

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   55% of Cars & Automotive peers do this.

   Guide: A Practical Website Health Check for Owners

What carfax.com 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
• HTTP/3 advertisedHTTP/3 advertised.30% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.41% of peers

What we saw

Homepage checked

https://www.carfax.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

NS1, plus 1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

86 KB, br

Images on homepage

20 (png 25, svg 14, avif 4, webp 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

• autoviza.fr63
• bama.ir63
• carexpert.com.au63
• carup.se63
• diariomotor.com63

Cars & Automotive readiness benchmark