swissvax.de website review

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Shopify and others), adding 2.5 MB and 2.1 s of main-thread time.

hcaptcha.com costs a phone 974 ms of main-thread work and 1.2 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.

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

About 820 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

Facebook costs a phone 269 ms of main-thread work and 249 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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

About 19 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 JavaScript.

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.

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

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

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

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

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

Your homepage downloads 31.8 MB in 355 requests on a phone: media 26.5 MB (2), scripts 2.5 MB (77) and other files 1.4 MB (228). Under 2 MB keeps phones on slow connections fast.

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

2 dropdowns have no label.

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

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

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

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

Your title is 107 characters, so Google will cut it off around 60: “Swissvax – Premium Autopflege, Polituren & Autowachs seit 1930 – SWISSVAX Logistics UG (h…”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 188 pages on swissvax.de and 10 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://swissvax.de/collections/quick-detailing/oberflache_lack is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211058975&tm=gtm002&Ver=2&mid=a3a3ded2-f3fc-4257-8d8c-caba69d56807&bo=3&sid=cc699790df5b11f1900451e30b5565e4&vid=cc69c8a0df5b11f1b9ca2f10eafa4a46&vids=1&msclkid=N&pi=9.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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