r-m.de website review

12 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

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

About 586 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

3 third-party services load with your homepage (Google Tag Manager, cookiefirst.com and s-v.de), adding 250 KiB and 71 ms of main-thread time.

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

1 image could be 9 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.

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

Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies on this website so …”.

The layout shifts by 1.061 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

The first text or image appears after 4.8 s on a phone. Good is under 1.8 s.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 94 ms to 108 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 2.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

my2026_hlf_swing5_1600x874_web.jpg weighs 491 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.8 MB in 22 requests on a phone: scripts 1.7 MB (8), stylesheets 636 KiB (2) and images 331 KiB (2). Under 2 MB keeps phones on slow connections fast.

3 images (566 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 further down the page (594 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example my2026_hlf_swing5_1600x874_web.jpg at 1,680 px wide, shown at 390 px. Resized copies would save about 253 KiB.

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

3 buttons have no accessible name, so screen readers announce just “button”.

1 image has no alt text, which hurts accessibility and image search.

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

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.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

There are 2 <h1> headlines (“Not at the cutting edge of technology?” and “”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link has no real href, so search engines can't follow it.

The homepage links to 49 pages on r-m.de and 8 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.r-m.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://www.r-m.de/en-gb/bikes, https://www.r-m.de/en-gb/trekking, https://www.r-m.de/en-gb/city and https://www.r-m.de/en-gb/cargo all use the title “Bikes & accessories | Riese & Müller”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.r-m.de/en-gb/privacy-policy, https://www.r-m.de/en-gb/service/warranty, https://www.r-m.de/en-gb/e-bike-accessories and https://www.r-m.de/en-gb/newsletter have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.r-m.de/en-gb/bikes, https://www.r-m.de/en-gb/trekking, https://www.r-m.de/en-gb/city and https://www.r-m.de/en-gb/cargo use the same meta description. A description written for each page earns more clicks.

https://www.r-m.de/en-gb/bikes and https://www.r-m.de/en-gb/trekking took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.r-m.de/cms/static/assets/css/libs/normalize.min.css' from origin 'https://w…”.

Large scripts ship without source maps.

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.

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

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

The homepage carries about 345 words of visible text.

Before a visitor clicks anything, the page loads 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 1 cookie (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.