retailex.de website review

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

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

About 221 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

5 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).

About 76 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.

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 195 KiB and 147 ms of main-thread time.

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

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

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hosting-Services und BPO im Kreis Ahrweiler und DE”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 images (295 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.

5 images further down the page (217 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

3 links inside paragraphs rely on colour alone to stand out.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Mit - Sicherheit - Günstiger” and “Aktuelle Referenzen”). One clear main headline is easier for people and search engines.

The homepage links to 25 pages on retailex.de and 5 external pages.

There is no https://retailex.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.

https://retailex.de/kontakt and https://retailex.de/Kontakt all use the title “Kontakt - Retailex - Hosting-Services und BPO”. Search engines can't tell which page to show for a search, so each competes with the others.

https://retailex.de/kontakt and https://retailex.de/Kontakt use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://retailex.de/Funnel-Start, whose canonical is https://retailex.de/funnel-start. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

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

Chrome logged issues while loading the page (“Mixed content”).

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 20 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 1,414 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 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.