Report loading
pulsefinder.co.uk
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
The PulseFinder digital infrastructure contains critical security vulnerabilities and brand inconsistencies that undermine user trust and site integrity.
The platform demonstrates a strong foundation in technical SEO and core security protocols. The heading hierarchy is well-structured for search engine crawling, and essential security headers—including HSTS, X-Content-Type-Options, and X-Frame-Options—are correctly implemented. Furthermore, the site utilizes efficient performance optimizations, such as high-priority loading for key images, which aids Largest Contentful Paint (LCP) metrics.
However, the absence of a Content-Security-Policy (CSP) presents a high-severity risk, leaving the site vulnerable to Cross-Site Scripting (XSS) and injection attacks. This technical weakness is compounded by significant brand fragmentation; the visible header logo displays "PulseBiz" while metadata identifies as PulseFinder, creating immediate cognitive dissonance for new users. Additionally, critical accessibility failures regarding color contrast ratios and broken internal links further degrade the professional user experience.
The most significant growth opportunity lies in optimizing the search interface to drive higher conversion rates. The current search form lacks immediate feedback or autocomplete functionality, forcing users into a high-friction "click-to-search" loop. Implementing an intelligent suggestion dropdown will reduce user effort and increase engagement with the platform's business listings.
To stabilize the platform and protect user data, the following actions are required within 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 3.32 (foreground color: #ffffff, background color: #e8634a, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
How to fix: Element matching `.sm\:inline-flex` has contrast ratio 3.32; 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 /
The search form relies on a 'Search' button click. For better conversion, implementing an autocomplete or suggestion dropdown as the user types can reduce friction (Nielsen Heuristic #6: Recognition rather than recall).
How to fix: Implement a debounced search listener that displays top-rated businesses in a dropdown menu as soon as the user begins typing in the `<input type="text" placeholder="What are you looking for?">` field.
On /
No COOP header. The page may be vulnerable to cross-origin attacks via window references. Practical impact is low unless the site uses cross-origin isolation features.
How to fix: Add: Cross-Origin-Opener-Policy: same-origin
On /
No CORP header. Resources may be loadable by cross-origin pages. Optional defence-in-depth.
How to fix: Add: Cross-Origin-Resource-Policy: same-origin (or same-site)
On /
