amf.de website review

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

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

About 2.7 MB of JavaScript is downloaded but never used on this page.

1.3 MB could be saved by minifying JavaScript.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.4 MB and 840 ms of main-thread time.

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

YouTube costs a phone 630 ms of main-thread work and 1.9 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 208 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.

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

Google Tag Manager costs a phone 185 ms of main-thread work and 317 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 1,751 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

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

2 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' largest content (lcp) went from 2.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 94 requests on a phone: scripts 2.8 MB (37), other files 660 KiB (19) and images 333 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 84 characters, so Google will cut it off around 60: “AMF Spanntechnik & Nullpunktspannsysteme – AMF Online-Shop & Automatisierungstechnik”.

There are 2 <h1> headlines (“” and “EFFIZIENT MIT PRODUKTEN VON AMF”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 238 pages on amf.de and 9 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.

/de/spanntechnik, /de/spanntechnik/schnellspanner and /de/spanntechnik/schnellspanner/senkrechtspanner took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'data:image/svg+xml,%3csvg%20xmlns='http://www.w3.org/2000/svg'%20width='16'%20height='16'%20fill='curren…”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

DMARC is set to p=none, so mail pretending to be amf.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 Ads, 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 18 cookies, 1 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.