spokanestop.com — Website Report
Scored 61/100 · Scanned with Foglift
Mean of SEO, Performance, Security, and Accessibility.
spokanestop.com scored 61. Addressing the 13 listed issues could raise its estimated score to 83.
Quick wins
~78 min total fix timehttps://spokanestop.com/ · 2026-09-07
Scanned with Foglift · Technical Audit + AI Readiness analysis
AI Search Readiness Risk
Your AI Readiness score of 41/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 →
AI Action Plan
Website Analysis for https://spokanestop.com/ Site Technical Health: 61/100. AI Readiness is 41/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 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. Slow server response — Server responded in 4.6s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance. QUICK WINS (Warnings): 1. Missing X-Content-Type-Options header — Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing. 2. Missing X-Frame-Options header — Set X-Frame-Options to prevent click
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 Readiness
Technical and authority signals that support AI systems in accessing, understanding, and reusing your content
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 Spokanestop?
When users ask AI about your industry, are you recommended?
Start with weekly Perplexity checks for Spokanestop. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.
Issues Found (13)
Enable HTTP Strict Transport Security to force HTTPS connections.
# 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' }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'" }Server responded in 4.6s. Aim for under 200ms Time to First Byte (TTFB). Check your server configuration, database queries, and hosting performance.
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Set X-Frame-Options to prevent clickjacking attacks.
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }Add a Referrer-Policy header to control information leakage.
# 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' }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 64 characters. Keep it under 60 for best display in search results.
Missing og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.
<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">Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology.
Your HTML is 505KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
5 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
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>Your Potential Score
61
Now
83
Estimated potential
+22 points estimated improvement from addressing 13 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.
Weekly Perplexity while active · No credit card required
Compare paid plans — from $49/moIndustry Benchmark
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.