Report loading
plans4.co.uk
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
59 / 100
Fair
0 critical fixes · 3 quick wins
Priority verdict
59/100 - fair. Start with the fixes below before reading the full report.
The biggest issue is missing content-security-policy. Start with the priority fixes, then use the evidence and technical details when a developer needs proof.
Fair
3 priority fixes identified
Score
59 / 100 — Fair
No major launch blockers found.
Biggest risk
Missing Content-Security-Policy
visitor safety and trust
Fastest win
Missing Content-Security-Policy
A practical first fix for your builder or AI agent.
Estimated impact
Higher confidence and discoverability
Fix the priority items first, then re-scan to confirm the evidence.
Biggest area to improve: Security, which mostly means visitor safety and trust.
Priority verdict
This site is technically inspectable, but the priority is making the next fix obvious.
Fix the highest-impact issue first, then use structured evidence and developer prompts so search engines, AI answer engines, and real visitors can understand the site more reliably.
What's working
What needs attention
What to do first
The Plans4 digital presence is currently undermined by significant accessibility barriers and a lack of fundamental security headers that expose the platform to injection risks. The site demonstrates a strong, cohesive brand identity through its unique "post-it note" aesthetic and custom typography, which effectively communicates its community-focused mission. It also shows high readiness for AI-driven discovery, as the robots.txt configuration allows major AI crawlers to access content, and the homepage successfully responds to agent-oriented Markdown requests. However, the platform faces high-priority technical and usability issues. A missing Content-Security-Policy (CSP) creates a serious security concern by leaving the site vulnerable to cross-site scripting (XSS) and injection attacks. Furthermore, accessibility is a major friction point; on desktop, several elements fail to meet minimum color contrast thresholds, and touch targets are too small for reliable interaction. On mobile, the fixed cookie consent banner obscures bottom-of-screen content, further degrading the user experience. The biggest opportunity lies in optimizing the site for "answer engine" visibility and performance. While the site is crawlable, it lacks the deep content coverage—such as explicit pricing, FAQ, and product catalogs—that modern AI search engines require to provide high-quality citations. Addressing the heavy page weight (2.6 MB) and implementing responsive images will also significantly improve load speeds for mobile users. To stabilize the platform and protect user data, the following actions must be prioritized in the first 30 days: - Implement a robust Content-Security-Policy (CSP) to mitigate injection vulnerabilities.
srcset to reduce layout shift and page weight.Scan details
Checks performed: SEO, UX, accessibility, performance, security, AI search.
Fix workflow
Treat this report as a queue: send the ready fixes, accept any intentional risks, then re-scan the production URL after changes land.
39
Ready to send
84
Not started
0
Accepted risk
0
Re-scan queued
The full report has all the proof. This is the owner-friendly version of what to do first.
Plain-English reason
This affects visitor safety and trust. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
No CSP header found. The site is vulnerable to XSS and injection attacks.
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 `a[href$="cookies"]` has contrast ratio 2.61; 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.61 (foreground color: #70a987, background color: #fcfaf8, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
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 `.scale-125` is rendered at 15x15 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
Ensure touch targets have sufficient size and space. Fix any of the following: Target has insufficient size (15px by 15px, 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.
A practical roadmap for turning the audit into progress.
Today
Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
This week
Element matching `a[href$="cookies"]` has contrast ratio 2.61; 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
This month
Element matching `.scale-125` is rendered at 15x15 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
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.