Skip to content
http://mytrendyes.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
84
GRADE
B
FIX
3
REVIEW
1
PASS
5
INFO
0
Checks
9
5 PASS 1 REVIEW 3 FIX
F
Image Optimization
Action
6 issues found across 41 images
FIX
6 issues found across 41 images
Warning::
2 images significantly larger than display size
Resizing to display dimensions could save approximately 33 KB.
Got: ~33 KB wasted
Warning::
16 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
14 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
20 of 41 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://mytrendyes.com/cdn/shop/files/1_1.png?v=1769745566&width=1100.
Info::
2 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://mytrendyes.com/cdn/shop/files/1_1.png?v=1769745566&width=1100, https://mytrendyes.com/cdn/shop/files/DM_20251220045504_001.png?v=1772675686&width=360.
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

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

D

47/100

Site name appears as

Page titleVisa
og:site_namemytrendyes
twitter:site—
Organization.namemytrendyes

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

14/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
  • No social share image — shared links render as bare URLs
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:image 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.

B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
og:title is short (10 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 10 chars Expected: 25–60 chars
Info::
og:description is short (10 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 10 chars Expected: 55–200 chars

The og:image tag provides a preview image for social sharing.

Why this matters

No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.

Learn more ▾

Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.

Source: Open Graph Protocol

URL: 10 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: 10 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

No image set

mytrendyes.com

mytrendyes

mytrendyes

Preview quality · Twitter/X C · 65/100
  • twitter:card — summary_large_image
  • twitter:title — mytrendyes
  • twitter:description — mytrendyes
  • twitter:image — Add twitter:image — preview card without an image looks broken

  • No preview image for Twitter/X

    → Add og:image or twitter:image (≥300×157 for summary_large_image)

No image set

MYTRENDYES.COM

mytrendyes

mytrendyes

Preview quality · Facebook C · 65/100
  • og:title — mytrendyes
  • og:description — mytrendyes
  • og:image — Add og:image — preview card without an image looks broken
  • og:type — website
  • og:url — https://mytrendyes.com/
  • og:site_name — mytrendyes

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

mytrendyes

mytrendyes.com

Preview quality · LinkedIn C · 65/100
  • og:title — mytrendyes
  • og:description — mytrendyes
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

mytrendyes.com

mytrendyes

mytrendyes

Preview quality · Slack B · 80/100
  • og:title — mytrendyes
  • og:description — mytrendyes
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image — Slack unfurl will be text-only

    → Add og:image or twitter:image

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———
A+
Mixed Content
Page is served over HTTP — mixed content check is not applicable.
PASS
Page is served over HTTP — mixed content check is not applicable.
Info::
Page is served over HTTP — mixed content check is not applicable
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": "mytrendyes",
  "logo": "https:\/\/mytrendyes.com\/cdn\/shop\/files\/5.png?v=1751339639\u0026width=500",
  "sameAs": [
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    ""
  ],
  "url": "https:\/\/mytrendyes.com"
}
Block 2 : WebSite
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "mytrendyes",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/mytrendyes.com\/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "url": "https:\/\/mytrendyes.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