mag-tools.eu website review

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

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

8 third-party services load with your homepage (iubenda, Shopify and zipchat.ai and others), adding 346 KiB and 683 ms of main-thread time.

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

iubenda costs a phone 601 ms of main-thread work and 125 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.

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

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

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

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

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

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

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

20 KiB could be saved by minifying JavaScript.

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

5 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 180 requests on a phone: media 1.5 MB (3), images 1.1 MB (34) and other files 740 KiB (85). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (796 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example image_16_1.png at 1,500 px wide, shown at 217 px. Resized copies would save about 473 KiB.

2 images (114 KiB) are 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.

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

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

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

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.

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

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

Your title is only 21 characters: “Magswitch Deutschland”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 231 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, CollectionPage, ImageObject and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

The homepage links to 164 pages on mag-tools.eu and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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://www.magswitch.de/collections/schiffsbau, https://www.magswitch.de/collections/werkstattbedarf-alle-produkte, https://www.magswitch.de/collections/ergonomie, https://www.magswitch.de/collections/engineering-bin-picking, https://www.magswitch.de/collections/engineering-spanntechnik and https://www.magswitch.de/collections/engineering-handling and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.magswitch.de/collections/automation-elektrisch and https://www.magswitch.de/collections/automation-cobot use the same meta description. A description written for each page earns more clicks.

https://www.magswitch.de/collections/schweissen-fertigung, https://www.magswitch.de/collections/schiffsbau, https://www.magswitch.de/collections/holzverarbeitung, https://www.magswitch.de/collections/werkstattbedarf-alle-produkte, https://www.magswitch.de/collections/ergonomie and https://www.magswitch.de/collections/automation-pneumatisch and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.magswitch.de/collections/engineering-handling, https://www.magswitch.de/collections/engineering-vorrichtungsbau and https://www.magswitch.de/blogs/news took over 3 s to send their HTML from our server.

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

5 of 16 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: the server responded with a status of 404 ()”.

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: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 1,052 words of visible text.

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

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

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