vaha.com website review

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

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

The page goes through 1 redirect before it starts loading, costing about 1.1 s. Link and advertise the final URL directly.

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

7 third-party services load with your homepage (Google Tag Manager, cookiefirst.com and ipregistry.co and others), adding 7.0 MB and 388 ms of main-thread time.

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

Amazon Web Services costs a phone 0 ms of main-thread work and 6.5 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.

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

Google Tag Manager costs a phone 387 ms of main-thread work and 393 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.

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

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

13 KiB could be saved by minifying CSS.

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 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vaha - the interactive mirror provides access to fully pers…”.

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

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

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

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.

Your homepage downloads 8.9 MB in 32 requests on a phone: media 6.5 MB (2), scripts 2.1 MB (17) and fonts 193 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

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

There are 2 <h1> headlines (“MOTIVIERT UND EFFEKTIV TRAINIEREN” and “DEIN INTELLIGENTES GYM ZUHAUSE FÜR Cardio Ausdaue…”). One clear main headline is easier for people and search engines.

Structured data found ((untyped)) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

The homepage links to 26 pages on vaha.com 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.

Your homepage links to https://vaha.com/https//:your-checkout.vaha.com, which answers with an error. Visitors hit a dead end and search engines drop it.

https://vaha.com/pages/kontakt and https://vaha.com/pages/faq are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://vaha.com/products/vaha, https://vaha.com/pages/kontakt and https://vaha.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://vaha.com/pages/kontakt and https://vaha.com/pages/faq took over 3 s to send their HTML from our server.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

The homepage has only about 36 words of visible text; thin pages give Google and first-time buyers little to go on.

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 page uses urgency cues (a countdown or limited-time wording).

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