Skip to main content

sitiospublicos.bancochile.cl — Website Report

Scored 61/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

sitiospublicos.bancochile.cl scored 61. Addressing the 14 listed issues could raise its estimated score to 80.

2 critical8 warnings14 total issues

Quick wins

~85 min total fix time
1Missing HSTS header~2m
2Missing X-Content-Type-Options header~2m
3Missing X-Frame-Options header~2m

https://sitiospublicos.bancochile.cl/cuenta-fan · 2026-08-18

Scanned with Foglift · Technical Audit + AI Readiness analysis

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

51D

Some external data sources were unavailable. Score is based on partial data.

Technical80
Authority27
Set up all 6 tiers free →
10
Brand Mentions
Found 1+ web mentions of "sitiospublicos"
44
Domain Authority
PageRank: 3.3/10, 5+ external references
Content Freshness
Unavailable
80
Technical Readiness
Strong technical AI readiness (schema, FAQ, AI crawler access)

How does AI see Sitiospublicos?

When users ask AI about your industry, are you recommended?

G
C
P
Ge
A

Start with weekly Perplexity checks for Sitiospublicos. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

Issues Found (14)

Missing HSTS headercriticalSecurity~2 min fix

Enable HTTP Strict Transport Security to force HTTPS connections.

Quick Fix
# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }
HSTS forces browsers to use HTTPS, preventing downgrade attacks and cookie hijacking.
Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix
# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }
Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.
Missing X-Content-Type-Options headerwarningSecurity~2 min fix

Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.

Quick Fix
# Nginx:
add_header X-Content-Type-Options "nosniff" always;

# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }
Prevents browsers from MIME-type sniffing, which can lead to security vulnerabilities.
Missing X-Frame-Options headerwarningSecurity~2 min fix

Set X-Frame-Options to prevent clickjacking attacks.

Quick Fix
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;

# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }
X-Frame-Options prevents clickjacking by controlling who can embed your page in an iframe.
Missing Referrer Policy headerwarningSecurity~2 min fix

Add a Referrer-Policy header to control information leakage.

Quick Fix
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }
Controls how much referrer information is sent with requests, protecting user privacy.
Missing Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }
Permissions-Policy restricts which browser features your site can use, reducing attack surface.
1 form input may lack labelswarningAccessibility

Form inputs should have associated labels or aria-label attributes so screen readers can identify them.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.

Large HTML documentwarningPerformance

Your HTML is 903KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

3 render-blocking scriptswarningPerformance

3 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Twitter Card tagsinfoSEO~5 min fix

Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.

Quick Fix
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">
Twitter Card tags control how your page appears when shared on Twitter/X.
Few internal linksinfoSEO

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix
<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>
Skip links let keyboard users bypass repetitive navigation and jump straight to content.
HTML contains many commentsinfoPerformance

Found 21 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

61

Now

80

Estimated potential

+19 points estimated improvement from addressing 14 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+32Ahead
AI Readiness
Avg: 35+16Ahead
Performance
Avg: 55+18Ahead
Security
Avg: 40-40At risk
Accessibility
Avg: 68+21Ahead

Based on 120+ websites scanned across industries. See full benchmark report →

What This Score Means for You

Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.

Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.

Security score: 0/100

Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.

Score of 0 means your site has no security headers at all. Browsers may show security warnings to visitors.

AI visibility preview

See which brands Perplexity surfaces for your category.

Recent scans on Foglift

Scan your own site free →