Audit overview
Security and Sustainability need attention; the other categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High 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.
Cookie 'AWSALB' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
55 third-party resources (100% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
Cookie 'AWSALB' has no SameSite attribute
Without SameSite, cookies ride along on cross-site requests — enabling CSRF attacks that SameSite=Lax blocks for free.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
£488 investment → £6,303/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
6 barrier(s) likely increasing bounce by ~28%.
- Page takes 6.1s to loadUsers abandon at ~3s — you're 3.6s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 800msClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
Start here for the best return on investment
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
Warning:Cost of inaction
Compliance Risk
£50,000
- Multiple H1 headings (2 found)Equality Act 2010: GBP 500 – GBP 50,000
Bounce-Rate Cost
£2,917 /mo
+27.8pp bounce · ~2,778 lost visitors/mo
CPC: GBP 1.05
Bandwidth Waste
£0.61 /mo
9713.9 MB/mo × 0.063 GBP/GB
- Optimize transfer: save ~971 KB per page loadSaves £0.61/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 3 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.
3.48 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.06 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
800 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.45 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.
9.97 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.30 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.76 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
19 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.019
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.19 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.
2.32 s
Categories
8Performance
55 third-party resources (100% of weight)
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 Cart Functionality sites score 78+ on Security; you're at 59 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon ALB, on Apache, hosted on Amazon Web Services
Stack Architecture
Google Tag Manager 
Cart Functionality 
Amazon ALB 
Cludo 
Cookie Control Google Search Console HSTS 
Isotope 
LazySizes Masonry Microsoft 365 
Open Graph 
Silktide 
core-js 3.46.0
jQuery 3.5.1
Apache 
Amazon Web Services Apache HTTP Server All Detected Technologies (18)
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Apache is a free and open-source cross-platform web server software.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
Amazon Application Load Balancer (ALB) distributes incoming application traffic to increase availability and support content-based routing.
Cludo is a cloud-based search solution.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Isotope.js is a JavaScript library that makes it easy to sort, filter, and add Masonry layouts to items on a webpage.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
Masonry is a JavaScript library that enables a cascading grid layout, positioning elements based on available vertical space for an optimized, gap-free arrangement.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Silktide is a platform that automatically detects and resolves accessibility, content, and user experience issues on websites.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Observations (2)
No build tool detected
A framework (Amazon ALB) 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
18 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/1f0959d4-ad88-4c05-86dc-a21cf468bd64)<a href="https://beavercheck.com/results/1f0959d4-ad88-4c05-86dc-a21cf468bd64"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flboro.ac.uk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Flboro.ac.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 · 6h total → projected B (83)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Cookie 'AWSALB' is missing the Secure flag
- · 55 third-party resources (100% of weight)
- · Cookie 'AWSALB' has no SameSite attribute
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found