Report loading
www.inner-void.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Good
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
The most critical finding is a severe security vulnerability where the login and password form submits via GET, causing sensitive user credentials to be exposed in plain text within the browser address bar and server logs.
InnerVoid maintains a strong, cohesive visual brand identity through its "Private Cognitive Engineering" aesthetic, utilizing a sophisticated dark palette with neon accents. The site achieves high-quality Core Web Vitals on desktop, with a Largest Contentful Paint (LCP) that falls within the "Good" threshold, ensuring a responsive initial user experience.
However, the site suffers from fundamental security and structural flaws that undermine user trust and search visibility. Beyond the credential exposure, the absence of an H1 heading and descriptive <title> tags prevents search engines from indexing the service effectively. Furthermore, the desktop experience is hampered by a massive 3.5 MB page weight and an excessive DOM size of nearly 3,000 nodes, which threatens long-term performance stability.
There is a significant opportunity to improve both conversion and discoverability by optimizing the technical SEO and social presence. Implementing Open Graph tags and a descriptive, keyword-rich title will ensure that shared links appear professional on platforms like LinkedIn or X. Additionally, publishing an llms.txt file would position the brand to be accurately represented by AI discovery engines, a vital move for a modern cognitive engineering product.
To mitigate immediate risk and stabilize the platform, the following must be addressed in the first 30 days:
GET to POST to secure user credentials.<title> and an <h1> tag to establish SEO context.5 highest-impact findings, ranked.
A form containing a password field uses `method="GET"` (or no method attribute, which defaults to GET). This causes credentials to appear in the browser address bar, browsing history, server access logs, and any analytics or proxy that records URLs.
How to fix: Change the form to `method="POST"`. Ensure the `action` URL uses HTTPS. Example: `<form method="POST" action="/api/login">`.
On /
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /
Third-party scripts (analytics, embeds, ad pixels, font CDNs, chat widgets) are hosted outside your control and often render-block, INP-block, or both. Each adds DNS resolution + TLS overhead and can fail independently of your own infrastructure.
How to fix: Audit every third-party tag: drop ones you're no longer measuring, switch from <script> to async/defer, route analytics through a single tag manager, and self-host fonts as woff2 (most font CDNs add 50-150 KB per family).
On /
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.22 (foreground color: #68676d, background color: #17151e, font size: 10.0pt (13.3333px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `button[onclick="EchoAuth._switchLang('de')"]` has contrast ratio 3.22; 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 /
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 /