STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

prodadvizh.com

prodadvizh.com's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index
48/100

Web Tools median 67

Ahead of
6.1%

of measured Web Tools sites

Practices observed
11/28

3 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:33:24 UTC from one location. How we measure

Readiness by lane

Green: prodadvizh.com. Thin bar: Web Tools peer median.

Enable

33/100

Peers 84

Harden

40/100

Peers 55

Accelerate

87/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for prodadvizh.com

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

  1. Priority 1 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    93% of Web Tools peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  2. Priority 2 · 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.

    73% of Web Tools peers do this.

  3. Priority 3 · Enable

    Meta description written

    Observed: The homepage had no meta description.

    What to do: Write a short, specific description of the page for people, not a list of keywords.

    96% of Web Tools peers do this.

  4. Priority 4 · Harden

    HSTS kept for at least a year

    Observed: The homepage response did not include a Strict-Transport-Security header.

    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.

    30% of Web Tools peers do this.

What prodadvizh.com already does well

Practices fewer than half of Web Tools peers use.

  • Content Security Policy presentContent-Security-Policy present.15% of peers

What we saw

Homepage checked
https://prodadvizh.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Let's Encrypt, 89-day validity, expiring 2026-11-15
DNS operators
1 self-run or other nameserver domain
Homepage HTML
1 KB, gzip
Images on homepage
1 (png 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

Observed 11

  • 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>
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Not measured 3

  • HTTP requests move to HTTPS
  • Modern image formats in use
  • Offscreen images lazy-loaded

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

Compare with other Web Tools sites