Website readiness profile · Snapshot 23 October 2026

rts.rs

rts.rs's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index: 38/100
Ahead of: <1%
Practices observed: 10/31
Popularity band: Top 50K

Measured 2026-10-23 11:55:30 UTC from one location. How we measure

Readiness by lane

Green: rts.rs. Thin bar: News & Media peer median.

Enable

67/100

Peers 89

Harden

29/100

Peers 56

Accelerate

20/100

Peers 68

Recover

100/100

Peers 11

Priority fixes for rts.rs

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

Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
94% of News & Media peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Guide: CDN Guide for Website Owners
Priority 2 · 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.
93% of News & Media peers do this.
Guide: HTTPS and TLS Guide for Website Owners
Priority 3 · 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.
87% of News & Media peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
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.
60% of News & Media peers do this.
Guide: Browser Caching Guide for Website Owners

What rts.rs already does well

Practices fewer than half of News & Media peers use.

Nameservers spread across providersNameservers spread across more than one operator.11% of peers

What we saw

Homepage checked: https://www.rts.rs/
Homepage response: HTTP 200, after 2 redirects
TLS: TLSv1.2
Certificate: Sectigo, 198-day validity, expiring 2027-01-29
DNS operators: 4 self-run or other nameserver domains
DMARC policy: p=none
Homepage HTML: 434 KB, gzip
Images on homepage: 164 (jpg 140, png 11)

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.

Sectigo (certificate authority)

All 31 checks

Select a gap for the method and fix. How each check works

Observed 10

HTTP requests move to HTTPS
Certificate has more than 14 days left
HTML compressed
robots.txt published
Canonical URL declared
Meta description written
Mobile viewport configured
Social preview image set
Page language declared
Nameservers spread across providers

Own rts.rs?

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.

Re-check rts.rs now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: rts.rs. This profile covers configuration only.

Compare with other News & Media sites

News & Media readiness benchmark

rts.rs

Readiness by lane

Priority fixes for rts.rs

HTTP/2 negotiated

TLS 1.3 negotiated

XML sitemap discoverable

Static files cached for 30 days or more