Audit overview
Security and Accessibility need attention; the other 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)
'unsafe-eval' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
Cookie 'TS010e0f58' 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.
1 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
3 button(s) with no accessible text
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
CAD 1,306 investment → CAD 8,684/month returns + CAD 250,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
5 barrier(s) likely increasing bounce by ~27%.
- Page takes 20.1s to loadUsers abandon at ~3s — you're 17.6s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 15 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- 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
- 1 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
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 250,000
- No <main> landmark foundACA: CAD 250 – CAD 250,000
- Heading level skipped: H2 → H4 (missing H3)ACA: CAD 250 – CAD 250,000
- 1 control(s) without accessible labelACA: CAD 250 – CAD 250,000
Bounce-Rate Cost
CAD 8,683 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: CAD 3.24
Bandwidth Waste
CAD 1.00 /mo
9206.4 MB/mo × 0.108 CAD/GB
- Optimize transfer: save ~921 KB per page loadSaves CAD 1.00/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.
11.45 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
20.08 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
22 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.203
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
11.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.
20.08 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.33 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.07 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.256
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.33 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.07 s
Categories
8Performance
All checks pass
Security
'unsafe-eval' found in script source
Accessibility
1 control(s) without accessible label
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 Drupal sites score 71+ on Accessibility; you're at 59 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 82+ on Security; you're at 64 — closing this gap is the highest-leverage improvement.
Technology stack
Drupal 7, on PHP
Stack Architecture
Facebook Pixel 
Linkedin Insight Tag 
Microsoft Power BI 
Drupal 7
Open Graph 
SWC 
Varnish 
YouTube 
jQuery 3.3.1
parcel 
PHP All Detected Technologies (12)
PHP is a general-purpose scripting language used for web development.
Drupal is a free and open-source web content management framework.
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.
SWC is an extensible Rust-based platform for the next generation of fast developer tools.
Varnish is a reverse caching proxy.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
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.
Parcel is an open-source web application bundler known for its zero-config approach, simplifying the process of building and bundling web projects.
Facebook pixel is an analytics tool that allows you to measure the effectiveness of your advertising.
LinkedIn Insight Tag is a lightweight JavaScript tag that powers conversion tracking, website audiences, and website demographics.
Microsoft Power BI is a data analytics platform that transforms company data into rich visuals for insights and decision-making.
Observations (3)
No build tool detected
A framework (HSTS) 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.
Drupal version may be outdated
Detected Drupal 7. The current major version is 10. Consider updating for security patches and new features.
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/0eecd466-fd80-876a-1223-20dd9b9dd81d)<a href="https://beavercheck.com/results/0eecd466-fd80-876a-1223-20dd9b9dd81d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mcgill.ca" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mcgill.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
3 sprints · 14h total → projected B (85)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Cookie 'TS010e0f58' is missing the Secure flag
- · 3 button(s) with no accessible text
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 1 control(s) without accessible label
Sprint 3: Strategic Improvements
+3Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source