STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

tsp.gov

tsp.gov's public homepage, certificate and DNS checked against 31 practices and compared with 203 Insurance & Financial Planning sites.

Readiness index
82/100

Insurance & Financial Planning median 69

Ahead of
87%

of measured Insurance & Financial Planning sites

Practices observed
23/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:56:02 UTC from one location. How we measure

Readiness by lane

Green: tsp.gov. Thin bar: Insurance & Financial Planning peer median.

Enable

95/100

Peers 81

Harden

89/100

Peers 64

Accelerate

59/100

Peers 60

Recover

0/100

Peers 19

Priority fixes for tsp.gov

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

  1. Priority 1 · Accelerate

    Modern image formats in use

    Observed: The homepage had 14 images and none used WebP or AVIF.

    Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

    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.

    43% of Insurance & Financial Planning peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 14 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.

    67% of Insurance & Financial Planning peers do this.

  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 Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

    18% of Insurance & Financial Planning peers do this.

  4. Priority 4 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    9.9% of Insurance & Financial Planning peers do this.

What tsp.gov already does well

Practices fewer than half of Insurance & Financial Planning peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.15% of peers
  • DNSSEC signedDNSSEC delegation (DS record) present.17% of peers
  • Referrer-Policy setReferrer-Policy present.39% of peers

What we saw

Homepage checked
https://www.tsp.gov/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2026-11-13
CDN or edge
Amazon CloudFront
DNS operators
Cloudflare
HSTS
max-age 730 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
104 KB, br
Images on homepage
14 (svg 9, png 3, jpg 2)

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

Observed 23

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DNSSEC signed
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own tsp.gov?

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: tsp.gov. This profile covers configuration only.

Compare with other Insurance & Financial Planning sites