pavilionchurch.net scored 65/100 on the website scan.
Decent
pavilionchurch.net · Scanned 2026-05-29
19 passed6 warnings9 failed
- Technical SEO & indexability83
- On-page SEO & content40
- AI search / AEO / GEO readiness13
- Local SEO & entity signals0
- Performance & mobile48
What to fix first
-
✗
Meta description (150–160 chars)
No meta description tag.
What we’d do: Every Zorva-built page gets a custom meta description that improves SERP CTR.
-
✗
Social share cards (OG + Twitter)
No OpenGraph or Twitter Card metadata. Shares on Slack, X, LinkedIn, iMessage will look broken.
What we’d do: Every Zorva page gets OG + Twitter cards with a custom image.
-
✗
JSON-LD schema markup
No JSON-LD schema found. Google and AI search engines lose the structured signal.
What we’d do: Every Zorva-built site ships 8+ JSON-LD schema types — Organization, LocalBusiness, FAQPage, Review, Breadcrumb, Service, Product, HowTo.
-
✗
Business entity schema
No Organization or LocalBusiness schema. Google can't build a knowledge-graph entry without it.
What we’d do: Standard on every Zorva site, with NAP + service area + hours.
-
✗
llms.txt (AI summary file)
No llms.txt at the domain root. ChatGPT, Perplexity, and Claude have to guess your business facts.
What we’d do: Every Zorva site ships a tuned llms.txt — see /blog/llms-txt-small-business-setup-guide for the playbook.
Every check, by category (38 checks)
AI search / AEO / GEO readiness 13
-
✗
llms.txt (AI summary file)
No llms.txt at the domain root. ChatGPT, Perplexity, and Claude have to guess your business facts.
What we’d do: Every Zorva site ships a tuned llms.txt — see /blog/llms-txt-small-business-setup-guide for the playbook.
-
!
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.
-
✓
AI crawler permissions
robots.txt does not block major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.).
Performance & mobile 48
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint is 13.8 s. Ranking-impact threshold: ≤4s passes, ≤6s acceptable, >6s fails.
What we’d do: Common LCP killers: unoptimized hero images, render-blocking scripts, slow TTFB. Zorva sites hit sub-1.5s LCP via edge hosting + AVIF/WebP images.
-
✗
Page load time
Fetched in 5642ms. Over 2s costs you 30%+ of mobile visitors and hurts Google ranking directly.
What we’d do: Zorva sites are edge-hosted with sub-800ms TTFB and 95+ mobile PageSpeed scores.
-
✗
Compression
Response is uncompressed — every page is 3–5x larger over the wire than it needs to be.
What we’d do: Zorva Edge hosting auto-enables brotli + gzip with zero configuration.
-
!
Mobile PageSpeed score
Google scores your mobile performance at 57/100. Below 70 starts costing you ranking position.
What we’d do: Zorva sites are built around hitting 90+ on mobile — edge hosting, hand-coded HTML, lazy-loaded images.
-
•
Interaction to Next Paint (INP)
No real-user data available yet — Google's CrUX dataset needs enough traffic to report INP. Once your site gets a few hundred mobile visitors a month, INP will appear here.
-
•
HTTP/2 or HTTP/3
Couldn't detect HTTP/2 or HTTP/3 from response headers. Server may still support it, but isn't advertising via Alt-Svc.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift is 0.004. Google's threshold: ≤0.10 passes, ≤0.25 acceptable, >0.25 fails.
-
✓
HTML payload size
12KB on the wire (gzipped) · 75KB uncompressed. Lean and fast.
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)
No meta description tag.
What we’d do: Every Zorva-built page gets a custom meta description that improves SERP CTR.
-
✗
Social share cards (OG + Twitter)
No OpenGraph or Twitter Card metadata. Shares on Slack, X, LinkedIn, iMessage will look broken.
What we’d do: Every Zorva page gets OG + Twitter cards with a custom image.
-
!
Single H1
Found 2 H1s — Google + AI engines prefer one.
What we’d do: We restructure your heading hierarchy during the build.
-
✓
Page title (50–60 chars)
"Pavilion Church – Encounter. Connect. Build. Reach." — 57 chars, dead-on Google's sweet spot.
-
✓
Canonical URL
Canonical points to https://pavilionchurch.net/
-
✓
Sitemap.xml
Sitemap published with 9 URLs.
-
✓
Image alt text
All 3 images have alt attributes.
-
✓
Favicon
Favicon link tag present — branded SERP appearance + browser tab icon.
-
✓
HTML lang attribute
<html lang="en-US"> — accessibility + AI search signal.
-
✓
robots.txt
robots.txt present (119 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
-
✗
Security headers
Missing 4/4 baseline security headers: Content-Security-Policy, X-Content-Type-Options, 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.
-
!
HSTS header
No Strict-Transport-Security header. Modern browsers will still use HTTPS but won't lock the policy in.
What we’d do: Zorva-hosted sites set HSTS with a 1-year max-age + includeSubDomains by default.
-
✓
Mobile viewport
Viewport meta tag set for responsive design.
-
✓
Mobile zoom not blocked
Pinch-to-zoom is allowed. Accessibility-compliant.
-
✓
No fixed-width elements
No inline styles with hardcoded widths ≥360px that would overflow a phone viewport.
-
✓
HTTPS (SSL)
Site loads over HTTPS.
-
✓
HTTP → HTTPS redirect
Plain HTTP requests redirect (301) to HTTPS.
-
✓
Mixed content
No insecure http:// resources referenced on the page.
Structured data
-
✗
JSON-LD schema markup
No JSON-LD schema found. Google and AI search engines lose the structured signal.
What we’d do: Every Zorva-built site ships 8+ JSON-LD schema types — Organization, LocalBusiness, FAQPage, Review, Breadcrumb, Service, Product, HowTo.
-
✗
Business entity schema
No Organization or LocalBusiness schema. Google can't build a knowledge-graph entry without it.
What we’d do: Standard on every Zorva site, with NAP + service area + hours.
-
!
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.
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 pavilionchurch.net.
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.