rhinoshield.de website review

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

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

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

8 third-party services load with your homepage (ZenDesk, Klaviyo and Shopify and others), adding 9.2 MB and 1.2 s of main-thread time.

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

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

ZenDesk costs a phone 543 ms of main-thread work and 355 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.

rhinoshield.app costs a phone 0 ms of main-thread work and 5.6 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.

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

Shopify costs a phone 163 ms of main-thread work and 3.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.

Klaviyo costs a phone 392 ms of main-thread work and 180 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.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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.

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

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

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bereit für iPhone 18 Pro”.

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

Your homepage downloads 10.6 MB in 289 requests on a phone: images 6.9 MB (75), other files 1.8 MB (66) and scripts 1.6 MB (134). Under 2 MB keeps phones on slow connections fast.

21 images are downloaded at several times the size a phone draws them, for example large_van_gogh_3da45bb2bc.png at 1,000 px wide, shown at 310 px. Resized copies would save about 2.3 MB.

large_van_gogh_3da45bb2bc.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

14 images (2.9 MB) 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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 69 pages on rhinoshield.de and 15 external pages.

There is no https://rhinoshield.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://rhinoshield.de/ditto/customize is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://rhinoshield.de/ditto/customize and https://rhinoshield.de/rhino-stories/product_design all use the title “RHINOSHIELD Deutschland | RHINOSHIELD Deutschland”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://rhinoshield.de/ditto/customize and https://rhinoshield.de/rhino-stories/product_design use the same meta description. A description written for each page earns more clicks.

https://rhinoshield.de/ditto/customize and https://rhinoshield.de/rhino-stories/product_design have no <h1> headline, so visitors and search engines get no clear main topic.

https://rhinoshield.de/ditto/customize and https://rhinoshield.de/featured/iphone-18 took over 3 s to send their HTML from our server.

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

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 trust badges. 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.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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 9 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.