Search the site · Ask Zorva

Results appear as you type. Press Enter and Zorva answers from this site’s own pages.

Public scan result · scored by the Zorva Labs website scan

garysomerhalder.com scored 64/100 on the website scan.

Decent

garysomerhalder.com · Scanned 2026-08-26

17 passed7 warnings8 failed

  • Technical SEO & indexability48
  • On-page SEO & content23
  • AI search / AEO / GEO readiness39
  • Local SEO & entity signals0
  • Performance & mobile71

What to fix first

  • ✗

    Meta description (150–160 chars)

    Description is only 104 chars. Way under the 150-char sweet spot — Google often rewrites short descriptions, losing your messaging.

    What we’d do: We write 150–160 char descriptions so Google uses what you wrote.

  • ✗

    Single H1

    No H1 heading found.

    What we’d do: We set a clear keyword-anchored H1 on every page.

  • ✗

    Mobile zoom not blocked

    Your viewport meta tag blocks pinch-to-zoom (user-scalable=no or maximum-scale=1). That's a WCAG 2.1 accessibility violation and Google penalizes it.

    What we’d do: Zorva sites always allow pinch-to-zoom — required for accessibility compliance and Google ranking.

  • ✗

    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.

Every check, by category (38 checks)

AI search / AEO / GEO readiness 39

  • !

    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 71

  • !

    Largest Contentful Paint (LCP)

    Largest Contentful Paint is 4.0 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.

  • !

    HTML payload size

    104KB on the wire (gzipped) · 361KB uncompressed. Working, but bigger HTML pushes TTFB and First Byte cost on slow connections.

    What we’d do: Hand-coded Zorva sites typically ship 20–50KB gzipped per page.

  • •

    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.

  • ✓

    Mobile PageSpeed score

    Google scores your mobile performance at 77/100 — above the ranking-impact threshold.

  • ✓

    Cumulative Layout Shift (CLS)

    Cumulative Layout Shift is 0. Google's threshold: ≤0.10 passes, ≤0.25 acceptable, >0.25 fails.

  • ✓

    Page load time

    Fetched in 684ms — fast.

  • ✓

    Compression

    Server is using gzip compression — saves 60–80% of bytes.

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 only 104 chars. Way under the 150-char sweet spot — Google often rewrites short descriptions, losing your messaging.

    What we’d do: We write 150–160 char descriptions so Google uses what you wrote.

  • ✗

    Single H1

    No H1 heading found.

    What we’d do: We set a clear keyword-anchored H1 on every page.

  • ✗

    Sitemap.xml

    No /sitemap.xml found. Google + AI crawlers have to guess at your full URL inventory.

    What we’d do: Every Zorva site auto-generates sitemap.xml from its full route + blog + glossary inventory.

  • ✗

    404 page handling

    A non-existent URL returned 200 instead of 404. Soft 404s let Google index ghost pages and waste your crawl budget.

    What we’d do: Zorva sites return proper 404s on missing routes — no soft-404 SEO penalty.

  • !

    Page title (50–60 chars)

    Title is 36 chars. Google's sweet spot is 50–60 — yours works but isn't optimal.

    What we’d do: Zorva-built titles target 50–60 chars exactly so they never truncate in the SERP.

  • !

    Sitemap directive in robots.txt

    robots.txt exists but doesn't include a `Sitemap:` line — Google has to guess the sitemap location.

    What we’d do: Zorva-published robots.txt always includes the Sitemap directive.

  • •

    Image alt text

    No images detected on the homepage.

  • •

    Title vs H1 differentiation

    Skipped — no H1 found on the page.

  • ✓

    Canonical URL

    Canonical points to https://garysomerhalder.com/

  • ✓

    Social share cards (OG + Twitter)

    OpenGraph and Twitter Card metadata present.

  • ✓

    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 (368156 bytes).

Mobile, accessibility + security

  • ✗

    Mobile zoom not blocked

    Your viewport meta tag blocks pinch-to-zoom (user-scalable=no or maximum-scale=1). That's a WCAG 2.1 accessibility violation and Google penalizes it.

    What we’d do: Zorva sites always allow pinch-to-zoom — required for accessibility compliance and Google ranking.

  • ✗

    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.

  • ✓

    Mobile viewport

    Viewport meta tag set for responsive design.

  • ✓

    No fixed-width elements

    No inline styles with hardcoded widths ≥360px that would overflow a phone viewport.

  • ✓

    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.

  • ✓

    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.

Want this fixed?

We can fix every issue on garysomerhalder.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.

ReplyOne business day
ProposalWritten · scoped · priced
ContractMonth to month
Proposal request

Tell us what you need

No spam · One business day reply · Month to month

garysomerhalder.com — 64/100 website scan | Zorva Labs