Skip to main content

renewe.fi — Website Report

Scored 54/100 · Scanned with Foglift

D
Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

renewe.fi scored 54. Addressing the 19 listed issues could raise its estimated score to 83.

4 critical11 warnings19 total issues

Quick wins

~146 min total fix time
1Missing X-Content-Type-Options header~2m
2Missing X-Frame-Options header~2m
3Missing Referrer Policy header~2m

https://renewe.fi/ · 2026-09-29

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Search Readiness Risk

Your AI Readiness score of 43/100 identifies technical and content barriers that may make this page harder for AI systems to access, understand, or reuse. It does not show whether AI assistants recommend or cite your site. Check answer-level AI visibility →

Share This Technical Audit

Send this Technical Audit 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

43F

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

Technical64
Authority25
Set up all 6 tiers free →
—
Brand Mentions
Unavailable
28
Domain Authority
PageRank signal only; external reference data is temporarily unavailable.
0
Content Freshness
No sitemap with date information found
64
Technical Readiness
Moderate technical readiness — some improvements possible

Technical Issues

No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

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>
FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.
AI doesn't know who you areinfo~10 min fix

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.

Quick Fix
<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>
Entity markup tells AI models who you are, making them more likely to cite your brand accurately.

Pro tip: The biggest drivers of AI visibility are brand mentions and domain authority — not just technical setup. Set up Free monitoring →

How does AI see Renewe?

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

G
C
P
Ge
A

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

SEO & Technical Issues (17)

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.
28 images missing alt textcriticalSEO

Found 28 of 55 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).

51% of images lack alt textcriticalAccessibility

28 of 55 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.

12 render-blocking scriptscriticalPerformance

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

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.
Multiple H1 headings foundwarningSEO

Found 2 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.

Skipped heading levelwarningAccessibility

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

Potential low contrast textwarningAccessibility

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.

Large HTML documentwarningPerformance

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

29 external stylesheetswarningPerformance

Loading 29 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.

25 images without lazy loadingwarningPerformance

25 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

No main landmarkinfoAccessibility~3 min fix

Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.

Quick Fix
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
  <h1>Page Title</h1>
  <p>Your primary content here...</p>
</main>
The <main> element identifies the primary content area, letting screen reader users skip to it directly.
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 52 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

54

Now

83

Estimated potential

+29 points estimated improvement from addressing 19 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+23Ahead
AI Readiness
Avg: 35+8On par
Performance
Avg: 55-6Behind
Security
Avg: 40-20At risk
Accessibility
Avg: 68-6Behind

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: 20/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.

Recent scans on Foglift

Scan your own site free →