www.belmontmansion.com scored 81/100 on the website scan.
Solid
belmontmansion.com · Scanned 2026-05-15
23 passed6 warnings3 failed
- Technical SEO & indexability72
- On-page SEO & content82
- AI search / AEO / GEO readiness43
- Local SEO & entity signals100
- Performance & mobile75
What to fix first
-
✗
HTML payload size
231KB on the wire (gzipped) · 1331KB uncompressed. Bloat-territory — usually inline scripts, embedded CSS, or builder boilerplate.
What we’d do: Zorva hand-coded sites are 20–50KB gzipped per page — fast on every connection.
-
✗
Mixed content
Found 3 insecure http:// references on an https:// page. Browsers warn / block these.
What we’d do: Zorva sites are 100% HTTPS — we replace any http:// asset URLs at build time.
-
✗
Security headers
Missing 3/4 baseline security headers: Content-Security-Policy, X-Frame-Options, Referrer-Policy.
What we’d do: Zorva sites ship CSP, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy by default.
-
!
Meta description (150–160 chars)
Description is 140 chars. Google's sweet spot is 150–160 — yours works but isn't using the full SERP real estate (or just over).
What we’d do: Zorva-built descriptions hit 150–160 chars exactly for max SERP CTR.
-
!
Possible fixed-width overflow
Found 1 inline width(s) at 980px — these may overflow a 360px phone viewport.
What we’d do: Zorva sites use fluid widths and CSS Grid/Flex so every layout scales to phone, tablet, and desktop.
Every check, by category (35 checks)
AI search / AEO / GEO readiness 43
-
!
Speakable spec (voice/AEO)
No SpeakableSpecification. Voice engines (Siri, Alexa, Google Assistant) have nothing tuned to read aloud.
What we’d do: We add Speakable + data-speakable hooks to TLDR + key paragraphs on every page.
-
✓
llms.txt (AI summary file)
llms.txt is published — AI engines have a structured business summary to cite.
-
✓
AI crawler permissions
robots.txt does not block major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.).
Performance & mobile 75
-
✗
HTML payload size
231KB on the wire (gzipped) · 1331KB uncompressed. Bloat-territory — usually inline scripts, embedded CSS, or builder boilerplate.
What we’d do: Zorva hand-coded sites are 20–50KB gzipped per page — fast on every connection.
-
•
Mobile PageSpeed score
Couldn't fetch Google PageSpeed Insights for this URL. PageSpeed Insights returned 500. PSI couldn't analyze this URL. The site may block its crawler or have a redirect chain.
-
✓
Page load time
Fetched in 144ms — fast.
-
✓
Compression
Server is using br compression — saves 60–80% of bytes.
-
✓
HTTP/2 or HTTP/3
Server advertises H3 via Alt-Svc.
Trust / E-E-A-T / reputation
-
!
Author / Person schema
No Person schema. Google + AI engines prefer content with a named human author entity.
What we’d do: We add a Person/Founder schema graph on the home + about + team pages.
SEO basics
-
!
Meta description (150–160 chars)
Description is 140 chars. Google's sweet spot is 150–160 — yours works but isn't using the full SERP real estate (or just over).
What we’d do: Zorva-built descriptions hit 150–160 chars exactly for max SERP CTR.
-
✓
Page title (50–60 chars)
"Belmont Mansion | Nashville Historic House Museum |" — 51 chars, dead-on Google's sweet spot.
-
✓
Single H1
Exactly one H1 on the page.
-
✓
Canonical URL
Canonical points to https://www.belmontmansion.com
-
✓
Social share cards (OG + Twitter)
OpenGraph and Twitter Card metadata present.
-
✓
Sitemap.xml
Sitemap published with 8 URLs.
-
✓
Image alt text
All 13 images have alt attributes.
-
✓
Favicon
Favicon link tag present — branded SERP appearance + browser tab icon.
-
✓
HTML lang attribute
<html lang="en"> — accessibility + AI search signal.
-
✓
robots.txt
robots.txt present (277 bytes).
-
✓
Sitemap directive in robots.txt
robots.txt points crawlers at the sitemap explicitly.
-
✓
Title vs H1 differentiation
Title and H1 are distinct — Google reads them as complementary signals.
-
✓
404 page handling
Random URLs return a proper 404 — Google won't index ghost pages.
Mobile, accessibility + security
-
✗
Mixed content
Found 3 insecure http:// references on an https:// page. Browsers warn / block these.
What we’d do: Zorva sites are 100% HTTPS — we replace any http:// asset URLs at build time.
-
✗
Security headers
Missing 3/4 baseline security headers: Content-Security-Policy, X-Frame-Options, Referrer-Policy.
What we’d do: Zorva sites ship CSP, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy by default.
-
!
Possible fixed-width overflow
Found 1 inline width(s) at 980px — these may overflow a 360px phone viewport.
What we’d do: Zorva sites use fluid widths and CSS Grid/Flex so every layout scales to phone, tablet, and desktop.
-
✓
Mobile viewport
Viewport meta tag set for responsive design.
-
✓
Mobile zoom not blocked
Pinch-to-zoom is allowed. Accessibility-compliant.
-
✓
HTTPS (SSL)
Site loads over HTTPS.
-
✓
HSTS header
Strict-Transport-Security is set — browsers force HTTPS forever.
-
✓
HTTP → HTTPS redirect
Plain HTTP requests redirect (301) to HTTPS.
Structured data
-
!
JSON-LD schema markup
Found 2 schema types: WebSite, LocalBusiness.
What we’d do: Zorva sites typically run 8+ schema types per page for richer SERP + AI citations.
-
!
FAQPage schema
No FAQPage schema. AI Overview + voice engines lean heavily on this format.
What we’d do: We add FAQPage schema to every site, auto-extracted from the visible Q&A blocks.
-
•
Article / BlogPosting schema
Not a blog/article URL — skipped.
-
•
HowTo schema
No HowTo schema. Optional — only valuable on pages that describe a step-by-step process.
-
✓
Business entity schema
Organization or LocalBusiness schema present.
Want these fixed?
Every fix above is part of the work Zorva Labs does. Tell us the business and what you want from the site, and a written, priced proposal comes back in one business day.
We can fix every issue on www.belmontmansion.com.
Zorva Labs builds, hosts and grows websites for businesses across the United States — including the fixes flagged above. Every engagement is priced to the project, with a written proposal in one business day.