miba.com website review

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

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

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

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

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

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

12 KiB could be saved by minifying CSS.

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

1 third-party service load with your homepage (datareporter.eu), adding 56 KiB and 33 ms of main-thread time.

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.

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 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Your homepage downloads 9.3 MB in 64 requests on a phone: images 8.9 MB (40), scripts 185 KiB (10) and fonts 84 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

31 images (6.9 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.

1 image is downloaded at several times the size a phone draws it, for example bgf.png at 250 px wide, shown at 80 px. Resized copies would save about 8 KiB.

5 images further down the page (250 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 2.63 g of CO₂e: 316.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 elements have a tabindex above 0, which scrambles the keyboard order.

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

Your title is only 10 characters: “Miba: Home”. 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.

There are 2 <h1> headlines (“Miba AG” and “Wie Miba Technologien einen Beitrag zu den nachha…”). One clear main headline is easier for people and search engines.

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

Your meta description is 519 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.

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 131 pages on miba.com and 30 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.miba.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.miba.com/de and https://www.miba.com/en all use the title “Miba: Home”, 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.miba.com/de/agb, https://www.miba.com/de/impressum, https://www.miba.com/de/datenschutz, https://www.miba.com/de/default-f0ee4b6752, https://www.miba.com/de/default-e900f7ad69 and https://www.miba.com/de/unternehmen and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miba.com/de/default-f0ee4b6752, https://www.miba.com/de/default-e900f7ad69, https://www.miba.com/de/unternehmen and https://www.miba.com/de/lighthouse have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.miba.com/de/lighthouse took over 3 s to send its HTML from our server.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 250 words of visible text.

Opening the homepage sets 1 cookie (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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.