wifimap.io

Readiness by lane

Green: wifimap.io. Thin bar: GPS Navigation & Maps peer median.

Priority fixes for wifimap.io

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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 25 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 Cloudflare: Cloudflare Polish can convert images to WebP.

   35% of GPS Navigation & Maps peers do this.

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

3. Priority 3 · 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 Cloudflare: Add the header with a response header transform rule.

   50% of GPS Navigation & Maps peers do this.

   Guide: A Practical Website Health Check for Owners

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

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   35% of GPS Navigation & Maps peers do this.

   Guide: CDN Guide for Website Owners

What wifimap.io already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, letsencrypt.org, pki.goog and others.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.38% of peers
• Reachable over IPv6IPv6 address published.41% of peers

What we saw

Homepage checked

https://www.wifimap.io/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-02

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

263 KB, br

Images on homepage

25

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.kz72
• gasbuddy.com73
• outdooractive.com72
• radarua.com73
• vesselfinder.com74

GPS Navigation & Maps readiness benchmark