Audit overview
3 categories need attention: Security, and 2 others.
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.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
1 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
AUD 761 investment → AUD 16,903/month returns + AUD 50,200,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
8 barrier(s) likely increasing bounce by ~27%.
- Page takes 7.8s to loadUsers abandon at ~3s — you're 5.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- High main-thread blocking timePage is non-interactive for 560ms after first paint→ Defer third-party scripts and split large bundles
- 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
- No structured dataNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
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
AUD 50,200,000
- No privacy policy link detectedPrivacy Act 1988: AUD 66,000 – AUD 50,000,000
- Trackers detected but no cookie policy foundPrivacy Act 1988: AUD 66,000 – AUD 50,000,000
- Trackers detected but no privacy policy foundPrivacy Act 1988: AUD 66,000 – AUD 50,000,000
Bounce-Rate Cost
AUD 9,279 /mo
+26.5pp bounce · ~2,651 lost visitors/mo
CPC: AUD 3.50
Bandwidth Waste
AUD 0.97 /mo
7883.1 MB/mo × 0.123 AUD/GB
- Optimize transfer: save ~788 KB per page loadSaves AUD 0.97/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 5 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.
6.88 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.78 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
560 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.005
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.32 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.
16.72 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.72 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.06 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
30 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.62 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.
6.16 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
1 link(s) with no accessible text
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.
Technology stack
Adobe Experience Manager, on Java
Stack Architecture
Adobe Analytics 
Adobe Experience Platform Launch Adobe Experience Manager 
Coveo 
Adobe Client Data Layer 2.0.2Microsoft Mimecast 
Open Graph 
Priority Hints 
ServiceNow 
Svelte 
Tailwind CSS 
Webpack 
YouTube 
Java All Detected Technologies (15)
Java is a class-based, object-oriented programming language that is designed to have as few implementation dependencies as possible.
Adobe Experience Manager (AEM) is a content management solution for building websites, mobile apps and forms.
Adobe Client Data Layer is a framework of JavaScript objects on your site that contains all variable values used in your implementation.
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.
ServiceNow is a cloud computing platform to help companies manage digital workflows for enterprise operations.
Webpack is an open-source JavaScript module bundler.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
Adobe Analytics is a web analytics, marketing and cross-channel analytics application.
Adobe Experience Cloud Launch is an extendable tag management solution for Adobe Experience Cloud, Adobe Experience Platform, and other applications.
Coveo is an enterprise search and relevance platform that uses AI to enhance search capabilities and deliver personalized content across digital touchpoints.
Observations (1)
Complex technology stack detected
15 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/f1ce1513-d3a6-4a08-8cd2-e5eafc141e31)<a href="https://beavercheck.com/results/f1ce1513-d3a6-4a08-8cd2-e5eafc141e31"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fusyd.edu.au" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fusyd.edu.auExport & 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 · 7h total → projected B (80)
Sprint 1: Quick Wins
+6Highest ROI — low effort, high impact
- · No <main> landmark found
- · HSTS header is missing
- · 1 link(s) with no accessible text
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found