bus.com.ua

Readiness by lane

Green: bus.com.ua. Thin bar: Trains & Public Transport peer median.

Priority fixes for bus.com.ua

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://bus.com.ua/ 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.

   95% of Trains & Public Transport peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   95% of Trains & Public Transport peers do this.

   Guide: Responsive Web Design Checklist for Real Devices

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.

   41% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   82% of Trains & Public Transport peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

What bus.com.ua already does well

Practices fewer than half of Trains & Public Transport peers use.

• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked

http://bus.com.ua/

Homepage response

HTTP 200

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

42 KB, gzip

Images on homepage

108 (png 70, gif 37)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

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

Compare with other Trains & Public Transport sites

• imhd.sk36
• jrkyushu-timetable.jp22
• mu-kgt.ru36
• ratbv.ro36
• tobus.jp29

Trains & Public Transport readiness benchmark