mbw.ch website review

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Hotjar and Google Fonts and others), adding 896 KiB and 533 ms of main-thread time.

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

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

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

The page has 1,610 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.

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 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CHILLED MIRROR HYGROMETERS FOR PRECISION DEW POINT & HUMIDI…”. Most of its time is element render delay (4.5 s).

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

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-31, real Chrome visitors' tap response (inp) went from 114 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

<td> elements in a large <table> do not have table headers. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Chilled Mirror Hygrometers | Dew Point & Humidity Measurement | MBW”.

There are 12 <h1> headlines (“Chilled Mirror Hygrometers for Precision Dew Poin…”, “” and “Chilled Mirror Hygrometers for Precision Dew Poin…”). One clear main headline is easier for people and search engines.

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

The homepage links to 464 pages on mbw.ch and 11 external pages.

There is no https://www.process-insights.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.process-insights.com/crds-gas-analyzers-2, https://www.process-insights.com/crds-gas-analyzers-2/product-specification-table, https://www.process-insights.com/crds-gas-analyzers-2/rental-analyzers and https://www.process-insights.com/service/analyzer-upgrades took over 3 s to send their HTML from our server.

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

4 of 10 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.

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 1,364 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Hotjar (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 9 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.