Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
5 findingsQuick Wins
1High impact, low effort — start here.
Strategic
4High 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
Your mail setup has problems.
tradingtitans007.sbs fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.
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.
122 third-party resources (56% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
233 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Images are 1.9 MB — compress or use modern formats
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$1,750 investment → $14,040/month returns + USD 7,500 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
3 barrier(s) likely increasing bounce by ~33%.
- Page takes 8.7s to loadUsers abandon at ~3s — you're 6.2s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.1sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- No viewport meta tagMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature→ Add <meta name="viewport" content="width=device-width, initial-scale=1">
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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
$7,500
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no privacy policy foundCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$8,821 /mo
+32.8pp bounce · ~3,279 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.86 /mo
10692.5 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~1.1 MB per page loadSaves $0.86/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 2 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.
2.30 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.66 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.09 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.81 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.82 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
690 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.89 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
18 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.012
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.69 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.33 s
Categories
6How you compare
Where this site stands against peers running the same stack.
Top 10% of Google Search Console sites score 86+ on Compliance; you're at 74 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 95+ on Performance; you're at 75 — closing this gap is the highest-leverage improvement.
Technology stack
Google Search Console, with Netlify CDN
Stack Architecture
Netlify Netlify CDN All Detected Technologies (4)
Netlify providers hosting and server-less backend services for web applications and static websites.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Observations (1)
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.
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/tradingtitans007.sbs)<a href="https://beavercheck.com/sites/tradingtitans007.sbs"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.tradingtitans007.sbs" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.tradingtitans007.sbsExport & 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 · 18h total → projected B (86)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 122 third-party resources (56% of weight)
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · Images are 1.9 MB — compress or use modern formats
- · 233 HTTP requests — consider bundling or reducing
Sprint 3: Strategic Improvements
+4Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source