subaru.jp

Readiness by lane

Green: subaru.jp. Thin bar: Cars & Automotive peer median.

Priority fixes for subaru.jp

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

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

   Guide: CDN Guide for Website Owners

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.

   41% of Cars & Automotive peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   55% of Cars & Automotive peers do this.

   Guide: Browser Caching Guide for Website Owners

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

What subaru.jp already does well

Practices fewer than half of Cars & Automotive peers use.

• Content Security Policy presentContent-Security-Policy present.31% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://www.subaru.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 365-day validity, expiring 2027-01-14

DNS operators

Akamai Edge DNS

DMARC policy

p=reject

Homepage HTML

54 KB, gzip

Images on homepage

54 (webp 52, svg 10)

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

• ocasionplus.com66
• petrolprices.com66
• subaru.com66
• tvsmotor.com66
• volkswagen.de66

Cars & Automotive readiness benchmark