Skip to main content

store.royallubricants.com.au — Website Report

Scored 75/100 · Scanned with Foglift

C
Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

store.royallubricants.com.au scored 75. Addressing the 11 listed issues could raise its estimated score to 96.

3 critical3 warnings11 total issues

Quick wins

~77 min total fix time
1Missing HSTS header~2m
2Missing Permissions Policy header~2m
3No main landmark~3m

https://store.royallubricants.com.au/ · 2026-10-11

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://store.royallubricants.com.au/ Site Technical Health: 75/100. AI Readiness is 54/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 3 critical issues and 3 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. 4 render-blocking scripts — 4 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 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 a

5 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 report

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

Email to Contact

AI Readiness

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

54D
Technical68
Authority42
Set up all 6 tiers free →
85
Brand Mentions
Found 19+ web mentions of "store"
0
Domain Authority
External reference signal only; PageRank data is temporarily unavailable.
39
Content Freshness
500 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

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 Store?

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

G
C
P
Ge
A

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

SEO & Technical Issues (10)

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.
4 render-blocking scriptscriticalPerformance

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

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.
Meta description too longwarningSEO

Your description is 180 characters. Keep it under 160 for best display.

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.
Heavy inline stylesinfoPerformance

Found 13 elements with large inline styles. Move these to external CSS for better caching and maintainability.

No resource hintsinfoPerformance~5 min fix

Add <link rel='preconnect'> for critical third-party domains to reduce connection setup time.

Quick Fix
<!-- Add to <head> for your critical third-party domains -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://cdn.example.com">
Preconnect and DNS-prefetch reduce connection time to third-party domains by starting the handshake early.
HTML contains many commentsinfoPerformance

Found 17 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

75

Now

96

Estimated potential

+21 points estimated improvement from addressing 11 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+35Ahead
AI Readiness
Avg: 35+19Ahead
Performance
Avg: 55+17Ahead
Security
Avg: 40+0On par
Accessibility
Avg: 68+24Ahead

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.

Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.

Security score: 40/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 →