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

musiccitycloset.com scored 68/100 on the website scan.

Decent

musiccitycloset.com · Scanned 2026-07-28

20 passed6 warnings8 failed

  • Technical SEO & indexability65
  • On-page SEO & content16
  • AI search / AEO / GEO readiness39
  • Local SEO & entity signals0
  • Performance & mobile84

What to fix first

  • ✗

    Page title (50–60 chars)

    Title is 113 chars. Google truncates at ~580px (~60 chars) — the back half of your title is hidden in search results.

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

  • ✗

    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.

  • ✗

    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.

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 84

  • !

    Page load time

    Fetched in 1922ms. Acceptable but Google's Core Web Vitals favors sub-1s LCP.

    What we’d do: Zorva sites are edge-hosted on Cloudflare's global CDN with sub-800ms TTFB worldwide.

  • •

    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 93/100 — above the ranking-impact threshold.

  • ✓

    Largest Contentful Paint (LCP)

    Largest Contentful Paint is 2.6 s. Ranking-impact threshold: ≤4s passes, ≤6s acceptable, >6s fails.

  • ✓

    Cumulative Layout Shift (CLS)

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

  • ✓

    HTML payload size

    27KB on the wire (gzipped) · 158KB uncompressed. Lean and 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

  • ✗

    Page title (50–60 chars)

    Title is 113 chars. Google truncates at ~580px (~60 chars) — the back half of your title is hidden in search results.

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

  • ✗

    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.

  • ✗

    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.

  • !

    Single H1

    Found 6 H1s — Google + AI engines prefer one.

    What we’d do: We restructure your heading hierarchy during the build.

  • ✓

    Canonical URL

    Canonical points to https://musiccitycloset.com/

  • ✓

    Sitemap.xml

    Sitemap published with 1 URL.

  • ✓

    Image alt text

    All 5 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 (120 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.

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 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.

  • ✓

    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.

Want this fixed?

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