Global Performance
6/6 locations ✓High global latency — average 1239ms across 6 locations, fastest from Singapore (781ms), slowest from Sao Paulo (1946ms). No CDN detected. Cache-Control header is missing. 6 locations above the 500ms target.
Audit overview
Compliance needs attention; the rest of the categories are in good shape.
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.
Cookie 'frontend_lang' 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.
2 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.
is missing width/height — may cause layout shift
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
NZD 875 investment → NZD 13,002/month returns + NZD 10,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
7 barrier(s) likely increasing bounce by ~28%.
- Page takes 5.6s to loadUsers abandon at ~3s — you're 3.1s 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 212ms 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
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- 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
Cost of inaction
Compliance Risk
NZD 10,000
- No privacy policy link detectedPrivacy Act 2020: NZD 1,000 – NZD 10,000
- 2 non-essential cookie(s) set without consent bannerPrivacy Act 2020: NZD 1,000 – NZD 10,000
- Trackers detected but no cookie policy foundPrivacy Act 2020: NZD 1,000 – NZD 10,000
- Trackers detected but no privacy policy foundPrivacy Act 2020: NZD 1,000 – NZD 10,000
- Privacy Policy not detectedPrivacy Act 2020: NZD 1,000 – NZD 10,000
Bounce-Rate Cost
NZD 8,335 /mo
+27.8pp bounce · ~2,778 lost visitors/mo
CPC: NZD 3.00
Bandwidth Waste
NZD 0.56 /mo
4200.5 MB/mo × 0.133 NZD/GB
- Optimize transfer: save ~420 KB per page loadSaves NZD 0.56/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.97 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.56 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
212 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.106
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.17 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.
11.15 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.54 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.87 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
32 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.037
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.28 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.
4.30 s
Categories
8Performance
is missing width/height — may cause layout shift
Security
Content-Security-Policy header is missing
Accessibility
2 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.
Top 10% of Bootstrap sites score 86+ on Compliance; you're at 54 — closing this gap is the highest-leverage improvement.
Technology stack
Odoo, on Python, with Nginx CDN
Stack Architecture
Plausible 
Odoo 
Bootstrap 
Font Awesome 
Google Font API HSTS 
Less 
Open Graph 
PostgreSQL 
Tailwind CSS 
Python 
Nginx All Detected Technologies (12)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Python is an interpreted and general-purpose programming language.
Odoo is business management software which includes CRM, ecommerce, billing, accounting, manufacturing, warehouse, project management, and inventory management.
Font Awesome is a font and icon toolkit based on CSS and Less.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Less is a CSS preprocessor, providing a set of extensions and features to traditional Cascading Style Sheets (CSS) for improved maintainability and ease of styling in web development.
Open Graph is a protocol that is used to integrate any web page into the social graph.
PostgreSQL, also known as Postgres, is a free and open-source relational database management system emphasizing extensibility and SQL compliance.
Plausible is an open-source alternative to Google Analytics.
Observations (2)
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
12 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/841bca7f-12fe-47fd-9031-353b3e36562a)<a href="https://beavercheck.com/results/841bca7f-12fe-47fd-9031-353b3e36562a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftechguys.nz" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftechguys.nzExport & 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 · 9h total → projected B (88)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Cookie 'frontend_lang' is missing the Secure flag
- · 2 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
- · is missing width/height — may cause layout shift