Global Performance
6/6 locations ✓High global latency — average 827ms across 6 locations, fastest from Madrid (116ms), slowest from Santa Clara (1679ms). No CDN detected. Cache-Control disables caching (no-store). 4 locations above the 500ms target.
Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
5 findingsQuick Wins
1High impact, low effort — start here.
Strategic
4High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
2 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
22 third-party resources (48% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
3 font preload(s) missing `crossorigin` -- font will be downloaded twice
Performance issues directly impact user engagement and conversion rates.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
£750 investment → £9,664/month returns + GBP 50,000 risk avoided
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
Conversion barriers
5 barrier(s) likely increasing bounce by ~25%.
- Page takes 4.5s to loadUsers abandon at ~3s — you're 2.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 3 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- High main-thread blocking timePage is non-interactive for 540ms after first paint→ Defer third-party scripts and split large bundles
- No Content-Security-Policy headerHigher XSS blast radius — one compromised script can exfiltrate the checkout form→ Ship a reporting-only CSP first, then enforce once violations are clean
- No skip-to-content linkKeyboard and screen-reader users must tab through the entire header on every page→ Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
Cost by category
Cost by effort level
Adjust assumptions
Team composition
Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.
Rates reflect fully-loaded developer cost including overhead
Cost of inaction
Compliance Risk
£50,000
- 2 of 3 <nav> elements are unlabeledEquality Act 2010: GBP 500 – GBP 50,000
- Skip navigation link is missing (WCAG 2.4.1)Equality Act 2010: GBP 500 – GBP 50,000
- Heading level skipped: H1 → H3 (missing H2)Equality Act 2010: GBP 500 – GBP 50,000
- Heading level skipped: H2 → H4 (missing H3)Equality Act 2010: GBP 500 – GBP 50,000
- Heading level skipped: H2 → H5 (missing H3)Equality Act 2010: GBP 500 – GBP 50,000
Bounce-Rate Cost
£7,551 /mo
+25.2pp bounce · ~2,517 lost visitors/mo
CPC: GBP 3.00
Bandwidth Waste
£0.17 /mo
2725.2 MB/mo × 0.063 GBP/GB
- Optimize transfer: save ~273 KB per page loadSaves £0.17/mo
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 2 critical issues to capture this value
How this is calculated
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Lighthouse
Mobile
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.37 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.49 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
540 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.021
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.37 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
8.49 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
597 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.74 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
22 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.010
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
597 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
1.88 s
Categories
8Performance
2 render-blocking <script src> tag(s) without async/defer
Security
Content-Security-Policy header is missing
Accessibility
All checks pass
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of WordPress sites score 86+ on Compliance; you're at 75 — closing this gap is the highest-leverage improvement.
Top 10% of Bootstrap sites score 86+ on Compliance; you're at 75 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, on LiteSpeed/PHP
Stack Architecture
Litespeed Cache 
Yoast SEO 
WordPress 
Bootstrap Google Search Console HSTS 
HTTP/3 Microsoft Microsoft 365 
MySQL 
Open Graph 
Priority Hints 
Really Simple SSL & Security 
Tailwind CSS 
PHP 
LiteSpeed All Detected Technologies (16)
LiteSpeed is a high-scalability web server.
PHP is a general-purpose scripting language used for web development.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
MySQL is an open-source relational database management system.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Really Simple SSL & Security is an easy to install and performant security solution for WordPress.
LiteSpeed Cache is an all-in-one site acceleration plugin for WordPress.
Yoast SEO is a search engine optimisation plugin for WordPress and other platforms.
Observations (3)
WordPress detected — review security configuration
WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.
No build tool detected
A framework (Bootstrap) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.
Complex technology stack detected
16 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.
Show your score
Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/09fd3756-84ee-4fd1-9245-3a4a25b039f8)<a href="https://beavercheck.com/results/09fd3756-84ee-4fd1-9245-3a4a25b039f8"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpcpclaim-uk.co.uk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpcpclaim-uk.co.ukExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
Fix Plan
Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.
Three-week fix plan
2 sprints · 10h total → projected A (92)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 22 third-party resources (48% of weight)
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found
- · 2 render-blocking <script src> tag(s) without async/defer
- · 3 font preload(s) missing `crossorigin` -- font will be downloaded twice