semic.de website review

11 images could be 11.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Fonts and others), adding 327 KiB and 94 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.

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

7 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 6 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.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 13.0 MB in 32 requests on a phone: images 12.4 MB (16), scripts 419 KiB (7) and fonts 120 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images weigh 9.4 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example 1-header-home-page-quantumcube-3.png at 2,200 px wide, shown at 390 px. Resized copies would save about 6.9 MB.

7 images (9.7 MB) 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.

2 images further down the page (46 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 3.68 g of CO₂e: 441.1 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.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

5 images have 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: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

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

Your title is 86 characters, so Google will cut it off around 60: “Home - SEMIC RF Electronic GmbH - RF & Microwave - Artificial Intelligence - AI - SaaS”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No XML sitemap at https://semic.de/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 35 pages on semic.de and 0 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://semic.de/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://semic.de/en/ai-io/data-safety has no meta description, so Google writes the search snippet from whatever text it finds.

https://semic.de/de/startseite, https://semic.de/en/ai-io/overview, https://semic.de/en/ai-io/data-safety, https://semic.de/en/ai-io/worlds-first-software-defined-gpu, https://semic.de/en/ai-io/redefining-data-storage-for-the-quantum-age-and-beyond and https://semic.de/en/ai-io/semic-eyescan and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

1 error was logged to the browser console while the page loaded, for example “Potentially unhandled rejection [1] InvalidValueError at _.dl (https://maps.googleapis.com/maps/api/js?key=AIzaSyCWU8_A…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

Before a visitor clicks anything, the page loads 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 3 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.