Report loading
myrenteval.com
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Fair
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
RentEval possesses an exceptionally fast and responsive technical foundation, but critical security vulnerabilities and accessibility gaps undermine its professional credibility and user safety.
The platform demonstrates industry-leading performance metrics across both desktop and mobile viewports, with all Core Web Vitals consistently falling within the "Good" band. This speed is paired with a strong visual hierarchy, clear branding, and effective use of primary calls-to-action above the fold. Furthermore, the implementation of descriptive meta descriptions and Open Graph metadata ensures high-quality social sharing and search engine visibility for key pages.
Significant security and accessibility failures present immediate risks to the brand. On desktop, the absence of a Content-Security-Policy (CSP) leaves the site vulnerable to cross-site scripting (XSS) and injection attacks. Accessibility is also compromised by insufficient color contrast ratios and undersized touch targets on desktop. Additionally, the lack of canonical URLs across all scanned pages risks fragmented search engine rankings due to URL variations.
There is a major opportunity to increase user trust and engagement by replacing generic "Photo coming soon" placeholders with actual property imagery. On mobile, refining the search experience by adding a clear/reset affordance for the search input will reduce friction during user queries. Addressing these content-level gaps alongside technical fixes transforms the site from a functional prototype into a high-authority marketplace.
First 30 days:
<link rel="canonical"> tags to all primary pages to consolidate SEO authority.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.48 (foreground color: #34b262, background color: #ebf7ef, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.text-card-foreground.shadow-sm.hover\:shadow-lg:nth-child(1) > .p-6 > .gap-4.items-start.flex > .min-w-0.flex-1 > .flex-wrap.gap-2.flex:nth-child(5) > .bg-\[hsl\(var\(--rating-excellent\)\)\]\/10.text-\[hsl\(var\(--rating-excellent\)\)\].py-1:nth-child(1)` has contrast ratio 2.48; 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 (16px by 8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16px instead of at least 24px.
How to fix: Element matching `.w-2.h-2.bg-primary` is rendered at 16x8 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 /
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://myrenteval.com/landlords">
On /landlords
While visually clear, the search input does not have an associated `<label>` element. This can make it difficult for screen reader users to understand the context of the input without reading surrounding text.
How to fix: Add a `<label>` element with a class like `sr-only` (screen-reader only) that describes the purpose of the input, e.g., `<label for='search-input' class='sr-only'>Search landlords or property managers</label>`. Ensure the input has an `id='search-input'`.
On /landlords