Skip to content
https://dearammi.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Checks
9
5 PASS 3 REVIEW 1 FIX
F
Image Optimization
Action
6 issues found across 59 images
FIX
6 issues found across 59 images
Warning::
4 images significantly larger than display size
Resizing to display dimensions could save approximately 63 KB.
Got: ~63 KB wasted
Warning::
34 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
9 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 47 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::
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://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124&width=70, https://dearammi.com/cdn/shop/files/Eye_Max_copy.png?v=1776655962&width=200, https://dearammi.com/cdn/shop/files/i.png?v=1777357948&width=200 (+7 more).
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.02:1 (603×590) is outside Facebook's recommended ~1.91:1
Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 603×590 give a ratio of 1.02: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.02:1 (603×590)
Warning::
Twitter card is `summary_large_image` but OG image is 603×590 (ratio 1.02:1) -- closer to square
`twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (603×590, aspect ratio 1.02: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: 603×590 declared with summary_large_image card
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

62/100

Site name appears as

Page titleDear Ammi
og:site_nameDear Ammi
twitter:site—
Organization.name—

Consistent

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

0/15

Contact info discoverable

10/10

contact page, mailto link + tel link

Findings

  • Missing brand name in: twitter:site, Organization.name
  • 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
  • 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
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://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124
Info::
og:title is short (9 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 9 chars Expected: 25–60 chars
Info::
og:description is short (9 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 9 chars Expected: 55–200 chars
URL: http://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124

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: 9 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

URL: 9 chars

Ideal length is 55–200 characters for social sharing previews.

Expected: 55–200 chars
Why this matters

og:description very short — provides little context in social cards.

Source: Open Graph Protocol

Preview

dearammi.com

Dear Ammi

Dear Ammi

Preview quality · Twitter/X A+ · 95/100
  • twitter:card — summary_large_image
  • twitter:title — Dear Ammi
  • twitter:description — Dear Ammi
  • twitter:image — falling back from og:image

DEARAMMI.COM

Dear Ammi

Dear Ammi

Preview quality · Facebook A+ · 100/100
  • og:title — Dear Ammi
  • og:description — Dear Ammi
  • og:image — http://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124
  • og:type — website
  • og:url — https://dearammi.com/
  • og:site_name — Dear Ammi

  • og:image is below recommended size (603×590)

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

Dear Ammi

dearammi.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — Dear Ammi
  • og:description — Dear Ammi
  • og:image — http://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124

dearammi.com

Dear Ammi

Dear Ammi

Preview quality · Slack A+ · 100/100
  • og:title — Dear Ammi
  • og:description — Dear Ammi
  • og:image — http://dearammi.com/cdn/shop/files/Untitled-2.png?v=1768398124

Social preview quality

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

A+ · 98/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 : BreadcrumbList
3 properties Valid
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://dearammi.com"
    }
  ]
}
Block 2 : WebSite
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "Dear Ammi",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/dearammi.com\/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "url": "https:\/\/dearammi.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): BreadcrumbList, 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
1 media element(s) found, none autoplay
PASS
1 media element(s) found, none autoplay
Info::
1 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