Skip to content
https://jungmaven.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
76
GRADE
C
FIX
3
REVIEW
1
PASS
5
INFO
0
Checks
9
5 PASS 1 REVIEW 3 FIX
F
Open Graph
Action
Open Graph tags need attention — social sharing previews may be incomplete.
FIX
Open Graph tags need attention — social sharing previews may be incomplete.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://cdn.shopify.com/s/files/1/1123/4596/files/GoGHP_desk_6c76b5c1-4bb2-4cf6-9930-3e212dadb22a.jpg?v=1743445416
Warning::
Missing og:title
The og:title tag controls the title shown in social sharing previews.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
URL: https://cdn.shopify.com/s/files/1/1123/4596/files/GoGHP_desk_6c76b5c1-4bb2-4cf6-9930-3e212dadb22a.jpg?v=1743445416

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.

Learn more ▾

Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.

Source: Open Graph Protocol / Facebook Sharing Debugger

The og:title tag controls the title shown in social sharing previews.

Why this matters

Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.

Learn more ▾

og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.

Source: Open Graph Protocol

The og:description tag controls the description in social sharing previews.

Why this matters

No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.

Learn more ▾

Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more ▾

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

The og:type tag helps social platforms categorize the content.

Why this matters

Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.

Learn more ▾

og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.

Source: Open Graph Protocol

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

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

jungmaven.com

No title set

No description

Preview quality · Twitter/X D · 50/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from <title>
  • twitter:description — falling back from <meta name=description>
  • twitter:image — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

JUNGMAVEN.COM

No title set

No description

Preview quality · Facebook F · 45/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://cdn.shopify.com/s/files/1/1123/4596/files/GoGHP_desk_6c76b5c1-4bb2-4cf6-9930-3e212dadb22a.jpg?v=1743445416
  • og:type — Add og:type — Recommended — tells Facebook the content category
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

No title set

jungmaven.com

Preview quality · LinkedIn A · 90/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://cdn.shopify.com/s/files/1/1123/4596/files/GoGHP_desk_6c76b5c1-4bb2-4cf6-9930-3e212dadb22a.jpg?v=1743445416

jungmaven.com

No title set

No description

Preview quality · Slack A · 90/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://cdn.shopify.com/s/files/1/1123/4596/files/GoGHP_desk_6c76b5c1-4bb2-4cf6-9930-3e212dadb22a.jpg?v=1743445416

Social preview quality

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

C · 68/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
F
Image Optimization
Action
6 issues found across 143 images
FIX
6 issues found across 143 images
Warning::
2 images significantly larger than display size
Resizing to display dimensions could save approximately 122 KB.
Got: ~122 KB wasted
Warning::
18 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
18 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 131 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 above-fold image(s) marked loading="lazy" (LCP anti-pattern)
Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://jungmaven.com/cdn/shop/files/LilyHP_desk2.jpg?v=1790979784&width=750.
Info::
4 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://jungmaven.com/cdn/shop/files/FeaturedBest2.jpg?v=1785549142, https://jungmaven.com/cdn/shop/files/FtdPrd-CambriaShort.jpg?v=1790000754&width=1114, https://jungmaven.com/cdn/shop/files/FtdPrd-YukonLS.jpg?v=1790001287&width=1114 (+1 more).
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

55/100

Site name appears as

Page titleHigh Quality Hemp Clothing
og:site_name—
twitter:site—
Organization.nameJungmaven

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • twitter:card missing
  • Consider adding contactPoint — helps appear in "contact us" rich results
  • Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link

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 / Twitter Card Depth
OG image dimensions and Twitter card configuration look healthy
PASS
OG image dimensions and Twitter card configuration look healthy
Info::
OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid
A+
Structured Data
2 JSON-LD block(s) found — structured data is well configured.
PASS
2 JSON-LD block(s) found — structured data is well configured.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
2 JSON-LD blocks found

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : Organization
6 properties Valid
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "name": "Jungmaven",
  "logo": "https:\/\/jungmaven.com\/cdn\/shop\/files\/logo.svg?v=1687809648\u0026width=500",
  "sameAs": [
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    ""
  ],
  "url": "https:\/\/jungmaven.com"
}
Block 2 : WebSite
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "Jungmaven",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/jungmaven.com\/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "url": "https:\/\/jungmaven.com"
}
A+
Rich Results Eligibility
2 JSON-LD block(s) declaring 2 schema type(s)
PASS
2 JSON-LD block(s) declaring 2 schema type(s)
Info::
SiteLinks Search Box markup detected
The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
Info::
2 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): Organization, WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
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