optotech.net website review

About 735 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

14 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

5 third-party services load with your homepage (Hubspot, Google Tag Manager and Usercentrics CMP and others), adding 2.3 MB and 233 ms of main-thread time.

About 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 380 ms faster on a phone.

reaze.cloud costs a phone 1 ms of main-thread work and 1.6 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.

Hubspot costs a phone 122 ms of main-thread work and 394 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.

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

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

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

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

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.

Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OptoTech ist Teil der Schunk Group und gilt im Kreis der Op…”.

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 72 requests on a phone: images 1.6 MB (25), scripts 1.3 MB (16) and stylesheets 56 KiB (1). Under 2 MB keeps phones on slow connections fast.

3 images (792 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 0.87 g of CO₂e: 103.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “Home | OptoTech”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

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

The homepage links to 98 pages on optotech.net and 26 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.optotech.net/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.

https://www.optotech.net/de, https://www.optotech.net/en and https://www.optotech.net/es all use the title “Home | OptoTech”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.optotech.net/en, https://www.optotech.net/es, https://www.optotech.net/de/produkte, https://www.optotech.net/de/produkte/feinoptik, https://www.optotech.net/de/produkte/brillenoptik and https://www.optotech.net/de/produkte/messtechnik and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.optotech.net/de/anwendungsbereiche/brillenglaeser-kunststoff took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

Large scripts ship without source maps.

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.

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

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

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