STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

t.me

t.me's public homepage, certificate and DNS checked against 31 practices and compared with 193 Social Media & Networking sites.

Readiness index
60/100

Social Media & Networking median 63

Ahead of
38%

of measured Social Media & Networking sites

Practices observed
14/29

2 of 31 could not be measured

Popularity band
Top 1K

Chrome UX Report top-sites list

Measured 2026-10-23 11:25:16 UTC from one location. How we measure

Readiness by lane

Green: t.me. Thin bar: Social Media & Networking peer median.

Enable

56/100

Peers 76

Harden

65/100

Peers 56

Accelerate

59/100

Peers 62

Recover

0/100

Peers 5

Priority fixes for t.me

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

  1. Priority 1 · Enable

    XML sitemap discoverable

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

    Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

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

    64% of Social Media & Networking peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · Accelerate

    Modern image formats in use

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

    34% of Social Media & Networking peers do this.

  3. 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.

    62% of Social Media & Networking peers do this.

  4. Priority 4 · Enable

    Page language declared

    Observed: The homepage <html> element had no lang attribute.

    What to do: Set lang on the html element (for example lang="en") and on any sections in another language.

    86% of Social Media & Networking peers do this.

What t.me already does well

Practices fewer than half of Social Media & Networking peers use.

  • 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.39% of peers
  • Reachable over IPv6IPv6 address published.47% of peers

What we saw

Homepage checked
https://t.me/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
GoDaddy, 397-day validity, expiring 2026-11-22
DNS operators
Google Cloud DNS
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
19 KB, gzip
Images on homepage
11

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 14

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • HTTP/2 negotiated
  • HTML compressed
  • No render-blocking scripts in <head>
  • Reachable over IPv6
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • At most one redirect to the homepage

Not measured 2

  • Static files cached for 30 days or more
  • robots.txt published

Own t.me?

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: t.me. This profile covers configuration only.

Compare with other Social Media & Networking sites