STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

tdgall.com

tdgall.com's public homepage, certificate and DNS checked against 31 practices and compared with 377 Forums & Communities sites.

Readiness index
42/100

Forums & Communities median 62

Ahead of
7.7%

of measured Forums & Communities sites

Practices observed
11/31

0 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 12:10:04 UTC from one location. How we measure

Readiness by lane

Green: tdgall.com. Thin bar: Forums & Communities peer median.

Enable

46/100

Peers 74

Harden

34/100

Peers 54

Accelerate

53/100

Peers 60

Recover

0/100

Peers 7

Priority fixes for tdgall.com

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

  1. Priority 1 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

    87% of Forums & Communities peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

    88% of Forums & Communities peers do this.

  3. Priority 3 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    61% of Forums & Communities peers do this.

  4. Priority 4 · Harden

    HSTS kept for at least a year

    Observed: Strict-Transport-Security was sent with a max-age of 30 days, below the one-year benchmark.

    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.

    28% of Forums & Communities peers do this.

What we saw

Homepage checked
https://tdgall.com/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-05
CDN or edge
Cloudflare
DNS operators
Cloudflare
HSTS
max-age 30 days
Homepage HTML
85 KB, gzip
Images on homepage
49 (png 27, gif 22)

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

Own tdgall.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: tdgall.com. This profile covers configuration only.

Compare with other Forums & Communities sites