vapechamp.de website review

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

17 images could be 733 KiB 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.

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

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

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

3 third-party services load with your homepage (Shopify, Snapchat and Judge.me), adding 1.5 MB and 69 ms of main-thread time.

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

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

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 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Weeks bei Vapechamp: Blitz-Deals mit Countdown”.

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

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

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

Your homepage downloads 3.7 MB in 290 requests on a phone: images 2.0 MB (52), other files 849 KiB (66) and scripts 487 KiB (137). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example Produktbild_OWLA_Doppelpacks_SourBlue_20mg.png at 600 px wide, shown at 113 px. Resized copies would save about 322 KiB.

1 image (80 KiB) is 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 (80 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 1.04 g of CO₂e: 124.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 elements use ARIA attributes their role does not allow, which confuses screen readers.

8 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

<td> elements in a large <table> do not have table headers. (1 element).

The homepage links to 494 pages on vapechamp.de and 0 external pages.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 3,680 words of visible text.

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