meinschiff.com website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

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

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

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

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

A phone's processor spends 2.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

3 third-party services load with your homepage (Dynamic Yield, baqend.com and Amazon Web Services), adding 286 KiB and 168 ms of main-thread time.

Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

2 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies und ähnliche Technologien, um unsere …”.

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

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

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

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

Scripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 2.0 MB in 123 requests on a phone: scripts 1.1 MB (82), images 488 KiB (18) and fonts 328 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Neue Reisen mit der Mein Schiff Flow” and “Mein Schiff ® Kreuzfahrten”). One clear main headline is easier for people and search engines.

The homepage links to 102 pages on meinschiff.com and 38 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.meinschiff.com/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.

https://www.meinschiff.com/de/mein-schiff-gefuehl is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.meinschiff.com/kreuzfahrt-buchen and https://www.meinschiff.com/an-bord all use the title “Cruises: Experience unforgettable moments | Mein Schiff ®”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.meinschiff.com/kreuzfahrt-buchen and https://www.meinschiff.com/an-bord use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.meinschiff.com/kreuzfahrt-buchen, whose canonical is https://www.meinschiff.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.meinschiff.com/de/kontakt has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.meinschiff.com/de/kontakt, https://www.meinschiff.com/de/inklusivleistungen, https://www.meinschiff.com/de/kreuzfahrten-angebote, https://www.meinschiff.com/kreuzfahrt-buchen, https://www.meinschiff.com/de/exklusivleistungen and https://www.meinschiff.com/de/flotte and 2 others took over 3 s to send their HTML from our server.

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

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 600 words of visible text.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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