saasten.com — Website Report
Scored 43/100 · Scanned with Foglift
Fixing "Missing HSTS header" would move saasten.com from 43 to 63.
Quick wins
~173 min total fix timehttps://saasten.com/ · 2026-06-29
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Search Readiness Risk
Your AI Readiness score of 40/100 means AI assistants like ChatGPT and Perplexity may not recommend your site. Monitor your AI visibility →
AI Action Plan
Website Analysis for https://Saasten.com Your site scores 43/100, but AI search engines can barely find you. AI Visibility: 34/100. When customers ask ChatGPT or Perplexity about your industry, you're likely not in the answer. We found 5 critical issues and 13 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 meta description — No meta description found. Search engines use this as the snippet in results. Add one for better CTR. 3. 37 images missing alt text — Found 37 of 40 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search). 4. 93% of images lack alt text — 37 of 40 images have no alt attribute. Screen readers cannot describe these images to visually impaired users. 5. 38 render-blocking scripts — 38 scripts without async or defer
17 more critical fixes + quick wins in your full report
Enter your email and we'll send the complete action plan to your inbox.
No spam. Just your report.
Share This Report
Send this scan to a teammate or contact. The shareable link includes all scores and issues.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
Technical Issues
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What does your company do?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We provide [your service]. Our solution helps..."
}
}]
}
</script>Pro tip: The biggest drivers of AI visibility are brand mentions and domain authority — not just technical setup. Set up AI visibility monitoring →
How does AI see Saasten?
When users ask AI about your industry, are you recommended?
See how ChatGPT, Claude, Perplexity, and Gemini talk about Saasten
SEO & Technical Issues (22)
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' }No meta description found. Search engines use this as the snippet in results. Add one for better CTR.
<meta name="description" content="Clear, compelling description of your page in 120-160 characters. Include your main keyword naturally.">Found 37 of 40 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
37 of 40 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
38 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }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 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
Form inputs should have associated labels or aria-label attributes so screen readers can identify them.
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 1.6s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Your HTML is 313KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Loading 38 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
40 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.
<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
<h1>Page Title</h1>
<p>Your primary content here...</p>
</main>Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.
<!-- 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>Found 42 elements with large inline styles. Move these to external CSS for better caching and maintainability.
Found 49 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
43
Now
75
Potential
+32 points possible by fixing 23 issues
That moves you from F to C — above average
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Free tier available · No credit card required
Industry 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: 25/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.