Website review, no card needed

gebeco.de logo

gebeco.de website review

Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 83 checks

This review found 31 issues worth fixing on gebeco.de, 13 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.1 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.7 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
191 ms176 msMay 2Oct 17180 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026189 ms
May 9, 2026187 ms
May 16, 2026185 ms
May 23, 2026183 ms
May 30, 2026181 ms
Jun 6, 2026183 ms
Jun 13, 2026179 ms
Jun 20, 2026178 ms
Jun 27, 2026178 ms
Jul 4, 2026178 ms
Jul 18, 2026184 ms
Jul 25, 2026182 ms
Aug 1, 2026180 ms
Aug 8, 2026179 ms
Aug 15, 2026179 ms
Aug 22, 2026183 ms
Aug 29, 2026180 ms
Sep 5, 2026180 ms
Sep 12, 2026181 ms
Sep 19, 2026182 ms
Sep 26, 2026186 ms
Oct 3, 2026186 ms
Oct 10, 2026185 ms
Oct 17, 2026180 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gebeco.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gebeco.de at 0.4 s0.4 s
  2. gebeco.de at 0.8 s0.8 s
  3. gebeco.de at 1.3 s1.3 s
  4. gebeco.de at 1.7 s1.7 s
  5. gebeco.de at 2.1 s2.1 s
  6. gebeco.de at 2.5 s2.5 s
  7. gebeco.de at 2.9 s2.9 s
  8. gebeco.de at 3.4 s3.4 s

Speed

6 to fix70
  • Improve image delivery

    3.8 s · 2.4 MB

    12 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

  • 3,053 HTML elements

    The page has 3,053 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    550 ms · 233 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (233 KiB).

  • Reduce unused JavaScript

    480 ms · 74 KiB

    About 74 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 37 KiB

    About 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cookiebot), adding 163 KiB and 58 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 95 but mobile only 70. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 542 ms of it running JavaScript. That is comfortably low.

  • Server response: 269 ms

    269 ms

    Your server sent the HTML in 269 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies, um Inhalte und Anzeigen zu personali…”.

  • Time to Interactive: 19.3 s

    19.3 s

    The page becomes fully interactive after 19.3 s. Good is under 3.8 s.

  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • 31 images without width and height

    31 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 189 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 197 ms

    197 ms

    Real visitors wait 197 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 578 ms

    578 ms

    Real visitors wait 578 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 37% faster for real visitors

    -37%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 90 ms

    90 ms

    Scripts block the page for only 90 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 16.7 MB in 86 requests

    16.7 MB

    Your homepage downloads 16.7 MB in 86 requests on a phone: media 11.9 MB (3), images 4.0 MB (20) and scripts 486 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Vietnam_Mekong_SchwimmenderMarkt_landscapeL-1.jpg weighs 671 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (918 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 4 images far larger than shown

    45 KiB

    4 images are downloaded at several times the size a phone draws them, for example suedafrika-vom-kruegerpark-bis-zur-gartenroute_01_landscape. at 600 px wide, shown at 192 px. Resized copies would save about 45 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (116 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.7 g of CO₂ per visit

    4.73 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.73 g of CO₂e: 567.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 8789
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 15 tap targets too small

    15 tap targets are too small or too close together to hit reliably with a finger.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • All page content should be contained by landmarks (20 elements)

    All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 27 links without text

    27 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Gebeco - Reisen, die begeistern | Erlebnisreisen, Studienreisen und Aktivreisen”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 266 internal links, 8 external

    The homepage links to 266 pages on gebeco.de and 8 external pages.

6 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Entdecken Sie die vielfältige Gebeco Reisewelt: Fremde Kulturen erkunden und Menschen begegnen, durch Gruppenreisen mit…”.

  • One H1 headline

    Your main headline reads: “Fernweh bringt Sie weiter!”.

  • Canonical URL set

    The canonical URL is https://www.gebeco.de/.

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gebeco.de/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.gebeco.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,384 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://www.gebeco.de/reisen/suche is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.gebeco.de/mein-gebeco/merklisten and https://www.gebeco.de/mein-gebeco/konfigurationen all use the title “Gebeco”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.gebeco.de/mein-gebeco/merklisten and https://www.gebeco.de/mein-gebeco/konfigurationen have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.gebeco.de/mein-gebeco/merklisten, https://www.gebeco.de/mein-gebeco/konfigurationen, https://www.gebeco.de/reisen/suche and https://www.gebeco.de/reisearten/kleingruppe have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    64 of 67 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,167 words of copy

    The homepage carries about 1,167 words of visible text.

4 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gebeco.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Angular
Analytics
Google Tag Manager

Company

Founded
1978
Headquarters
Kiel

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on gebeco.de, including 10 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25