simtek.com website review

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

About 100 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

4 third-party services load with your homepage (piwik.pro, Unpkg and JSDelivr CDN and others), adding 274 KiB and 71 ms of main-thread time.

1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

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

Desktop scores 92 but mobile only 51. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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.31 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

1 image 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 94 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Website-Header-graphic-toolfinder3_2~-~media--5abec06c--quer is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 image further down the page (436 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

4 buttons have no accessible name, so screen readers announce just “button”.

6 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 element hidden from screen readers can still receive keyboard focus.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 16 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.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

The page declares lang=“de_DE”, which is not a usable language code, so screen readers and translation tools guess.

There are 2 <h1> headlines (“Intelligente Spanbrecher von SIMTEK” and “SIMTEK Toolfinder”). 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 174 pages on simtek.com and 7 external pages.

There is no https://www.simtek.com/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.simtek.com/en_DE/home and https://www.simtek.com/it_IT all use the title “Home | SIMTEK”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.simtek.com/de_DE/kontakt has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 81 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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “One or more required elements for the slider are missing”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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

Opening the homepage sets 4 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.