springhavenmansion.com scored 88/100 on the website scan.
Solid
springhavenmansion.com · Scanned 2026-09-26
Unchanged from 2026-09-26
47 passed9 warnings4 failed
- Performance + Core Web Vitals62
- SEO basics100
- Mobile, accessibility + security97
- Structured data95
- AI search92
- Turning visitors into calls68
- Trust + E-E-A-T100
- Across the site75
What to fix first
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 8.1 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
What we’d do: The hero image sized and preloaded, no render-blocking scripts, a fast first byte: our pages paint in about a second.
-
✗
Image hygiene
4 images: 0 with dimensions, 0 in a modern format or through an image service, 3 lazy-loaded. 4 of 4 images have no width and height, so the page jumps as they load; none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
✗
Trust signals
No license, insurance, warranty, accreditation or years-in-business language on the home page.
What we’d do: We state license, insurance, guarantee and years on every page, and mark them up so the engines read them as facts.
-
✗
Descriptions across the site
the service page's description is 164 characters.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 68/100 (measured 2026-09-27). Google calls 50–89 “needs improvement”; lab runs vary, so we grade 70 and up as a pass.
What we’d do: Our sites score 90 and up on mobile: static HTML from an edge network, images sized and in modern formats, almost no JavaScript.
Every check, by category (65 checks)
Performance + Core Web Vitals 62
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 8.1 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
What we’d do: The hero image sized and preloaded, no render-blocking scripts, a fast first byte: our pages paint in about a second.
-
✗
Image hygiene
4 images: 0 with dimensions, 0 in a modern format or through an image service, 3 lazy-loaded. 4 of 4 images have no width and height, so the page jumps as they load; none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 68/100 (measured 2026-09-27). Google calls 50–89 “needs improvement”; lab runs vary, so we grade 70 and up as a pass.
What we’d do: Our sites score 90 and up on mobile: static HTML from an edge network, images sized and in modern formats, almost no JavaScript.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Render-blocking requests (about 1.3 s); Improve image delivery (about 1.0 s); Reduce unused JavaScript (about 0.5 s).
What we’d do: These are the first three things we would fix.
-
•
Interaction to Next Paint (INP)
No real-user INP yet — Google reports it once a page has enough visitors on Chrome. It measures how quickly the page reacts to a tap.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Time to first byte
First byte in 159 ms from our server.
-
✓
HTML weight
About 5 KB compressed (19 KB of HTML).
-
✓
Compression
Responses are compressed (br).
-
✓
HTTP/2 or HTTP/3
HTTP/2 negotiated, HTTP/3 advertised.
SEO basics 100
-
✓
Page title
“Spring Haven Mansion — Wedding Venue Near Nashville TN” — 54 characters, inside the 30–60 Google shows in full.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Meta description
155 characters — fills the space Google shows without being cut.
-
✓
Single H1
One H1: “Historic Nashville Wedding Venue”.
-
✓
Canonical URL
Canonical is https://springhavenmansion.com/.
-
✓
Social share cards
Open Graph title and image and a Twitter card with its own image. A share on any platform unfurls with a picture.
-
✓
Readable content in the HTML
736 words of readable text in the HTML.
-
✓
Sitemap
Sitemap at https://springhavenmansion.com/sitemap.xml — 5 URLs.
-
✓
Missing pages return 404
A made-up URL returns 404, so Google never indexes ghost pages.
-
✓
Image alt text
All 4 images have an alt attribute.
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
Language declared
<html lang="en">.
-
✓
Title and H1 differ
The title and the H1 are different, each doing its own job.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (1 group, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://springhavenmansion.com/sitemap.xml.
-
✓
Sitemap dates
5 pages with lastmod dates, from 2026-04-25 to 2026-09-26.
-
✓
Share image loads
The share image loads (image/jpeg, 260 KB).
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
Mobile, accessibility + security 97
-
!
www and apex agree
Both www.springhavenmansion.com and springhavenmansion.com serve the site. Two copies split links and signals; one should redirect to the other.
What we’d do: One host — www or apex — and a 301 from the other.
-
✓
Mobile viewport
The viewport meta tag is set for phones.
-
✓
HTTPS certificate
Valid until 2026-12-19, issued by Google Trust Services, on springhavenmansion.com and www.springhavenmansion.com.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://springhavenmansion.com/.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 93/100.
-
✓
Pinch-to-zoom allowed
Pinch-to-zoom is allowed.
-
✓
No fixed-width overflow
No inline widths of 400px or more that would push past a phone screen.
-
✓
HSTS header
Strict-Transport-Security is set — browsers remember to use HTTPS.
-
✓
Security headers
All four baseline security headers are set.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
Structured data 95
-
!
Business schema completeness
The business node has name, url, telephone, address, logo or image, sameAs but not areaServed, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served, logo and the same-as links to its profiles.
-
•
Article schema on the post
No post found in the sitemap to check.
-
•
Freshness dates in schema
No dateModified or datePublished in the schema. Not expected on every home page; a freshness date helps the engines trust the page is current.
-
✓
Business entity schema
Organization / LocalBusiness / EventVenue schema names the business.
-
✓
JSON-LD present and valid
11 schema types: Organization, LocalBusiness, EventVenue, PostalAddress, WebSite, Person, WebPage, SpeakableSpecification, ….
-
✓
FAQPage schema
FAQPage schema is present.
-
✓
FAQ questions visible on the page
All 4 questions in the FAQ schema are on the page.
-
✓
Speakable specification
A speakable specification is present.
AI search (AEO · AIO · GEO) 92
-
!
Extractable structure
Little for an engine to lift: 7 H2s, 1 H3s, 0 list items. Answer engines quote headed sections, lists and question-and-answer blocks.
What we’d do: Every page is written in headed sections with lists and question headings, so an answer can be lifted whole.
-
✓
AI crawlers allowed
robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.
-
✓
llms.txt
llms.txt is published (2 KB) — a plain statement of the business for the AI engines to read.
Turning visitors into calls 68
-
✗
Trust signals
No license, insurance, warranty, accreditation or years-in-business language on the home page.
What we’d do: We state license, insurance, guarantee and years on every page, and mark them up so the engines read them as facts.
-
!
Contact form
No form on the home page; a contact or quote page is linked. Every extra tap loses a share of visitors.
What we’d do: Our home pages carry the quote form itself — name, phone, what they need — stored before it is emailed, so nothing is lost.
-
!
Reviews on the page
The home page mentions “Kind Words” but shows no rating, review count or live reviews.
What we’d do: The live Google rating and count, and the newest reviews, on the home page.
-
!
Service area stated
The home page does not say which towns the business serves — visitors and engines both need it.
What we’d do: A service-area line in the hero and footer, a page per town, and areaServed in the schema.
-
•
Chat or text option
No chat or text option. Not a fault, but a share of visitors will not call; an assistant that answers in seconds, day and night, is the cheapest lead a site can add.
-
✓
Tappable phone number
2 tel: links — the number dials from a phone.
-
✓
Call to action in the first screen
A phone link, a form or a quote button appears in the top of the page.
Trust + E-E-A-T 100
-
✓
Analytics installed
Measured by Google Analytics, Cloudflare Web Analytics.
-
✓
A named person
A named person in the schema: Spring Haven Mansion Owner.
Across the site 75
-
✗
Descriptions across the site
the service page's description is 164 characters.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
!
FAQs on the inner pages
Neither inner page read carries a FAQ. The questions people ask about a service are what the answer engines quote.
What we’d do: Every service, area and post page carries its own researched questions — the ones people ask about that subject.
-
•
Pages read
Read with the home page: service page https://springhavenmansion.com/packages.html.
-
✓
Titles across the site
Each page read has its own title of 30–60 characters.
-
✓
Pages that repeat each other
The pages read share no sentences beyond the header, footer and calls to action.
Read with the home page: service page springhavenmansion.com/packages.html
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 springhavenmansion.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.