Report loading
zenidebtfree.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Poor
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
Summary language has been tempered to match the structured findings: this scan does not contain any CRITICAL severity findings.
The Zeni digital presence establishes a professional visual foundation but currently operates under significant security and accessibility risks that undermine user trust and search visibility.
The platform demonstrates high-quality design execution, characterized by a cohesive visual hierarchy, consistent branding, and excellent Core Web Vitals. The homepage achieves a strong Largest Contentful Paint (LCP) of 1156ms, and the user experience is bolstered by clear, high-contrast primary calls-to-action and a well-structured heading hierarchy that aids both navigation and readability.
high-priority concerns exist in the site's security configuration and accessibility compliance. The absence of a Content-Security-Policy (CSP) header leaves the site exposed to XSS and injection attacks, while insufficient color contrast ratios fail to meet WCAG 2 AA standards. Furthermore, the lack of canonical URLs across all scanned pages risks diluting SEO authority by allowing search engines to treat URL variations as duplicate content.
There is a significant opportunity to improve organic discoverability and AI-readiness by implementing missing technical SEO assets. Currently, the site lacks a sitemap.xml, JSON-LD structured data, and an llms.txt file. Deploying these elements will ensure search engines and AI models accurately index the product and surface Zeni in rich search results and generative AI responses.
To stabilize the platform and protect user data, the following actions must be prioritized in the next 30 days:
5 highest-impact findings, ranked.
No CSP header found. The site is vulnerable to XSS and injection attacks.
How to fix: Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
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 2.71 (foreground color: #fefbf8, background color: #f97319, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.py-2.hover\:-translate-y-0\.5[href$="signup"]` has contrast ratio 2.71; 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 /
No <link rel="canonical"> on this page. Search engines may treat URL variations (with/without trailing slash, query-string permutations) as separate pages, splitting ranking signals.
How to fix: Add to <head>: <link rel="canonical" href="https://zenidebtfree.com/">
On /
Browsers may MIME-sniff responses without this header.
How to fix: Add: X-Content-Type-Options: nosniff
On /
The page can be embedded in iframes, risking clickjacking.
How to fix: Add: X-Frame-Options: DENY (or SAMEORIGIN if embedding is needed). Alternatively, set CSP frame-ancestors.
On /
