Global Performance
6/6 locations ✓High global latency — average 609ms across 6 locations, fastest from Singapore (281ms), slowest from Sao Paulo (1036ms). Azure CDN edge cache (TCP_REMOTE_HIT). 3 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
2High impact, low effort — start here.
Strategic
3High 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.
Page weighs 10.3 MB (4.1 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
Soft 404: server returns HTTP 200 for non-existent pages
Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.
1 render-blocking <script src> tag(s) without async/defer
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
AUD 935 investment → AUD 9,002/month returns + AUD 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 ~26%.
- Page takes 20.6s to loadUsers abandon at ~3s — you're 18.1s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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, …)
- 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
Cost of inaction
Compliance Risk
AUD 200,000
- Skip navigation link is missing (WCAG 2.4.1)DDA: AUD 5,000 – AUD 200,000
Bounce-Rate Cost
AUD 9,001 /mo
+25.7pp bounce · ~2,572 lost visitors/mo
CPC: AUD 3.50
Bandwidth Waste
AUD 1.57 /mo
12752.1 MB/mo × 0.123 AUD/GB
- Optimize transfer: save ~1.3 MB per page loadSaves AUD 1.57/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 4 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.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
20.59 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
194 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.006
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.00 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.
20.81 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
787 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.46 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.007
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.34 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.51 s
Categories
8Performance
Page weighs 10.3 MB (4.1 MB transferred)
Security
Content-Security-Policy header is missing
Accessibility
Soft 404: server returns HTTP 200 for non-existent pages
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
Contentful, hosted on Azure, with Azure CDN CDN
Stack Architecture
Contentful 
AOS 
Adobe Fonts 
Azure Front Door HSTS 
Open Graph 
React 
Tailwind CSS 
Webpack 
core-js 3.38.1 Azure CDN Azure 
Next.js 14.2.35All Detected Technologies (13)
Azure is a cloud computing service for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.
Next.js is a React framework for developing single page Javascript applications.
Contentful is an API-first content management platform to create, manage and publish content on any digital channel.
JavaScript library to animate elements on your page as you scroll.
Adobe Fonts is a web-based service providing access to a vast library of high-quality fonts for web and print design.
Azure Front Door is a scalable and secure entry point for fast delivery of your global web applications.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Observations (2)
No build tool detected
A framework (AOS) 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
13 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/203365a5-faa7-4593-8440-af941777b124)<a href="https://beavercheck.com/results/203365a5-faa7-4593-8440-af941777b124"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.itechnologies.com.au" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.itechnologies.com.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 · 8h total → projected A (92)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Page weighs 10.3 MB (4.1 MB transferred)
- · Soft 404: server returns HTTP 200 for non-existent pages
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found
- · 1 render-blocking <script src> tag(s) without async/defer