m-watch.com website review

The page goes through 1 redirect before it starts loading, costing about 12.2 s. Link and advertise the final URL directly.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

A phone's processor spends 13.0 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

7 third-party services load with your homepage (ZenDesk, Cookiebot and Klaviyo and others), adding 1.5 MB and 1.4 s of main-thread time.

ZenDesk costs a phone 852 ms of main-thread work and 865 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.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.9 MB in 562 requests on a phone: images 2.9 MB (176), scripts 2.3 MB (123) and other files 1.3 MB (245). Under 2 MB keeps phones on slow connections fast.

WYA.37110-1-lifestyle1-crop-2.jpg 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).

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 302 pages on m-watch.com and 5 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.

Your homepage links to https://m-watch.com/pages/store-locator, which answers with an error. Visitors hit a dead end and search engines drop it.

https://m-watch.com/en/collections/classic, https://m-watch.com/en/collections/casual, https://m-watch.com/en/collections/uhren-mit-gehausedurchmesser-22-mm-bis-28-mm, https://m-watch.com/en/collections/gehausedurchmesser-von-35-bis-38-mm, https://m-watch.com/en/collections/gehausedurchmesser-von-40-bis-44-mm and https://m-watch.com/en/collections/damen and 6 others use the same meta description. A description written for each page earns more clicks.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Unexpected token ')'”.

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

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

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