Website readiness profile · Snapshot 23 October 2026
gofo.com
gofo.com's public homepage, certificate and DNS checked against 31 practices and compared with 185 Postage & Courier Services sites.
- Readiness index
- 54/100
- Ahead of
- 29%
- Practices observed
- 12/29
- Popularity band
- Top 50K
Postage & Courier Services median 60
of measured Postage & Courier Services sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: gofo.com. Thin bar: Postage & Courier Services peer median.
Enable
69/100
Peers 75
Harden
48/100
Peers 56
Accelerate
50/100
Peers 53
Recover
0/100
Peers 12
Priority fixes for gofo.com
Ordered by impact and by how common each practice is among peers.
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.
39% of Postage & Courier Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 14 days, 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.
44% of Postage & Courier Services peers do this.
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script without async or defer.
What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
39% of Postage & Courier Services peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · 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.
61% of Postage & Courier Services peers do this.
What we saw
- Homepage checked
- https://www.gofo.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 199-day validity, expiring 2026-12-13
- CDN or edge
- Amazon CloudFront
- Platform or framework
- Nuxt
- DNS operators
- Amazon Route 53
- DMARC policy
- p=quarantine
- Homepage HTML
- 8 KB, br
- Images on homepage
- 0
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 17
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 12
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own gofo.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: gofo.com. This profile covers configuration only.