Website readiness profile · Snapshot 23 October 2026
geocaching.com
geocaching.com's public homepage, certificate and DNS checked against 31 practices and compared with 73 GPS Navigation & Maps sites.
- Readiness index
- 68/100
- Ahead of
- 49%
- Practices observed
- 19/31
- Popularity band
- Top 10K
GPS Navigation & Maps median 68
of measured GPS Navigation & Maps sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: geocaching.com. Thin bar: GPS Navigation & Maps peer median.
Enable
77/100
Peers 81
Harden
74/100
Peers 57
Accelerate
48/100
Peers 63
Recover
100/100
Peers 14
Priority fixes for geocaching.com
Ordered by impact and by how common each practice is among peers.
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.
86% of GPS Navigation & Maps peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 7 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.
35% of GPS Navigation & Maps peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
71% of GPS Navigation & Maps peers do this.
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 7 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.
What geocaching.com already does well
Practices fewer than half of GPS Navigation & Maps peers use.
- Nameservers spread across providersNameservers spread across more than one operator.14% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.38% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.38% of peers
What we saw
- Homepage checked
- https://www.geocaching.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3
- Certificate
- Let's Encrypt, 44-day validity, expiring 2026-11-20
- DNS operators
- DNS Made Easy, plus 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 28 KB, gzip
- Images on homepage
- 7 (svg 4, png 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
Not observed 12
Observed 19
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own geocaching.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: geocaching.com. This profile covers configuration only.