icecube.asia — Website Report
Scored 62/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
icecube.asia scored 62. Addressing the 14 listed issues could raise its estimated score to 87.
Quick wins
~103 min total fix timehttps://icecube.asia/ · 2026-07-28
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://icecube.asia Great news — your site has strong AI Readiness (77/100). Site Technical Health: 62/100. Its technical, content, and authority signals give AI systems a solid foundation for accessing, understanding, and reusing the page. We found 3 critical issues and 10 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. 7 render-blocking scripts — 7 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. Missing X-Frame-Options header — Set X-Frame-Options to prevent clickjacking attacks. 2. Missing Referrer Policy header — Add a Referrer-Policy header to control information leakage. 3. Missing Permissions
12 more critical fixes + quick wins in your full report
Create a free account to save this audit and unlock the complete action plan.
Save and unlock my full reportFree account. No credit card required.
Share This Technical Audit
Send this Technical Audit to a teammate or contact. The shareable link includes all scores and issues.
AI Readiness
Technical and authority signals that support AI systems in accessing, understanding, and reusing your content
How does AI see Icecube?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Icecube. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
Issues Found (14)
Enable HTTP Strict Transport Security to force HTTPS connections.
# 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' }Add a Content-Security-Policy header to prevent XSS and injection attacks.
# 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'" }7 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Set X-Frame-Options to prevent clickjacking attacks.
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }Add a Referrer-Policy header to control information leakage.
# 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' }Add a Permissions-Policy header to control browser feature access.
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }Found 2 of 42 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
2 of 42 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.
Some text appears to use light colors that may not have sufficient contrast against the background. WCAG requires a minimum 4.5:1 contrast ratio.
Server responded in 2.9s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 630KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
42 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.
Your Potential Score
62
Now
87
Estimated potential
+25 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.
Weekly Perplexity while active · No credit card required
Compare paid plans — from $49/moIndustry Benchmark
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.
Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.
Security score: 15/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.