Scan report for tegro.by
4 pages crawled — 3615 words, 113 images and 268 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 39 distinct problems found, counted 135 times across the pages.
Report updated 2026-10-27
Category scores
- Overall
- 81/100
- SEO
- 93/100 · Issues: 9
- Accessibility
- 70/100 · Issues: 24
- Performance
- 93/100 · Issues: 7
- Security
- 0/100 · Issues: 46
- Privacy
- 94/100 · Issues: 5
- HTML validity
- 82/100 · Issues: 16
- Forms
- 70/100 · Issues: 16
- Links
- 94/100 · Issues: 8
- Console
- Not measured
- Infrastructure
- 100/100 · No issues found
- Mobile
- 100/100 · No issues found
- Images
- 97/100 · Issues: 4
Quick Wins
High-impact, low-effort fixes, ranked by what this scan actually found.
- Give every form a submit control — Visitors can actually send the form.
- Add alt text to the images that are missing it — Search engines can index the images and screen-reader users learn what they show.
- Send a Strict-Transport-Security header — Browsers refuse to fall back to plain HTTP for this domain.
- Update the copyright year — The footer stops telling everyone the site was abandoned.
- Replace the legacy doctype with <!DOCTYPE html> — The page renders in standards mode in every browser.
- Send X-Content-Type-Options: nosniff — Browsers stop guessing content types and executing files as scripts.
What the site checks found
- Critical — Security — Files a deploy should never publish are readable over the web: /.git/config, /.git/HEAD.
- 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.16.1, x-powered-by: PHP/5.5.38.
- 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 Google Tag Manager with no consent layer anywhere in the markup — under the GDPR and the ePrivacy Directive those tags need consent before they run.
Other sites scanned recently
Scan your own site
Get the same diagnostic report for your website in under a minute.