Report loading
ghostpen.us
Preparing the full page inventory and screenshots.
Score
84
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
Good
Health Score
Here's the simple version
84/100 - good. Good enough to understand, not good enough to ignore. _GhostPen_ suffers from significant accessibility failures that impede user engagement and risk regulatory non-compliance. The website establishes a strong, premium brand identity through a cohesive dark-mode aesthetic and modern visual elements. The product value proposition is clear, supported by effective risk-reversal micro-copy such as "No credit card" and "Cancel anytime," which successfully reduces user friction at the point of conversion. Furthermore, the site is well-optimized for AI retrieval, with a clear heading hierarchy and a robots.txt configuration that allows major AI crawlers to index content for answer-engine discovery. A high-priority accessibility issue exists regarding color contrast ratios, where several elements fail to meet the minimum WCAG 2 AA thresholds. This lack of contrast makes high-priority text difficult to read for many users and undermines the professional polish of the interface. Additionally, the site lacks a visible privacy policy link on the homepage, creating a gap in necessary trust signals and regulatory compliance. There is a major opportunity to capture more "answer engine" market share by expanding commercial AI-search coverage. While the site is technically accessible to crawlers, it currently lacks dedicated, crawlable pages for pricing, detailed product catalogs, and comprehensive FAQs. Developing these content clusters will allow AI agents to more effectively answer specific buyer prompts regarding cost and use cases, directly driving higher-intent traffic. To stabilize the user experience and improve compliance, the following actions are required within the next 30 days: - Remediate all high-priority color contrast failures to meet WCAG 2 AA standards. - Implement a visible, permanent link to the privacy policy in the site footer. - Resolve the misconfigured email authentication DNS records to prevent domain spoofing.
Good
Health score
Launch blockers
No major launch blockers found.
The rest of the report is a fix queue, not a reason to panic.
Fix first
Start with the top 3.
These are the items most likely to improve trust, speed, or conversion.
Best next step
Hand the fix list to your builder or AI agent.
The technical detail is still here when they need evidence.
Biggest area to improve: Performance, which mostly means speed and loading experience.
The full report has all the proof. This is the owner-friendly version of what to do first.
Plain-English reason
This affects whether everyone can use the site. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Element matching `.p-2 > .text-\[8\.5px\].uppercase.tracking-wider` has contrast ratio 2.53; 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
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 2.53 (foreground color: #55556d, background color: #131323, font size: 6.4pt (8.5px), font weight: normal). Expected contrast ratio of 4.5:1
Plain-English reason
This affects clarity and completeness of the content. PageLens marked it as worth fixing so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Keep one <h1> for the primary heading. Demote the others to <h2> or lower as appropriate.
This page has 2 <h1> tags. Best practice is exactly one H1 per page for clear document hierarchy.
Plain-English reason
This affects speed and loading experience. PageLens marked it as worth fixing so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Optimise the LCP element: serve responsive image sizes (srcset/sizes), set fetchpriority="high" on the hero image, preconnect to the image origin, and ensure the LCP element isn't blocked by render-blocking scripts (see PERF-015) or late-mounting React components.
LCP measures how quickly the largest visible element finishes rendering. Google flags anything above 2.5s as needing improvement and anything above 4s as poor — both signal a slow first impression to users and rank against the page in CrUX.
Same data as the full report, grouped by what a non-technical owner should do with it.
High-impact fixes that should usually be tackled before anything else.
Important fixes that may need more development time or a design decision.
Nothing in this bucket.
Polish and lower-priority work. Useful, but not where to start.
Need the detail?
The full report still has every finding, evidence, rule ID, filters, screenshots, and technical panels.
