ruf.eu website review

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

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

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

41 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

8 third-party services load with your homepage (Cookiebot, Shopify and sibforms.com and others), adding 1.6 MB and 660 ms of main-thread time.

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

Cookiebot costs a phone 411 ms of main-thread work and 42 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

Shopify costs a phone 108 ms of main-thread work and 1.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

14 KiB JavaScript is shipped twice across bundles.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 299 requests on a phone: images 2.3 MB (48), scripts 1.2 MB (83) and other files 856 KiB (120). Under 2 MB keeps phones on slow connections fast.

Muesli_neu_Slider_Mobil_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example apple-cinnamon-rolls-bb1.jpg at 1,600 px wide, shown at 212 px. Resized copies would save about 401 KiB.

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

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

[role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

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

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your <h1> is empty.

The homepage links to 298 pages on ruf.eu and 16 external pages.

https://www.ruf.eu/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.ruf.eu/collections/bestseller and https://www.ruf.eu/a/magazin have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 138 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.

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

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 990 words of visible text.

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

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