Skip to content
https://dearduchessboutique.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Checks
9
5 PASS 4 REVIEW
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.32:1 (3024×2286) is outside Facebook's recommended ~1.91:1
Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 3024×2286 give a ratio of 1.32: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.32:1 (3024×2286)
Warning::
Twitter card is `summary_large_image` but OG image is 3024×2286 (ratio 1.32:1) -- closer to square
`twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (3024×2286, aspect ratio 1.32: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: 3024×2286 declared with summary_large_image card
C
Image Optimization
Action
4 issues found across 78 images
REVIEW
4 issues found across 78 images
Warning::
50 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
34 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
72 of 78 images use legacy formats
Info::
8 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://dearduchessboutique.com/cdn/shop/files/Chocolate_plum_zippered_sweater_by_525.webp?v=1792973847&width=360, https://dearduchessboutique.com/cdn/shop/files/81D35D09-34DB-4933-8A31-C62C098E8D0F.jpg?v=1792775932&width=360, https://dearduchessboutique.com/cdn/shop/files/B43F01C4-8D26-4EDA-B3CE-DEF1F69A13C4.jpg?v=1792775880&width=360 (+5 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

67/100

Site name appears as

Page titleVisa
og:site_nameDear Duchess Boutique
twitter:site—
Organization.nameDear Duchess Boutique

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

20/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
  • 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://dearduchessboutique.com/cdn/shop/files/image_50421249.jpg?v=1761673862
URL: http://dearduchessboutique.com/cdn/shop/files/image_50421249.jpg?v=1761673862

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

Preview

dearduchessboutique.com

Dear Duchess, Boston Fashion Boutique

Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Centre, MA. Shop online or at our brick and mortar store.

Preview quality · Twitter/X A+ · 95/100
  • twitter:card — summary_large_image
  • twitter:title — Dear Duchess, Boston Fashion Boutique
  • twitter:description — Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Ce...
  • twitter:image — falling back from og:image

DEARDUCHESSBOUTIQUE.COM

Dear Duchess, Boston Fashion Boutique

Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Centre, MA. Shop online or at our brick and mortar store.

Preview quality · Facebook A+ · 95/100

Description will be truncated (172 chars / 155 max)

  • og:title — Dear Duchess, Boston Fashion Boutique
  • og:description — Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Ce...
  • og:image — http://dearduchessboutique.com/cdn/shop/files/image_50421249.jpg?v=1761673862
  • og:type — website
  • og:url — https://dearduchessboutique.com/
  • og:site_name — Dear Duchess Boutique

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

    → Tighten og:description to ≤155 characters

Dear Duchess, Boston Fashion Boutique

dearduchessboutique.com

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (172 chars / 150 max)

  • og:title — Dear Duchess, Boston Fashion Boutique
  • og:description — Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Ce...
  • og:image — http://dearduchessboutique.com/cdn/shop/files/image_50421249.jpg?v=1761673862

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

    → Tighten og:description to ≤150 characters

dearduchessboutique.com

Dear Duchess, Boston Fashion Boutique

Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Centre, MA. Shop online or at our brick and mortar store.

Preview quality · Slack A+ · 100/100
  • og:title — Dear Duchess, Boston Fashion Boutique
  • og:description — Dear Duchess - A thoughtfully curated women's boutique for updated fashion and personal styling, located in Newton Ce...
  • og:image — http://dearduchessboutique.com/cdn/shop/files/image_50421249.jpg?v=1761673862

Social preview quality

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

A+ · 96/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.
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": "Dear Duchess Boutique",
  "logo": "https:\/\/dearduchessboutique.com\/cdn\/shop\/files\/Dear_Duchess_2.png?v=1706304655\u0026width=500",
  "sameAs": [
    "",
    "https:\/\/www.facebook.com\/dearduchessboutique",
    "",
    "https:\/\/www.instagram.com\/dearduchessboutique\/",
    "",
    "",
    "",
    "",
    ""
  ],
  "url": "https:\/\/dearduchessboutique.com"
}
Block 2 : WebSite
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "Dear Duchess Boutique",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/dearduchessboutique.com\/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "url": "https:\/\/dearduchessboutique.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
14 media element(s) found, none autoplay
PASS
14 media element(s) found, none autoplay
Info::
14 media element(s) found, none autoplay
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback