Scan report
https://aimangatranslator.app/
Scanned 9/15/2026, 11:35:20 AM
80
/ 100
Overall readiness
Strong agentic-web readiness
Grade B2 critical issues and 4 recommended fixes found.
Agent Readiness
100/100
llms.txt / agents.md quality — Pass, scored 100 of 100
Evidence: llms.txt found (5048 chars), well-formed
Server-rendered content — Pass, scored 100 of 100
Evidence: 5864 chars of visible text in the server-rendered HTML
Spec: Google: JavaScript SEO basicsOpenAI: crawlers and bots
Structured data — Pass, scored 100 of 100
Evidence: 4 JSON-LD block(s) found with a valid @type
Spec: JSON-LD 1.1 (W3C Recommendation)Google: structured data policies
Machine-readable metadata — Pass, scored 100 of 100
Evidence: 3/3 core metadata tags present
SEO
100/100
robots.txt present — Pass, scored 100 of 100
Evidence: robots.txt present and not blocking the whole site
XML sitemap — Pass, scored 100 of 100
Evidence: sitemap.xml found
Spec: Sitemaps XML protocol
Title & meta description — Pass, scored 100 of 100
Evidence: Title 50 chars, description 136 chars
Open Graph tags — Pass, scored 100 of 100
Evidence: 3/3 core Open Graph tags present
Spec: The Open Graph protocol
Canonical URL — Pass, scored 100 of 100
Evidence: Canonical points to https://aimangatranslator.app/
Performance & Accessibility
99/100
HTML payload weight — Pass, scored 95 of 100
Evidence: HTML document is 196 KB
Render-blocking resources — Pass, scored 100 of 100
Evidence: 0 render-blocking script(s) in <head>
Image alt text — Pass, scored 100 of 100
Evidence: All 16 image(s) have alt text (15 described, 1 marked decorative)
Semantic landmarks — Pass, scored 100 of 100
Evidence: All core landmarks present (header, nav, main, footer, h1)
HTML lang attribute — Pass, scored 100 of 100
Evidence: <html lang="en"> present
Security
44/100
HTTPS — Pass, scored 100 of 100
Evidence: Page served over HTTPS
Spec: RFC 9110: HTTP Semantics
HSTS header — Fail, scored 0 of 100
Evidence: No Strict-Transport-Security header
Fix: Send an HSTS header to force HTTPS for returning visitors.
Strict-Transport-Security: max-age=31536000; includeSubDomainsContent-Security-Policy — Fail, scored 0 of 100
Evidence: No Content-Security-Policy header
Fix: Add a Content-Security-Policy to mitigate XSS and data-injection attacks.
Content-Security-Policy: default-src 'self'; img-src 'self' data:; script-src 'self'X-Content-Type-Options — Fail, scored 0 of 100
Evidence: No X-Content-Type-Options header
Fix: Send X-Content-Type-Options: nosniff to stop MIME-type sniffing.
X-Content-Type-Options: nosniffReferrer-Policy — Fail, scored 0 of 100
Evidence: No Referrer-Policy header
Fix: Set a Referrer-Policy to control how much referrer information leaks.
Referrer-Policy: strict-origin-when-cross-originSpec: Referrer Policy (W3C)
No mixed content — Pass, scored 100 of 100
Evidence: No insecure http:// resource references found
Spec: Mixed Content (W3C)
Cookie security flags — Pass, scored 100 of 100
Evidence: No Set-Cookie headers
Critical issues
Fix these first
HSTS header
security
No Strict-Transport-Security header
Content-Security-Policy
security
No Content-Security-Policy header
Recommended fixes
Ranked by impact
HSTS headersecurityHigh impactLow effort
Why: No Strict-Transport-Security header
Fix: Send an HSTS header to force HTTPS for returning visitors.
Strict-Transport-Security: max-age=31536000; includeSubDomainsContent-Security-PolicysecurityHigh impactMed effort
Why: No Content-Security-Policy header
Fix: Add a Content-Security-Policy to mitigate XSS and data-injection attacks.
Content-Security-Policy: default-src 'self'; img-src 'self' data:; script-src 'self'X-Content-Type-OptionssecurityMed impactLow effort
Why: No X-Content-Type-Options header
Fix: Send X-Content-Type-Options: nosniff to stop MIME-type sniffing.
X-Content-Type-Options: nosniffReferrer-PolicysecurityMed impactLow effort
Why: No Referrer-Policy header
Fix: Set a Referrer-Policy to control how much referrer information leaks.
Referrer-Policy: strict-origin-when-cross-origin