Foglift
pec.no — Website Report
Scored 63/100 · Scanned with Foglift
D
pec.no scored 63. One fix would take it to 83.
3 critical9 warnings14 total issues
Quick wins
~111 min total fix time1Missing HSTS header~2m
2Missing Referrer Policy header~2m
3Missing Permissions Policy header~2m
https://pec.no/ · 6/3/2026, 12:46:01 PM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://pec.no Your site scores 63/100 overall, but AI engines may be missing you. Your AI Visibility is 53/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 3 critical issues and 9 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. 21 render-blocking scripts — 21 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. No FAQ section found — 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
11 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
53D
85
Brand Mentions
Found 19+ web mentions of "pec"
20
Domain Authority
PageRank: 2.6/10, 0+ external references
26
Content Freshness
30 pages in sitemap but none updated recently
68
Technical Readiness
Moderate technical readiness — some improvements possible
Technical Issues
No FAQ section foundwarning~15 min fix
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.
Quick Fix
<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>AI models frequently cite FAQ content. Add FAQPage schema to boost your chances of appearing in AI-generated answers.
Page summary too short for AIinfo~5 min fix
Your meta description is under 80 characters. AI engines use this as a quick summary of your page. Write a clear, factual description (120-160 characters) that explains what your business does and why it matters.
Quick Fix
<!-- Aim for 120-160 characters with clear, factual information -->
<meta name="description" content="[Your Company] provides [specific service] for [target audience]. Founded in [year], we serve [number]+ customers with [key differentiator].">AI models extract meta descriptions to understand what your business does. Make it factual and specific.
How does AI see Pec?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Pec
SEO & Technical Issues (12)
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.
21 render-blocking scriptscriticalPerformance
21 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
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.
Missing Open Graph tagswarningSEO~10 min fix
Missing og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.
Quick Fix
<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">Open Graph tags control how your page looks when shared on Facebook, LinkedIn, and other social platforms.
Multiple H1 headings foundwarningSEO
Found 16 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
Server response could be fasterwarningPerformance
Server responded in 1.1s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Large HTML documentwarningPerformance
Your HTML is 651KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
49 external stylesheetswarningPerformance
Loading 49 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
45 images without lazy loadingwarningPerformance
45 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
HTML contains many commentsinfoPerformance
Found 9 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
63
Now
83
Potential
+20 points possible by fixing 14 issues
That moves you from D to B — top 15% of all websites
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.
Start monitoring — from $49/mo
Free tier available · No credit card required
Industry Benchmark
SEO
Avg: 62+28Ahead
AI Readiness
Avg: 35+24Ahead
Performance
Avg: 55-11At risk
Security
Avg: 40-10Behind
Accessibility
Avg: 68+32Ahead
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: 30/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.