maxxus.com website review

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

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

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

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

8 third-party services load with your homepage (rebuyengine.com, Clarity and Klaviyo and others), adding 1.4 MB and 611 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 196 ms of main-thread work and 334 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.

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

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

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

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

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

About 46 KiB of CSS is downloaded but never applied on this page.

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website verwendet Cookies, um dir das beste Erlebnis …”.

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

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

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

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

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-11-07, real Chrome visitors' tap response (inp) went from 132 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.9 MB in 341 requests on a phone: media 3.2 MB (1), scripts 1.4 MB (112) and images 1,023 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

ARIA dialog and alertdialog nodes should have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 4 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.

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

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

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

Your <h1> is empty.

The homepage links to 84 pages on maxxus.com and 5 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

/policies/shipping-policy, /policies/refund-policy and /policies/contact-information use the same meta description. A description written for each page earns more clicks.

/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=26063673&tm=gtm002&Ver=2&mid=1bfd9541-152c-4e07-b4c1-1ce2a26c1c01&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=MAXXUS%20%7C%20Fitnessger%C3%A4te%20f%C3%BCr%.

19 of 73 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.maxxus.com/cdn/shop/t/21/assets/component-predictive-search.css?v=10527' becau…”.

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.

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

The page uses urgency cues (a countdown or limited-time wording).

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