omtechlaser.de website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.

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

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Hotjar and others), adding 2.3 MB and 1.8 s of main-thread time.

28 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

consentmanager.net costs a phone 421 ms of main-thread work and 127 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.

shulex-voc.com costs a phone 230 ms of main-thread work and 466 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,807 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

xcottons.com costs a phone 93 ms of main-thread work and 345 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.

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

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

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

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

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 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 6.1 MB in 301 requests on a phone: scripts 2.8 MB (90), images 2.1 MB (75) and other files 828 KiB (105). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 768-1024_81f93224-a468-40a6-a1c3-71052169f1d1.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 351 KiB.

5 images (373 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.

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

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

ARIA commands must have an accessible name: 39 elements on the page fail this check, rated serious by axe-core.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

5 links have no real href, so search engines can't follow them.

The homepage links to 111 pages on omtechlaser.de and 34 external pages.

https://de.omtech.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://de.omtech.com/collections/samtliche-lasermaschinen, https://de.omtech.com/collections/laser-graviermaschinen-cutter-mit-rabatten, https://de.omtech.com/collections/industrie-laser, https://de.omtech.com/collections/turbo-serie, https://de.omtech.com/collections/dedesktop-laser-cutter-und-graviermaschinen-fuer-zuhause and https://de.omtech.com/collections/faserlaser-serie and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=355014546&Ver=2&mid=4c7ddcc4-9926-4285-af61-25979cf149c7&bo=1&sid=51dac120dd0c11f18af46527261fca93&vid=51dae660dd0c11f1997adfdb331acfd5&vids=1&msclkid=N&pi=918639831&l.

10 of 24 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 “Replace_with_Variable_Revenue_Function is not defined”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 30 cookies, 1 of them by other companies (measured from a US location before any click).

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