mk.ru

Readiness by lane

Green: mk.ru. Thin bar: News & Media peer median.

Priority fixes for mk.ru

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.

   93% of News & Media 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 7 days, 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.

   60% of News & Media peers do this.

   Guide: Browser Caching Guide for Website Owners

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

   35% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

   44% of News & Media peers do this.

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

What mk.ru already does well

Practices fewer than half of News & Media peers use.

• Content Security Policy presentContent-Security-Policy present.29% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers

What we saw

Homepage checked

https://www.mk.ru/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2027-04-01

DNS operators

RU-CENTER DNS

DMARC policy

p=reject

Homepage HTML

466 KB, gzip

Images on homepage

174 (jpg 313, png 56, svg 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 News & Media sites

• makfax.com.mk61
• maremmaoggi.net61
• mediacourant.nl61
• mstar.com.my61
• ndtv.in61

News & Media readiness benchmark