Audit overview
Security 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.
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.
58 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.
Cross-Origin-Embedder-Policy header is missing
COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
CAD 689 investment → CAD 9,426/month returns + CAD 350,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%.
- Mixed content on HTTPS pageBrowsers block insecure subresources — broken images, missing scripts, warning badge→ Change http:// URLs inside the page to https:// (or protocol-relative)
- Page loads in 3.4sEvery additional 100ms above 2.5s costs conversions — you're 912ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- High main-thread blocking timePage is non-interactive for 341ms 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
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
CAD 350,000
- No privacy policy link detectedPIPEDA: CAD 1,000 – CAD 100,000
- Trackers detected but no cookie policy foundPIPEDA: CAD 1,000 – CAD 100,000
- Trackers detected but no privacy policy foundPIPEDA: CAD 1,000 – CAD 100,000
Bounce-Rate Cost
CAD 7,639 /mo
+27.3pp bounce · ~2,728 lost visitors/mo
CPC: CAD 2.80
Bandwidth Waste
CAD 0.47 /mo
4302.6 MB/mo × 0.108 CAD/GB
- Optimize transfer: save ~430 KB per page loadSaves CAD 0.47/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.41 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.41 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
341 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.18 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.78 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.41 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.55 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
21 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.
1.80 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.59 s
Categories
8Performance
58 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 Google Search Console sites score 96+ on SEO; you're at 80 — closing this gap is the highest-leverage improvement.
Technology stack
Drupal 10, on PHP, with Nginx CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
Drupal 10
Open Graph 
React 
jQuery 3.7.1
PHP 
styled-components 6.1.8
Nginx All Detected Technologies (11)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
PHP is a general-purpose scripting language used for web development.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
Drupal is a free and open-source web content management framework.
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.
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 Analytics is a free web analytics service that tracks and reports website traffic.
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 (4)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 6.1.8'. Remove this header in production to reduce information leakage.
jQuery loaded alongside a modern framework
Both jQuery and React are loaded. Modern frameworks handle DOM manipulation natively. jQuery may be unnecessary and adds ~30KB to the page weight. Check the Performance tab for bundle analysis.
No build tool detected
A framework (Google Search Console) 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
11 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/sites/ontario.ca)<a href="https://beavercheck.com/sites/ontario.ca"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fontario.ca" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fontario.caExport & 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 (84)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · HSTS header is missing
- · 58 third-party resources (100% of weight)
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found
- · Cross-Origin-Embedder-Policy header is missing