ansmann.de website review

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

Your mobile performance score is 89 (desktop: 100). Pages that score under 90 lose visitors before the first paint.

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

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

website-files.com costs a phone 64 ms of main-thread work and 377 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.

4 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 744 KiB and 221 ms of main-thread time.

3 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

4 KiB could be saved by minifying JavaScript.

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

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 106 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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: 48 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.

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

The homepage links to 61 pages on ansmann.de and 23 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/karriere/karriere-bei-ansmann and /en/karriere/karriere-bei-ansmann all use the title “Karriere bei ANSMANN”. Search engines can't tell which page to show for a search, so each competes with the others.

/karriere/karriere-bei-ansmann and /en/karriere/karriere-bei-ansmann use the same meta description. A description written for each page earns more clicks.

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

Large scripts ship without source maps.

1 link to other sites is dead, for example https://shop.ansmann.de/powerstations (404).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://ansmann.de goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ansmann.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

DMARC is set to p=none, so mail pretending to be ansmann.de is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 2 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.