Global Performance
6/6 locations ✓High global latency — average 615ms across 6 locations, fastest from Singapore (262ms), slowest from Santa Clara (984ms). No CDN detected. 4 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
3High impact, low effort — start here.
Strategic
2High 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)
/.env is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
Page weighs 10.7 MB (6.9 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
3 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.
/composer.json is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€234 investment → €9,833/month returns + EUR 120,500,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
9 barrier(s) likely increasing bounce by ~30%.
- Page takes 16.2s to loadUsers abandon at ~3s — you're 13.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 3 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
- High main-thread blocking timePage is non-interactive for 481ms 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
€120.500.000
- 1 non-essential cookie(s) set without consent bannerGDPR: EUR 5.000 – EUR 10.000.000
- 1 non-essential cookie(s) set without consent bannerGDPR: EUR 10.000 – EUR 20.000.000
- 1 non-essential cookie(s) set without consent bannerePrivacy Directive: EUR 5.000 – EUR 100.000.000
Bounce-Rate Cost
€9.832 /mo
+30.3pp bounce · ~3,034 lost visitors/mo
CPC: EUR 3.24
Bandwidth Waste
€1,61 /mo
21709.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~2.2 MB per page loadSaves €1,61/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.
2.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.21 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
481 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.126
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.20 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.
16.27 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
790 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.83 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
7 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.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.
3.83 s
Categories
8Performance
Page weighs 10.7 MB (6.9 MB transferred)
Security
/.env is publicly accessible
Accessibility
3 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.
Technology stack
Alpine.js 3.15.12, on LiteSpeed/PHP, with unpkg CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
Hostinger 
Alpine.js 3.15.12
Axios 
Google Font API 
HTTP/3 Microsoft 365 
Open Graph 
Tailwind CSS 
YouTube 
PHP 8.3.30
LiteSpeed All Detected Technologies (14)
LiteSpeed is a high-scalability web server.
PHP is a general-purpose scripting language used for web development.
Alpine.js is a minimal framework for composing behavior directly in your markup.
Promise based HTTP client for the browser and node.js
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Open Graph is a protocol that is used to integrate any web page into the social graph.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
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.
Hostinger is an employee-owned Web hosting provider and internet domain registrar.
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'PHP 8.3.30'. Remove this header in production to reduce information leakage.
No build tool detected
A framework (Alpine.js) 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
14 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/37c5e31a-9f82-43b4-a747-026f6e92cf66)<a href="https://beavercheck.com/results/37c5e31a-9f82-43b4-a747-026f6e92cf66"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftrydantech.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftrydantech.comExport & 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 · 3h total → projected A (91)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · Page weighs 10.7 MB (6.9 MB transferred)
- · HSTS header is missing
- · 3 link(s) with no accessible text
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · /.env is publicly accessible
- · /composer.json is publicly accessible