thealphamen.de website review

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

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

8 third-party services load with your homepage (thealphamen.nl, Shopify and Klaviyo and others), adding 1.6 MB and 1.0 s of main-thread time.

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

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

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

thealphamen.nl costs a phone 396 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.

Shopify costs a phone 264 ms of main-thread work and 469 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 209 ms of main-thread work and 507 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 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.

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

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

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

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

16 KiB could be saved by minifying JavaScript.

8 KiB JavaScript is shipped twice across bundles.

6 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

Scripts block taps and scrolling for 346 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 128 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 333 requests on a phone: scripts 1.6 MB (118), other files 979 KiB (143) and images 437 KiB (27). Under 2 MB keeps phones on slow connections fast.

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

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

16 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

8 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h3 → h6, h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (7 elements).

There are 2 <h1> headlines (“Selbstbewusst aus dem Haus. Jeden Tag.” and “Selbstbewusst aus dem Haus. Jeden Tag.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://thealphamen.nl)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 1,192 pages on thealphamen.de and 8 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thealphamen.de/pages/wishlist, whose canonical is https://thealphamen.de/pages/wunschliste. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thealphamen.de/pages/zu-bemerken, https://thealphamen.de/collections/haar, https://thealphamen.de/collections/bart, https://thealphamen.de/collections/gesicht, https://thealphamen.de/collections/korper and https://thealphamen.de/collections/rasur and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://thealphamen.de/collections/haar took over 3 s to send its HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://thealphamen.nl/cart.json' from origin 'https://thealphamen.de' has been blocked by CORS pol…”.

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.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Pinterest Tag and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 19 cookies (measured from a US location before any click).

Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.