Skip to content
https://www.91servings.in

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
79
GRADE
C
FIX
4
REVIEW
0
PASS
5
INFO
0
Checks
9
5 PASS 4 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.
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.

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

www.91servings.in

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

WWW.91SERVINGS.IN

No title set

No description

Preview quality · Facebook F · 35/100

Description will be truncated (159 chars / 155 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://cdn.shopify.com/s/files/1/0626/3327/9657/files/91-servings-light-logo_0d75df6e-93bc-488b-a59e-25ebc3ac79db.pn...
  • 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

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

    → Tighten og:description to ≤155 characters

  • og:image is too small for Facebook (400×120)

    → Upload an image at least 200×200 — recommended 1200×630 for large cards

No title set

www.91servings.in

Preview quality · LinkedIn B · 80/100

Description will be truncated (159 chars / 150 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://cdn.shopify.com/s/files/1/0626/3327/9657/files/91-servings-light-logo_0d75df6e-93bc-488b-a59e-25ebc3ac79db.pn...

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

    → Tighten og:description to ≤150 characters

  • og:image is too small for LinkedIn (400×120)

    → Upload an image at least 200×200

www.91servings.in

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/0626/3327/9657/files/91-servings-light-logo_0d75df6e-93bc-488b-a59e-25ebc3ac79db.pn...

Social preview quality

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

D · 63/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
D
Image Optimization
Action
4 issues found across 125 images
FIX
4 issues found across 125 images
Warning::
53 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
48 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
112 of 125 images use legacy formats
Warning::
4 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

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

D

49/100

Site name appears as

Page titleBuy Authentic Proteins Online in India
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

10/10

contact page, mailto link + tel link

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:title missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel

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
1 OG/Twitter depth issue(s) detected
PASS
1 OG/Twitter depth issue(s) detected
Warning::
og:image dimensions 400×120 are below Facebook's 200×200 minimum
Facebook treats OG images smaller than 200×200 as too small to display as a preview. The actual image will likely be ignored and shares will fall back to no preview image. Use at least 200×200; optimal is 1200×630 for the standard 1.91:1 wide preview.
Got: 400×120
A+
Structured Data
1 JSON-LD block(s) found — structured data is well configured.
PASS
1 JSON-LD block(s) found — structured data is well configured.

JSON-LD Blocks

Block 1 : BreadcrumbList
3 properties Valid
{
  "@context": "http://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": "1",
      "item": {
        "@type": "Website",
        "@id": "https://www.91servings.in",
        "name": "91servings"
      }
    }
  ]
}
A+
Rich Results Eligibility
1 JSON-LD block(s) declaring 1 schema type(s)
PASS
1 JSON-LD block(s) declaring 1 schema type(s)
Info::
1 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): BreadcrumbList 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