Website readiness profile · Snapshot 23 October 2026
randomus.ru
randomus.ru's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.
- Readiness index
- 68/100
- Ahead of
- 53%
- Practices observed
- 17/29
- Popularity band
- Top 50K
Web Tools median 67
of measured Web Tools sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: randomus.ru. Thin bar: Web Tools peer median.
Enable
64/100
Peers 84
Harden
60/100
Peers 55
Accelerate
87/100
Peers 69
Recover
100/100
Peers 6
Priority fixes for randomus.ru
Ordered by impact and by how common each practice is among peers.
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.
73% of Web Tools peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 2 · 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.
74% of Web Tools peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: No DMARC record was found at _dmarc.randomus.ru.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
23% of Web Tools peers do this.
Priority 4 · 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.
56% of Web Tools peers do this.
What randomus.ru already does well
Practices fewer than half of Web Tools peers use.
- Nameservers spread across providersNameservers spread across more than one operator.6.1% of peers
- Content Security Policy presentContent-Security-Policy present.15% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers
What we saw
- Homepage checked
- https://randomus.ru/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-17
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days
- Homepage HTML
- 36 KB, gzip
- Images on homepage
- 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 17
- 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
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own randomus.ru?
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: randomus.ru. This profile covers configuration only.