seltenwatch.com website review

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and seel.com and others), adding 1.8 MB and 704 ms of main-thread time.

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

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

YouTube costs a phone 410 ms of main-thread work and 1,005 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.

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

Shopify costs a phone 155 ms of main-thread work and 493 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.

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

38 KiB could be saved by minifying JavaScript.

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

2 images could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

Your largest element takes 13.6 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 20.5 s. Good is under 3.8 s.

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 3.3 MB in 260 requests on a phone: scripts 1.8 MB (72), other files 845 KiB (132) and images 226 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your meta description is only 6 characters: “Selten”. 70 to 160 characters is enough to sell the click.

The homepage links to 21 pages on seltenwatch.com and 3 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.

https://seltenwatch.com/collections/grand-feu-enamel-series, https://seltenwatch.com/collections/m1-moonphase, https://seltenwatch.com/collections/salvage-bronze, https://seltenwatch.com/collections/accessories, https://seltenwatch.com/products/yum-cha-wh-c-x-selten and https://seltenwatch.com/policies/terms-of-service and 4 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://seltenwatch.com/products/jui-%E8%81%9A-bauhinia-cnc-guilloche-mop-whc-x-selten-purple, whose canonical is https://seltenwatch.com/products/jui-%e8%81%9a-bauhinia-cnc-guilloche-mop-whc-x-selten-purple. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://seltenwatch.com/collections/grand-feu-enamel-series, https://seltenwatch.com/collections/m1-moonphase, https://seltenwatch.com/collections/salvage-bronze, https://seltenwatch.com/collections/accessories, https://seltenwatch.com/pages/about-us and https://seltenwatch.com/collections/frontpage have no <h1> headline, so visitors and search engines get no clear main topic.

https://seltenwatch.com/collections/m1-moonphase, https://seltenwatch.com/collections/accessories and https://seltenwatch.com/collections/frontpage have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

Requests the notification permission on page load.

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.

The homepage has only about 30 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads and Meta Pixel (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 21 cookies, 2 of them by other companies (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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.