mapion.co.jp

Readiness by lane

Green: mapion.co.jp. Thin bar: GPS Navigation & Maps peer median.

Priority fixes for mapion.co.jp

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.

   38% of GPS Navigation & Maps 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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for mapion.co.jp was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   38% of GPS Navigation & Maps peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 43 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   60% of GPS Navigation & Maps peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GlobalSign nv-sa had a 199-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   71% of GPS Navigation & Maps peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What mapion.co.jp already does well

Practices fewer than half of GPS Navigation & Maps peers use.

• Modern image formats in useWebP or AVIF images detected.35% of peers

What we saw

Homepage checked

https://www.mapion.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2026-11-12

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

51 KB, gzip

Images on homepage

43 (png 39, webp 9, gif 2, jpg 1)

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 GPS Navigation & Maps sites

• 2gis.ru67
• alerts.in.ua64
• alltrails.com66
• czynaczas.pl59
• mapquest.com63

GPS Navigation & Maps readiness benchmark