Skip to content
https://potentialspouse.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Checks
9
4 PASS 4 REVIEW 1 FIX
D
Image Optimization
Action
4 issues found across 1 images
FIX
4 issues found across 1 images
Warning::
All 1 images use legacy formats (JPEG/PNG/GIF)
WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
Warning::
1 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
Info::
1 image(s) wider than 400px without srcset (no responsive serving)
These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://potentialspouse.com/images/hero-bg-8d8495e5b71cb1f46987f3916900964f.jpg?vsn=d.
Info::
1 image(s) rendered at a different aspect ratio than the source
The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://potentialspouse.com/images/hero-bg-8d8495e5b71cb1f46987f3916900964f.jpg?vsn=d.
B
Open Graph / Twitter Card Depth
2 OG/Twitter depth issue(s) detected
REVIEW
2 OG/Twitter depth issue(s) detected
Info::
og:image aspect ratio 1.00:1 (1024×1024) is outside Facebook's recommended ~1.91:1
Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 1024×1024 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
Got: 1.00:1 (1024×1024)
Warning::
Twitter card is `summary_large_image` but OG image is 1024×1024 (ratio 1.00:1) -- closer to square
`twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (1024×1024, aspect ratio 1.00:1) are closer to square than wide. Twitter will crop the image to fit the wide format, often badly. Either: (1) provide a wider image (~2:1 ratio recommended; minimum 600×314, optimal 1200×630), or (2) change `twitter:card` to `summary` which uses a square thumbnail crop.
Got: 1024×1024 declared with summary_large_image card
C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
C
Rich Results Eligibility
Action
No JSON-LD found -- no rich-result eligibility
REVIEW
No JSON-LD found -- no rich-result eligibility
Info::
No JSON-LD structured data on the page
No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

C

60/100

Site name appears as

Page titleFind your potential spouse anonymously · PotentialSpouse
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes, apple-touch-icon + SVG

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • No Organization schema — Google can't render your logo in the knowledge panel
  • No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
A
Open Graph
Open Graph tags are well configured for social sharing.
PASS
Open Graph tags are well configured for social sharing.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

Source: Open Graph Protocol

Preview

potentialspouse.com

Find your potential spouse anonymously

Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately for a serious partner without your friends, family, or coworkers seeing you look.

Preview quality · Twitter/X A · 90/100
  • twitter:card — summary_large_image
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — https://potentialspouse.com/images/og-image.png?v=1

POTENTIALSPOUSE.COM

Find your potential spouse anonymously

Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately for a serious partner without your friends, family, or coworkers seeing you look.

Preview quality · Facebook B · 80/100

Description will be truncated (196 chars / 155 max)

  • og:title — Find your potential spouse anonymously
  • og:description — Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately fo...
  • og:image — https://potentialspouse.com/images/og-image.png?v=1
  • og:type — website
  • og:url — https://potentialspouse.com/
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

  • Description will be truncated on Facebook (196 chars, max 155)

    → Tighten og:description to ≤155 characters

  • og:image is below recommended size (1024×1024)

    → Upload an image ≥1200×630 for the large preview card

Find your potential spouse anonymously

potentialspouse.com

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (196 chars / 150 max)

  • og:title — Find your potential spouse anonymously
  • og:description — Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately fo...
  • og:image — https://potentialspouse.com/images/og-image.png?v=1

  • Description will be truncated on LinkedIn (196 chars, max 150)

    → Tighten og:description to ≤150 characters

potentialspouse.com

Find your potential spouse anonymously

Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately for a serious partner without your friends, family, or coworkers seeing you look.

Preview quality · Slack A+ · 100/100
  • og:title — Find your potential spouse anonymously
  • og:description — Private, photo-free matchmaking for marriage-minded people. No public profile, no email required. Search privately fo...
  • og:image — https://potentialspouse.com/images/og-image.png?v=1

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

A · 91/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image———
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback