Scan report for mtravel.by
1 pages crawled — 0 words, 0 images and 0 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 33 distinct problems found, counted 34 times across the pages.
Report updated 2026-10-30
Category scores
- Overall
- 84/100
- SEO
- 46/100 · Issues: 10
- Accessibility
- 64/100 · Issues: 3
- Performance
- 97/100 · Issues: 1
- Security
- 58/100 · Issues: 10
- Privacy
- 88/100 · Issues: 2
- HTML validity
- 97/100 · Issues: 1
- Forms
- 100/100 · No issues found
- Links
- 91/100 · Issues: 1
- Console
- 82/100 · Issues: 2
- Infrastructure
- 94/100 · Issues: 2
- Mobile
- 88/100 · Issues: 2
- Images
- 100/100 · No issues found
Quick Wins
High-impact, low-effort fixes, ranked by what this scan actually found.
- Add an H1 heading — Both readers and crawlers get a clear statement of what the page is about.
- Write meta descriptions for the pages without one — Google stops inventing snippets and shows the copy you wrote.
- Send X-Content-Type-Options: nosniff — Browsers stop guessing content types and executing files as scripts.
- Send an X-Frame-Options header — The site cannot be framed for click-jacking.
- Send a Referrer-Policy header — Internal URLs stop leaking to third-party sites.
- Add a favicon — The site gets its own icon in tabs, bookmarks and history.
What the site checks found
- Medium — SEO — Both www.mtravel.by and the canonical host serve the site with HTTP 200 — the whole site exists at two addresses.
- Low — Security — No /.well-known/security.txt — anyone who finds a vulnerability has to guess where to report it.
- Low — Security — Response headers publish exact software versions: server: nginx/1.30.6, x-powered-by: PHP/5.3.29.
- Medium — Security — No DMARC record at _dmarc — nothing tells receiving servers what to do with mail that fails the SPF check.
- Low — Security — No CAA record — any certificate authority may issue a certificate for this domain.
- Low — Security — The zone is not signed with DNSSEC, so a forged DNS answer cannot be detected.
- Low — Performance — The HTML is compressed with gzip but not with Brotli, which every current browser accepts and which is typically 15–20% smaller.
- Low — Privacy — The site loads Yandex Metrica with no consent layer anywhere in the markup — under the GDPR and the ePrivacy Directive those tags need consent before they run.
- Medium — Privacy — None of the scanned pages links a privacy policy (missing: privacy, terms, imprint).
- Low — Infrastructure — Requests from outside a browser are answered by bot protection rather than by the site, so the pages and files in this report were read in a real browser and the checks that cannot be asked that way are reported as not checked.
Other sites scanned recently
Scan your own site
Get the same diagnostic report for your website in under a minute.