ati.su

Readiness by lane

Green: ati.su. Thin bar: Business Tools peer median.

Priority fixes for ati.su

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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.

   85% of Business Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 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.

   45% of Business Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

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

   42% of Business Tools peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   46% of Business Tools peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What ati.su already does well

Practices fewer than half of Business Tools peers use.

• Content Security Policy presentContent-Security-Policy present.28% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.42% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://ati.su/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2027-03-07

DNS operators

RU-CENTER DNS

HSTS

max-age 0 days

DMARC policy

p=quarantine

Homepage HTML

415 KB, br

Images on homepage

55 (svg 50, jpg 17, gif 2, 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

Compare with other Business Tools sites

• autoconvert.co.uk64
• bouncy.ai64
• cloudsign.jp63
• livehealth.solutions63
• reservo.cl64

Business Tools readiness benchmark