Scan report for petosevic.com
5 pages crawled — 2103 words, 22 images and 340 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 30 distinct problems found, counted 71 times across the pages.
Report updated 2026-10-28
Category scores
- Overall
- 92/100
- SEO
- 81/100 · Issues: 20
- Accessibility
- 90/100 · Issues: 10
- Performance
- 86/100 · Issues: 13
- Security
- 63/100 · Issues: 22
- Privacy
- 97/100 · Issues: 1
- HTML validity
- 98/100 · Issues: 1
- Forms
- 100/100 · No issues found
- Links
- 90/100 · Issues: 2
- Console
- 98/100 · Issues: 1
- Infrastructure
- 100/100 · No issues found
- Mobile
- 98/100 · Issues: 1
- Images
- 100/100 · No issues found
Quick Wins
High-impact, low-effort fixes, ranked by what this scan actually found.
- Write meta descriptions for the pages without one — Google stops inventing snippets and shows the copy you wrote.
- Give every iframe a title — Screen-reader users hear what each embedded frame contains.
- 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.
- Add rel="noopener" to target="_blank" links — External tabs can no longer reach back into the opener window.
- Add integrity hashes to the CDN scripts and stylesheets — A compromised CDN can no longer run whatever it likes on the site.
- Introduce a Content-Security-Policy — Injected scripts stop being able to run.
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.
- Medium — Links — Internal links leading to an error page: 2 of 10 checked.
- Low — Security — The zone is not signed with DNSSEC, so a forged DNS answer cannot be detected.
- Low — Privacy — The site loads Google Analytics, 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.