Skip to content
https://racing-hub.pages.dev

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Checks
9
5 PASS 3 REVIEW 1 FIX
F
Image Optimization
Action
5 issues found across 37 images
FIX
5 issues found across 37 images
Warning::
1 images significantly larger than display size
Resizing to display dimensions could save approximately 1135 KB.
Got: ~1135 KB wasted
Warning::
34 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
2 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
Total image weight: 1137 KB (1.1 MB)
Consider compressing images, using modern formats, and serving appropriately sized images.
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: data:, data:.
B
Structured Data
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 JSON-LD block(s) found — some improvements recommended.
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Warning::
Missing required property "url" for WebSite
The "url" property is required for the WebSite schema type.
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.

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

The "url" 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

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
2 properties Valid
Missing required property: name
Missing required property: url
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebSite",
      "@id": "https://racing-hub.pages.dev/#website",
      "url": "https://racing-hub.pages.dev/",
      "name": "Racing Hub",
      "description": "Plateforme indépendante et non officielle des supporters du RC Strasbourg Alsace",
      "inLanguage": "fr-FR"
    },
    {
      "@type": "SportsTeam",
      "@id": "https://racing-hub.pages.dev/#team",
      "name": "Racing Club de Strasbourg Alsace",
      "sport": "Football",
      "url": "https://racing-hub.pages.dev/",
      "logo": "https://racing-hub.pages.dev/logo.webp"
    }
  ]
}
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

57/100

Site name appears as

Page titleActus, Stats et Communauté du RC Strasbourg Alsace
og:site_nameRacing Hub
twitter:site—
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • No Organization schema — Google can't render your logo in the knowledge panel
  • No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions

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.
Info::
og:title is long (63 characters)
Titles over 60 characters may be truncated in social sharing previews.
Got: 63 chars Expected: 25–60 chars
URL: 63 chars

Titles over 60 characters may be truncated in social sharing previews.

Expected: 25–60 chars
Why this matters

og:title borderline-too-long — Facebook/LinkedIn may truncate. Aim for ~60-70 characters max.

Source: Open Graph Protocol

Preview

racing-hub.pages.dev

Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace

Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Club de Strasbourg Alsace.

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary
  • twitter:title — Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace
  • twitter:description — Actualités en direct, résultats, effectif, statistiques, quiz et pronostics du RCSA.
  • twitter:image — https://racing-hub.pages.dev/logo.webp

RACING-HUB.PAGES.DEV

Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace

Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Club de Strasbourg Alsace.

Preview quality · Facebook A+ · 95/100

Title will be truncated (66 chars / 60 max)

  • og:title — Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace
  • og:description — Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Clu...
  • og:image — https://racing-hub.pages.dev/logo.webp
  • og:type — website
  • og:url — https://racing-hub.pages.dev/
  • og:site_name — Racing Hub

  • Title will be truncated on Facebook (66 chars, max 60)

    → Shorten og:title to ≤60 characters

Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace

racing-hub.pages.dev

Preview quality · LinkedIn A+ · 100/100
  • og:title — Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace
  • og:description — Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Clu...
  • og:image — https://racing-hub.pages.dev/logo.webp

racing-hub.pages.dev

Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace

Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Club de Strasbourg Alsace.

Preview quality · Slack A+ · 100/100
  • og:title — Racing Hub – Actus, Stats et Communauté du RC Strasbourg Alsace
  • og:description — Actualités en direct, résultats de Ligue 1, effectif, statistiques, quiz et pronostics des supporters du Racing Clu...
  • og:image — https://racing-hub.pages.dev/logo.webp

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
1 OG/Twitter depth issue(s) detected
PASS
1 OG/Twitter depth issue(s) detected
Info::
1 Twitter Card field(s) differ from Open Graph counterparts
Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches: - description: twitter="Actualités en direct, résultats, effec...", og="Actualités en direct, résultats de Lig..." Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.
Got: 1 field(s) differ
A+
Rich Results Eligibility
1 JSON-LD block(s) declaring 2 schema type(s)
PASS
1 JSON-LD block(s) declaring 2 schema type(s)
Info::
2 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): SportsTeam, 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