STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

samanehha.com

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

Readiness index
35/100

Web Tools median 67

Ahead of
1.2%

of measured Web Tools sites

Practices observed
9/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:52:20 UTC from one location. How we measure

Readiness by lane

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

Enable

69/100

Peers 84

Harden

25/100

Peers 55

Accelerate

20/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for samanehha.com

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

  1. Priority 1 · Harden

    HTTP requests move to HTTPS

    Observed: A request to http://www.samanehha.com/ was not redirected to HTTPS.

    Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

    What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

    94% of Web Tools peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

  2. Priority 2 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    92% of Web Tools peers do this.

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

    92% of Web Tools peers do this.

  4. Priority 4 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

    What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

    54% of Web Tools peers do this.

What samanehha.com already does well

Practices fewer than half of Web Tools peers use.

  • HSTS kept for at least a yearHSTS with a 365-day max-age.30% of peers

What we saw

Homepage checked
https://www.samanehha.com/
Homepage response
HTTP 200
TLS
TLSv1.2, http/1.1
Certificate
Asseco Data Systems S.A., 198-day validity, expiring 2026-11-20
DNS operators
1 self-run or other nameserver domain
HSTS
max-age 365 days
Homepage HTML
95 KB, gzip
Images on homepage
33 (jpg 21, png 3)

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

Compare with other Web Tools sites