Skip to main content

kaesthetics.in — Website Report

Scored 52/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

kaesthetics.in scored 52. Addressing the 21 listed issues could raise its estimated score to 76.

4 critical13 warnings21 total issues

Quick wins

~158 min total fix time
1Missing HSTS header~2m
2Missing X-Content-Type-Options header~2m
3Missing X-Frame-Options header~2m

https://kaesthetics.in/ · 2026-08-01

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://kaesthetics.in/ Your site scores 52/100 overall. AI Readiness is 62/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 4 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 Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. Slow server response — Server responded in 3.4s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance. 4. 33 render-blocking scripts — 33 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 — A clea

16 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.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

62D
Technical73
Authority53
Set up all 6 tiers free →
100
Brand Mentions
Found 20+ web mentions of "kaesthetics"
12
Domain Authority
PageRank: 1.6/10, 0+ external references
0
Content Freshness
No sitemap with date information found
73
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.

How does AI see Kaesthetics?

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

G
C
P
Ge
A

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

SEO & Technical Issues (20)

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.
Slow server responsecriticalPerformance

Server responded in 3.4s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance.

33 render-blocking scriptscriticalPerformance

33 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.
Title tag too longwarningSEO

Your title is 65 characters. Keep it under 60 for best display in search results.

4 form inputs may lack labelswarningAccessibility

Form inputs should have associated labels or aria-label attributes so screen readers can identify them.

Skipped heading levelwarningAccessibility

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

1 link with vague textwarningAccessibility

Links with text like "click here" or "read more" don't make sense out of context. Use descriptive link text that explains the destination.

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 283KB. 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.

17 images without lazy loadingwarningPerformance

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

Few internal linksinfoSEO

Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.

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 12 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

52

Now

76

Estimated potential

+24 points estimated improvement from addressing 21 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 Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, 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 Google AI Overview while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+30Ahead
AI Readiness
Avg: 35+27Ahead
Performance
Avg: 55-21At risk
Security
Avg: 40-40At risk
Accessibility
Avg: 68+2On par

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

AI visibility preview

See which brands Google AI Overview surfaces for your category.

Recent scans on Foglift

Scan your own site free →