Skip to content
https://LorientHaus.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Checks
9
5 PASS 3 REVIEW 1 FIX
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.12:1 (393×352) is outside Facebook's recommended ~1.91:1
Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 393×352 give a ratio of 1.12: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.12:1 (393×352)
Warning::
Twitter card is `summary_large_image` but OG image is 393×352 (ratio 1.12:1) -- closer to square
`twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (393×352, aspect ratio 1.12: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: 393×352 declared with summary_large_image card
C
Image Optimization
Action
4 issues found across 117 images
REVIEW
4 issues found across 117 images
Info::
21 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
113 of 117 images use legacy formats
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://lorienthaus.com/cdn/shop/files/LH_BW_log0_v2.png?height=100&v=1748020289.
Info::
10 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://lorienthaus.com/cdn/shop/files/New_Arrivals_desktop.png?v=1773529549&width=1000, https://lorienthaus.com/cdn/shop/files/614863354_765372309943596_6673473507979934541_n.jpg?v=1772404383&width=1000, https://lorienthaus.com/cdn/shop/files/Ao_ba_ba_desktop.png?v=1773529549&width=1000 (+7 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

62/100

Site name appears as

Page titleVisa
og:site_nameL'Orient Haus
twitter:site—
Organization.nameL'Orient Haus

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

4/15

Organization schema present but missing all recommended fields

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • Organization schema missing logo — add a logo property pointing to a square PNG
  • Organization schema missing url — point it at the canonical homepage
  • 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
Open Graph tags are well configured for social sharing.
PASS
Open Graph tags are well configured for social sharing.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: http://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099
Info::
og:title is short (15 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 15 chars Expected: 25–60 chars
URL: http://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099

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

URL: 15 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

Preview

LorientHaus.com

Lorienthaus.com

L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary_large_image
  • twitter:title — Lorienthaus.com
  • twitter:description — L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.
  • twitter:image — https://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099

LORIENTHAUS.COM

Lorienthaus.com

L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.

Preview quality · Facebook A+ · 100/100
  • og:title — Lorienthaus.com
  • og:description — L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.
  • og:image — http://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099
  • og:type — website
  • og:url — https://lorienthaus.com/
  • og:site_name — L'Orient Haus

  • og:image is below recommended size (393×352)

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

Lorienthaus.com

LorientHaus.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — Lorienthaus.com
  • og:description — L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.
  • og:image — http://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099

LorientHaus.com

Lorienthaus.com

L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.

Preview quality · Slack A+ · 100/100
  • og:title — Lorienthaus.com
  • og:description — L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia.
  • og:image — http://lorienthaus.com/cdn/shop/files/LH_logo_blue_db30a4f8-b32e-47ac-bc19-1fd12e8e9b0c.png?v=1754925099

Social preview quality

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

A+ · 100/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
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.
Warning::
Missing required property "name" for Organization
The "name" property is required for the Organization schema type.
Info::
Missing recommended property "url" for Organization
Adding "url" can improve how search engines display your content.
Info::
Missing recommended property "logo" for Organization
Adding "logo" can improve how search engines display your content.
Info::
Missing recommended property "sameAs" for Organization
Adding "sameAs" can improve how search engines display your content.
Info::
Missing recommended property "sameAs" for Organization
Adding "sameAs" can improve how search engines display your content.
Info::
2 JSON-LD blocks found

The "name" property is required for the Organization schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

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

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

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

Adding "sameAs" 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
2 properties Valid
Missing required property: name
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://lorienthaus.com/#organization",
      "name": "L\u0026#39;Orient Haus",
      "url": "https:\/\/lorienthaus.com",
      "description": "L’Orient Haus is a curated online boutique offering luxury fashion, fragrances, and artisanal treasures from Asia. ",
      "sameAs": []
    },
    {
      "@type": "WebSite",
      "@id": "https://lorienthaus.com/#website",
      "name": "L\u0026#39;Orient Haus",
      "url": "https:\/\/lorienthaus.com",
      "publisher": {
        "@id": "https://lorienthaus.com/#organization"
      },
      "potentialAction": {
        "@type": "SearchAction",
        "target": "/search?q={search_term_string}",
        "query-input": "required name=search_term_string"
      }
    }
  ]
}
Block 2 : Organization
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "name": "L\u0026#39;Orient Haus",
  "logo": "https:\/\/lorienthaus.com\/cdn\/shop\/files\/LH_BW_log0_v2.png?v=1748020289\u0026width=500",
  "url": "https:\/\/lorienthaus.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 (×2), WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
Warning::
2 Organization blocks on the page -- only one should describe the publishing entity
Multiple `Organization` JSON-LD blocks confuse search engines about which is canonical. Google may suppress knowledge-panel features when the entity identity is ambiguous. Pick one Organization block (typically representing the publisher) and remove the rest, or merge by giving the duplicates explicit `@id` URIs that point to a single canonical entity.
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