Report loading
itmly.app
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
itmly currently suffers from critical security vulnerabilities and significant accessibility barriers that undermine its professional brand authority.
The platform demonstrates excellent technical performance and a cohesive visual identity. On desktop, the site achieves an impressive Largest Contentful Paint (LCP) of 972ms, ensuring near-instantaneous perceived loading. The design utilizes a strong typographic hierarchy and a consistent dark-mode aesthetic that establishes immediate trust. Furthermore, the primary conversion path is highly effective, with a prominent "Get started free" call-to-action positioned clearly above the fold on both desktop and mobile viewports.
However, severe security and usability flaws present significant risks to user safety and retention. The absence of a Content-Security-Policy (CSP) header leaves the site vulnerable to XSS and injection attacks. On desktop, critical accessibility failures exist, including insufficient color contrast ratios and touch targets that do not meet minimum size requirements. On mobile, the hero graphic is overly complex, featuring illegible text that creates visual clutter and degrades the user experience for smaller screens. Additionally, the sign-up flow introduces unnecessary friction through high form field density and a lack of essential SEO metadata on secondary pages.
The greatest opportunity lies in optimizing the conversion funnel and search visibility by implementing a robust SEO and social sharing strategy. By enriching page titles, adding canonical URLs, and deploying Open Graph tags across all subpages, itmly can significantly improve its organic search presence and ensure professional-grade link previews when shared on social platforms.
First 30 Days Recommendation:
5 highest-impact findings, ranked.
The large, detailed 'app preview' graphic in the hero section contains very small text (e.g., 'Name', 'Artist', 'Year') that is illegible on a mobile viewport. This creates visual clutter and undermines the brand's professional look.
How to fix: On mobile viewports, replace the complex nested UI component graphic with a simplified, high-level illustration or a larger, more legible text-based value proposition to improve clarity and mobile readability.
On /
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 3.66 (foreground color: #ffffff, background color: #0d9688, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.gap-1` has contrast ratio 3.66; 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 /
Ensure touch targets have sufficient size and space. Fix any of the following: Target has insufficient size (24px by 6px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 22px instead of at least 24px.
How to fix: Element matching `button[aria-label="View demo item 1"]` is rendered at 24x6 px; touch targets must be >=24x24 px (WCAG 2.5.8). Add padding (e.g. `min-h-[24px] min-w-[24px]` in Tailwind, or `padding` so the bounding box reaches 24 px in both dimensions). Reference: https://dequeuniversity.com/rules/axe/4.11/target-size?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 /sign-up
