Skip to content
https://www.der-betze-brennt.de

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
73
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Checks
9
3 PASS 4 REVIEW 2 FIX
F
Image Optimization
Action
9 issues found across 74 images
FIX
9 issues found across 74 images
Warning::
17 images significantly larger than display size
Resizing to display dimensions could save approximately 750 KB.
Got: ~750 KB wasted
Warning::
22 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
39 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
46 of 74 images use legacy formats
Warning::
29 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
Warning::
Total image weight: 1366 KB (1.3 MB)
Consider compressing images, using modern formats, and serving appropriately sized images.
Warning::
2 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://cdn.consentmanager.net/delivery/flags/en.gif, https://www.der-betze-brennt.de/images/news/thumbnails/2026-05-10-spielszene-scp-svd.jpg.
Info::
10 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://cdn.target-video.com/shared/20446/live/partners/27899/snapshot/2088401_sd_67f7deb9da4c3_1744297657.jpg, https://www.der-betze-brennt.de/images/news/2026-05-09-betze-comic-233-ehre-wem-ehre-gebuehrt.jpg, https://www.der-betze-brennt.de/images/artikel/3961/foto.jpg (+7 more).
Info::
6 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://www.der-betze-brennt.de/images/system/footer/icon-social-media-facebook.png, https://www.der-betze-brennt.de/images/system/footer/icon-social-media-instagram.png, https://www.der-betze-brennt.de/images/system/footer/icon-social-media-bluesky.png (+3 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

53/100

Site name appears as

Page titleDer Betze brennt
og:site_nameDer Betze brennt
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: twitter:site, Organization.name
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • twitter:card missing
  • 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.

B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://www.der-betze-brennt.de/images/news/1000-logo-der-betze-brennt.jpg
Info::
og:title is long (78 characters)
Titles over 60 characters may be truncated in social sharing previews.
Got: 78 chars Expected: 25–60 chars
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
URL: https://www.der-betze-brennt.de/images/news/1000-logo-der-betze-brennt.jpg

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

The og:type tag helps social platforms categorize the content.

Why this matters

Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.

Learn more ▾

og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

www.der-betze-brennt.de

1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen

Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das größte FCK-Forum im World Wide Web.

Preview quality · Twitter/X F · 45/100

Title will be truncated (78 chars / 70 max)

  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — falling back from og:image

  • twitter:card is missing

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

  • Title will be truncated on Twitter/X (78 chars, max 70)

    → Shorten the title to ≤70 characters

WWW.DER-BETZE-BRENNT.DE

1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen

Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das größte FCK-Forum im World Wide Web.

Preview quality · Facebook B · 80/100

Title will be truncated (78 chars / 60 max)

  • og:title — 1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen
  • og:description — Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das grö...
  • og:image — https://www.der-betze-brennt.de/images/news/1000-logo-der-betze-brennt.jpg
  • og:type — Add og:type — Recommended — tells Facebook the content category
  • og:url — https://www.der-betze-brennt.de
  • og:site_name — Der Betze brennt

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

    → Shorten og:title to ≤60 characters

1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen

www.der-betze-brennt.de

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (152 chars / 150 max)

  • og:title — 1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen
  • og:description — Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das grö...
  • og:image — https://www.der-betze-brennt.de/images/news/1000-logo-der-betze-brennt.jpg

  • Description will be truncated on LinkedIn (152 chars, max 150)

    → Tighten og:description to ≤150 characters

www.der-betze-brennt.de

1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen

Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das größte FCK-Forum im World Wide Web.

Preview quality · Slack A+ · 100/100
  • og:title — 1. FC Kaiserslautern - Das Online-Magazin: News, Analysen, Fotos, Diskussionen
  • og:description — Täglich alle Infos rund um den 1. FC Kaiserslautern: Aktuelle Berichte, News, Fotos, umfangreiches Archiv und das grö...
  • og:image — https://www.der-betze-brennt.de/images/news/1000-logo-der-betze-brennt.jpg

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

B · 80/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
C
Rich Results Eligibility
Action
No JSON-LD found -- no rich-result eligibility
REVIEW
No JSON-LD found -- no rich-result eligibility
Info::
No JSON-LD structured data on the page
No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.
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+
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