Skip to content
https://loopjc.myshopify.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Checks
9
6 PASS 3 REVIEW
C
Image Optimization
Action
3 issues found across 8 images
REVIEW
3 issues found across 8 images
Info::
7 of 8 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://loopjc.myshopify.com/cdn/shop/files/IMG_6816.jpg?v=1718396192&width=550.
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://loopjc.myshopify.com/cdn/shop/files/Screenshot2025-03-18135400.png?v=1742320456&width=360, https://loopjc.myshopify.com/cdn/shop/files/Screenshot2026-02-27at8.01.12PM.png?v=1772240501&width=360.
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

59/100

Site name appears as

Page titleVisa
og:site_nameThe Loop
twitter:site—
Organization.nameThe Loop

Inconsistent — names differ across channels

Brand assets

Favicon

0/15

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
  • No favicon link tags detected — browsers fall back to the generic globe
  • 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://loopjc.myshopify.com/cdn/shop/files/theloopweb.png?height=628&pad_color=ffffff&v=1718393744&width=1200
Info::
og:title is short (8 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 8 chars Expected: 25–60 chars
Info::
og:description is short (8 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 8 chars Expected: 55–200 chars
URL: http://loopjc.myshopify.com/cdn/shop/files/theloopweb.png?height=628&pad_color=ffffff&v=1718393744&width=1200

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

loopjc.myshopify.com

The Loop

The Loop

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

LOOPJC.MYSHOPIFY.COM

The Loop

The Loop

Preview quality · Facebook A+ · 100/100
  • og:title — The Loop
  • og:description — The Loop
  • og:image — http://loopjc.myshopify.com/cdn/shop/files/theloopweb.png?height=628&pad_color=ffffff&v=1718393744&width=1200
  • og:type — website
  • og:url — https://loopjc.myshopify.com/
  • og:site_name — The Loop

  • og:image is below recommended size (1200×628)

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

The Loop

loopjc.myshopify.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — The Loop
  • og:description — The Loop
  • og:image — http://loopjc.myshopify.com/cdn/shop/files/theloopweb.png?height=628&pad_color=ffffff&v=1718393744&width=1200

loopjc.myshopify.com

The Loop

The Loop

Preview quality · Slack A+ · 100/100
  • og:title — The Loop
  • og:description — The Loop
  • og:image — http://loopjc.myshopify.com/cdn/shop/files/theloopweb.png?height=628&pad_color=ffffff&v=1718393744&width=1200

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+
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": "The Loop",
  "logo": "https:\/\/loopjc.myshopify.com\/cdn\/shop\/files\/theloopweb.png?v=1718393744\u0026width=500",
  "sameAs": [
    "",
    "",
    "",
    "https:\/\/www.instagram.com\/theloopjc?igsh=bmh1Y2tzYm9najl0",
    "https:\/\/www.tiktok.com\/@theloopjc?_t=8nqOSZsxg9W\u0026_r=1",
    "",
    "",
    "",
    ""
  ],
  "url": "https:\/\/loopjc.myshopify.com"
}
Block 2 : WebSite
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "name": "The Loop",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/loopjc.myshopify.com\/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  },
  "url": "https:\/\/loopjc.myshopify.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