Report loading
www.inner-void.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Excellent
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
InnerVoid maintains a high-performance digital presence, but critical security vulnerabilities in email authentication and content delivery policies pose a significant risk to brand integrity.
The site excels in technical performance and visual identity. On desktop, the platform demonstrates excellent Core Web Vitals, specifically achieving a highly optimized Largest Contentful Paint (LCP) of 540ms. The brand identity is sophisticated, utilizing a premium dark theme and a well-structured heading hierarchy that supports both user experience and search engine crawling. Furthermore, the implementation of comprehensive SoftwareApplication structured data provides a strong foundation for rich search snippets and AI-driven discovery.
The highest-impact weakness is a lack of robust security configurations. The domain is currently vulnerable to spoofing due to misconfigured or missing SPF, DMARC, and DKIM email authentication records. Additionally, the desktop Content-Security-Policy (CSP) is weak, utilizing insecure unsafe-inline directives and multi-tenant Firebase hosting, which increases the attack surface for cross-site scripting.
The biggest opportunity lies in optimizing for the next generation of search and discovery. While the site uses advanced Schema.org markup, it currently lacks an llms.txt file, meaning AI agents like ChatGPT and Claude cannot accurately parse the business's core value proposition. Implementing this, alongside more granular schema details such as applicationSubCategory, will ensure InnerVoid is positioned as a primary authority in AI-generated answers and specialized search results.
To secure the platform and improve accessibility, the following actions must be prioritized in the first 30 days:
unsafe-inline directives.aria-expanded state for screen reader compatibility.5 highest-impact findings, ranked.
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 3.35 (foreground color: #6a6965, background color: #141414, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.iv-nav-inner > div > a:nth-child(1)` has contrast ratio 3.35; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
On /guides/en
Google typically displays 50–60 characters of the title in search results. A title under 30 chars usually fails to set context.
How to fix: Expand the title to 30–60 characters with the page topic and a brand suffix, e.g. <title>Page topic — Brand</title>.
On /guides/en
Open Graph tags drive how the page appears when shared on Slack, LinkedIn, Facebook, WhatsApp, iMessage and most other platforms. Without them, shares fall back to the URL or a stripped preview.
How to fix: Add to <head>: <meta property="og:title" content="…"> <meta property="og:description" content="…"> <meta property="og:image" content="https://…/social-card.png">
On /guides/en
CSP contains insecure directives: script-src 'unsafe-inline' without nonce, *.firebaseapp.com in script-src (multi-tenant hosting), *.firebase.com in script-src, *.firebaseio.com in connect-src, *.firebaseio.com in connect-src. These weaken XSS protections.
How to fix: Use nonce-based or hash-based CSP for scripts. Remove 'unsafe-eval' if possible. Replace dangerous wildcard hosts with specific origins.
On /home-en
Google's recommended snippet length is 120–160 characters. Under 70 chars usually leaves CTR on the table.
How to fix: Expand the description to 120–160 chars covering the page's value proposition and a primary CTA.
On /guides/en