tw.live

Readiness by lane

Green: tw.live. Thin bar: GPS Navigation & Maps peer median.

Priority fixes for tw.live

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.tw.live.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 3 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 · 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

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

   28% of GPS Navigation & Maps peers do this.

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

What tw.live already does well

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

• Referrer-Policy setReferrer-Policy present.21% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.38% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.43% of peers

What we saw

Homepage checked

https://tw.live/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-03

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains

Homepage HTML

33 KB, br

Images on homepage

3 (svg 3)

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

• fogos.pt75
• garmin.com77
• komoot.com77
• times-info.net74
• tuttocitta.it74

GPS Navigation & Maps readiness benchmark