Scan report for mobipay.by
5 pages crawled — 26714 words, 48 images and 102 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 28 distinct problems found, counted 83 times across the pages.
Report updated 2026-10-27
Category scores
- Overall
- 91/100
- SEO
- 78/100 · Issues: 12
- Accessibility
- 96/100 · Issues: 6
- Performance
- 84/100 · Issues: 19
- Security
- 58/100 · Issues: 38
- Privacy
- 97/100 · Issues: 1
- HTML validity
- 93/100 · Issues: 7
- Forms
- 100/100 · No issues found
- Links
- 100/100 · No issues found
- Console
- Not measured
- Infrastructure
- 100/100 · No issues found
- Mobile
- 100/100 · No issues found
- Images
- 100/100 · No issues found
Quick Wins
High-impact, low-effort fixes, ranked by what this scan actually found.
- Send a Strict-Transport-Security header — Browsers refuse to fall back to plain HTTP for this domain.
- Add an H1 heading — Both readers and crawlers get a clear statement of what the page is about.
- 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.
- Preconnect to the origins the page loads assets from — The DNS, TCP and TLS work for the other origins happens while the HTML is still parsing.
What the site checks found
- Low — Performance — The HTML is sent with no Cache-Control, Expires, ETag or Last-Modified — every visit re-downloads it in full.
- 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 — Security — No /.well-known/security.txt — anyone who finds a vulnerability has to guess where to report it.
- 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 — Privacy — The site loads Meta Pixel with no consent layer anywhere in the markup — under the GDPR and the ePrivacy Directive those tags need consent before they run.
- Medium — SEO — The sitemap lists 2 pages that are not meant to be indexed — noindex, an error status or another canonical: /privacypolicy/, /faq/.
Other sites scanned recently
Scan your own site
Get the same diagnostic report for your website in under a minute.