Skip to content
https://informezonal.com.ar

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
2
PASS
3
INFO
0
Checks
9
3 PASS 2 REVIEW 4 FIX
F
Open Graph
Action
No Open Graph tags found — social sharing previews will be generic.
FIX
No Open Graph tags found — social sharing previews will be generic.
Warning::
No Open Graph meta tags found
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Why this matters

Without Open Graph tags, social shares show a broken or empty preview card.

Learn more ▾

When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.

Source: Open Graph Protocol

Preview

No image set

informezonal.com.ar

No title set

No description

Preview quality · Twitter/X F · 10/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from <title>
  • twitter:description — Add twitter:description to give the preview body text
  • twitter:image — Add twitter:image — preview card without an image looks broken

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

  • No preview image for Twitter/X

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

No image set

INFORMEZONAL.COM.AR

No title set

No description

Preview quality · Facebook F · 0/100
  • og:title — falling back from <title>
  • 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 — Add og:type — Recommended — tells Facebook the content category
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

No title set

informezonal.com.ar

Preview quality · LinkedIn F · 45/100
  • og:title — falling back from <title>
  • 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)

informezonal.com.ar

No title set

No description

Preview quality · Slack D · 60/100
  • og:title — falling back from <title>
  • 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.

F · 28/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description———
twitter:image———
F
Structured Data
Action
7 JSON-LD block(s) found — issues found that may affect search visibility.
FIX
7 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: http://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #2
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://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: http://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #4
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #5
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #6
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Warning::
Missing or invalid @context in block #7
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Custom type "organization" — unable to validate specific properties
Info::
5 blocks of custom type "WPSideBar" — unable to validate specific properties
Info::
7 JSON-LD blocks found
URL: http://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: http://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: http://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: http://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: http://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: http://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: http://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

JSON-LD Blocks

Block 1 : organization
7 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "organization",
  "@id": "#organization",
  "logo": {
    "@type": "ImageObject",
    "url": "https:\/\/informezonal.com.ar\/wp-content\/uploads\/2025\/06\/cropped-logo_grande.png"
  },
  "url": "https:\/\/informezonal.com.ar\/",
  "name": "INFORME ZONAL",
  "description": ""
}
Block 2 : WebSite
6 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WebSite",
  "name": "INFORME ZONAL",
  "alternateName": "",
  "url": "https:\/\/informezonal.com.ar\/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https:\/\/informezonal.com.ar\/search\/{search_term}",
    "query-input": "required name=search_term"
  }
}
Block 3 : WPSideBar
5 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WPSideBar",
  "name": "Sidebar Right",
  "alternateName": "Add widgets here to display them on blog and single",
  "url": "https:\/\/informezonal.com.ar"
}
Block 4 : WPSideBar
5 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WPSideBar",
  "name": "Sidebar Left",
  "alternateName": "Add widgets here to display them on page",
  "url": "https:\/\/informezonal.com.ar"
}
Block 5 : WPSideBar
5 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WPSideBar",
  "name": "Footer Column #1",
  "alternateName": "Add widgets here to display them in the first column of the footer",
  "url": "https:\/\/informezonal.com.ar"
}
Block 6 : WPSideBar
5 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WPSideBar",
  "name": "Footer Column #2",
  "alternateName": "Add widgets here to display them in the second column of the footer",
  "url": "https:\/\/informezonal.com.ar"
}
Block 7 : WPSideBar
5 properties Valid
Missing or invalid @context
{
  "@context": "http:\/\/schema.org\/",
  "@type": "WPSideBar",
  "name": "Footer Column #3",
  "alternateName": "Add widgets here to display them in the third column of the footer",
  "url": "https:\/\/informezonal.com.ar"
}
F
Image Optimization
Action
5 issues found across 8 images
FIX
5 issues found across 8 images
Warning::
2 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
5 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 8 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 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://informezonal.com.ar/wp-content/uploads/2025/06/cropped-logo_grande.png.
Info::
1 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://informezonal.com.ar/wp-content/uploads/2025/06/WhatsApp-Video-2025-03-27-at-11.17.24-AM.gif.
F
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.

F

14/100

Site name appears as

Page titleINFORME ZONAL
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

0/15

Social share image

0/20

Meta completeness

4/20

Organization schema

0/15

Contact info discoverable

5/10

mailto link

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • No social share image — shared links render as bare URLs
  • No favicon link tags detected — browsers fall back to the generic globe
  • og:title missing
  • og:image missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • 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
Mixed Content
1 HTTP resource(s) loaded on HTTPS page
REVIEW
1 HTTP resource(s) loaded on HTTPS page
Critical::
HTTP link loaded on HTTPS page
Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
Got: http://gmpg.org/xfn/11 Expected: https://gmpg.org/xfn/11
URL: http://gmpg.org/xfn/11

Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

Expected: https://gmpg.org/xfn/11
Why this matters

Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.

Source: Google Chrome Security

A+
Open Graph / Twitter Card Depth
No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)
PASS
No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)
Info::
No OG image / Twitter card to evaluate
A+
Rich Results Eligibility
7 JSON-LD block(s) declaring 3 schema type(s)
PASS
7 JSON-LD block(s) declaring 3 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::
3 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): WPSideBar (×5), WebSite, organization 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