nektar.ai — Website Report

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'" }

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

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=()' }

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

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

Heading hierarchy jumps from H1 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 278KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

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

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>