Audit overview
3 categories need attention: Security, and 2 others.
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.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
21 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.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
110 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
CLP 426,667 investment → CLP 5,086,002/month returns + CLP 50,000,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 ~34%.
- Page takes 19.3s to loadUsers abandon at ~3s — you're 16.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.7sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- Severe layout shift during page loadUsers mis-click when content jumps — converting intent into frustration→ Reserve space for images, ads, and embeds with explicit width/height
- 4 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 HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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
CLP 50,000,000
- No privacy policy link detectedLey 19.628: CLP 1,000,000 – CLP 50,000,000
- Trackers detected but no cookie policy foundLey 19.628: CLP 1,000,000 – CLP 50,000,000
- Trackers detected but no privacy policy foundLey 19.628: CLP 1,000,000 – CLP 50,000,000
Bounce-Rate Cost
CLP 5,085,313 /mo
+33.9pp bounce · ~3,390 lost visitors/mo
CPC: CLP 1500.00
Bandwidth Waste
CLP 689 /mo
9048.8 MB/mo × 76.190 CLP/GB
- Optimize transfer: save ~905 KB per page loadSaves CLP 689/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.
9.39 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
19.26 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.67 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
1.404
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.39 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.
19.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.
2.92 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.33 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
54 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.014
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.53 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.
5.34 s
Categories
8Performance
110 HTTP requests — consider bundling or reducing
Security
Content-Security-Policy header is missing
Accessibility
21 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 Google Font API sites score 95+ on Content; you're at 71 — closing this gap is the highest-leverage improvement.
Technology stack
FancyBox 3.5.2, with Nginx CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
FancyBox 3.5.2
Google Font API Google Search Console Google Workspace HSTS Hotjar Microsoft 
Open Graph 
Varnish 6.6
YouTube 
jQuery 2.1.4
jQuery UI 1.12.1
Nginx All Detected Technologies (15)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
FancyBox is a tool for displaying images, html content and multi-media in a Mac-style 'lightbox' that floats overtop of web page.
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.
Open Graph is a protocol that is used to integrate any web page into the social graph.
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.
jQuery UI is a collection of GUI widgets, animated visual effects, and themes implemented with jQuery, Cascading Style Sheets, and HTML.
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 (3)
No build tool detected
A framework (FancyBox) 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.
jQuery version may be outdated
Detected jQuery 2.1.4. The current major version is 3. Consider updating for security patches and new features.
Complex technology stack detected
15 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/uchile.cl)<a href="https://beavercheck.com/sites/uchile.cl"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fuchile.cl" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fuchile.clExport & 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 · 11h total → projected B (82)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · No <main> landmark found
- · 21 link(s) with no accessible text
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found
- · 110 HTTP requests — consider bundling or reducing