Skip to content
https://www.javalf.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
1
PASS
5
INFO
0
Checks
9
5 PASS 1 REVIEW 3 FIX
F
Structured Data
Action
3 JSON-LD block(s) found — issues found that may affect search visibility.
FIX
3 JSON-LD block(s) found — issues found that may affect search visibility.
Warning::
Missing or invalid @context in block #1
The @context should be "https://schema.org" for search engines to recognize the data.
Got: https://schema.org/ Expected: https://schema.org
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Warning::
Missing or invalid @context in block #2
The @context should be "https://schema.org" for search engines to recognize the data.
Got: https://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #3
The @context should be "https://schema.org" for search engines to recognize the data.
Got: https://schema.org/ Expected: https://schema.org
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Missing recommended property "telephone" for LocalBusiness
Adding "telephone" can improve how search engines display your content.
Info::
Missing recommended property "openingHours" for LocalBusiness
Adding "openingHours" can improve how search engines display your content.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Missing recommended property "potentialAction" for WebSite
Adding "potentialAction" can improve how search engines display your content.
Info::
3 JSON-LD blocks found
URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

The "name" property is required for the WebSite 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

URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

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

Adding "telephone" 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 "openingHours" 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 "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

Adding "potentialAction" 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 : WebSite
4 properties Valid
Missing or invalid @context
Missing required property: name
{
  "@context": "https://schema.org/",
  "@type": "WebSite",
  "url": "https://www.javalf.com/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://www.javalf.com/search?q={search_term}"
    },
    "query-input": "required name=search_term"
  }
}
Block 2 : LocalBusiness
5 properties Valid
Missing or invalid @context
{
  "@context": "https://schema.org/",
  "@type": "LocalBusiness",
  "name": "javalf",
  "url": "https://www.javalf.com",
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "EC"
  }
}
Block 3 : WebSite
4 properties Valid
Missing or invalid @context
{
  "@context": "https://schema.org/",
  "@type": "WebSite",
  "name": "Javalf",
  "url": "https://www.javalf.com"
}
F
Image Optimization
Action
7 issues found across 42 images
FIX
7 issues found across 42 images
Warning::
3 images significantly larger than display size
Resizing to display dimensions could save approximately 204 KB.
Got: ~204 KB wasted
Warning::
38 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
28 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 42 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::
Total image weight: 3162 KB (3.1 MB)
Consider compressing images, using modern formats, and serving appropriately sized images.
Info::
3 image(s) wider than 400px without srcset (no responsive serving)
These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://static.wixstatic.com/media/11062b_017f998d03a44d5494c1f4eb4a9fcace~mv2.jpg/v1/fill/w_466,h_520,al_c,q_80,usm_0.66_1.00_0.01,enc_avif,quality_auto/11062b_017f998d03a44d5494c1f4eb4a9fcace~mv2.jpg, https://static.wixstatic.com/media/11062b_de46667dfdba445994e2b216a91629aff000.jpg/v1/fill/w_469,h_520,al_c,q_80,usm_0.33_1.00_0.00,enc_avif,quality_auto/11062b_de46667dfdba445994e2b216a91629aff000.jpg, https://static.wixstatic.com/media/e0821a_143f3ef53f934f21bea72146ea9363c1~mv2.png/v1/fill/w_56,h_42,al_c,q_85,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/e0821a_143f3ef53f934f21bea72146ea9363c1~mv2.png.
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://static.wixstatic.com/media/c9aa5c_13e7dedf7e8b47829063650180c8b0c1~mv2.png/v1/fit/w_1672,h_668,q_90,enc_avif,quality_auto/c9aa5c_13e7dedf7e8b47829063650180c8b0c1~mv2.png, https://static.wixstatic.com/media/c9aa5c_034399506955489ba332f6102c2c60b5~mv2.png/v1/fit/w_1672,h_668,q_90,enc_avif,quality_auto/c9aa5c_034399506955489ba332f6102c2c60b5~mv2.png, https://static.wixstatic.com/media/0b1aab_4c6d63d3355c459684ff3259ad59fe90~mv2.jpg/v1/fill/w_62,h_118,al_c,q_80,usm_0.66_1.00_0.01,blur_2,enc_avif,quality_auto/0b1aab_4c6d63d3355c459684ff3259ad59fe90~mv2.jpg (+7 more).
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

D

48/100

Site name appears as

Page titleJavalf
og:site_nameJavalf
twitter:site
Organization.namejavalf

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

0/20

Meta completeness

8/20

Organization schema

8/15

has name + url

Contact info discoverable

5/10

contact page

Findings

  • Missing brand name in: twitter:site
  • No social share image — shared links render as bare URLs
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:image missing
  • Organization schema missing logo — add a logo property pointing to a square PNG
  • 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.

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

The og:description tag controls the description in social sharing previews.

Why this matters

No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.

Learn more

Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.

Source: Open Graph Protocol

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

No image set

www.javalf.com

INICIO | Javalf

No description

Preview quality · Twitter/X D · 50/100
  • twitter:card — summary_large_image
  • twitter:title — INICIO | Javalf
  • twitter:description — Add twitter:description to give the preview body text
  • 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

WWW.JAVALF.COM

INICIO | Javalf

No description

Preview quality · Facebook D · 50/100
  • og:title — INICIO | Javalf
  • og:description — Add og:description to give the preview body text
  • og:image — Add og:image — preview card without an image looks broken
  • og:type — website
  • og:url — https://www.javalf.com
  • og:site_name — Javalf
  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

INICIO | Javalf

www.javalf.com

Preview quality · LinkedIn D · 50/100
  • og:title — INICIO | Javalf
  • og:description — Add og:description to give the preview body text
  • og:image — Add og:image — preview card without an image looks broken
  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

www.javalf.com

INICIO | Javalf

No description

Preview quality · Slack C · 65/100
  • og:title — INICIO | Javalf
  • og:description — Add og:description to give the preview body text
  • 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.

D · 53/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
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 / 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+
Rich Results Eligibility
3 JSON-LD block(s) declaring 2 schema type(s)
PASS
3 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): WebSite (×2), LocalBusiness 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