mci.ir

Readiness by lane

Green: mci.ir. Thin bar: Telecommunications & Internet peer median.

Priority fixes for mci.ir

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.

   81% of Telecommunications & Internet 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 · 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.

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 23 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   66% of Telecommunications & Internet peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 4 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.

   37% of Telecommunications & Internet peers do this.

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

What mci.ir already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Reachable over IPv6IPv6 address published.33% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://mci.ir/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Asseco Data Systems S.A., 364-day validity, expiring 2027-02-05

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

209 KB, gzip

Images on homepage

23 (webp 8, jpg 4, svg 2)

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 Telecommunications & Internet sites

• free.fr71
• hmd.com71
• jcom.co.jp71
• orange.be71
• telenor.se71

Telecommunications & Internet readiness benchmark