psaprof.nl — Website Report
Scored 37/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
psaprof.nl: start with "AI search engines can't read your site". Addressing the 25 listed issues could raise its estimated score from 37 to 65.
Quick wins
~177 min total fix timehttps://psaprof.nl/ · 2026-07-08
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Action Plan
Website Analysis for https://psaprof.nl/ Your site scores 37/100 overall, but AI engines may be missing you. Your AI Visibility is 69/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 9 critical issues and 12 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
2. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections. 3. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 4. Missing meta description — No meta description found. Search engines use this as the snippet in results. Add one for better CTR. 5. 25 images missing alt text — Found 25 of 34 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
20 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
Technical Issues
Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.
# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /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>Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"sameAs": [
"https://twitter.com/yourhandle",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourorg"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}
</script>How does AI see Psaprof?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Psaprof. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
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' }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'" }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 25 of 34 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
25 of 34 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Your viewport meta tag prevents users from zooming. This is an accessibility violation — users with low vision need to zoom to read content.
<!-- Replace your viewport meta tag with this (allows zooming) -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Do NOT use: maximum-scale=1, user-scalable=no -->Server responded in 4.6s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance.
32 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=()' }Missing og:description, og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">Found 3 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
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.
Your HTML is 419KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
Loading 14 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
33 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.
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>Your Potential Score
37
Now
65
Estimated potential
+28 points estimated improvement from addressing 25 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
SEO issues — Your site may be losing 20-40% of potential Google traffic due to missing meta tags, broken structure, or indexing problems.
Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.
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: 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.