atelierwen.com website review

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

8 third-party services load with your homepage (Google Tag Manager, zaapi.com and Shopify and others), adding 2.3 MB and 2.5 s of main-thread time.

About 1,005 KiB of JavaScript is downloaded but never used on this page.

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

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

zaapi.com costs a phone 676 ms of main-thread work and 682 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.

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

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

Klaviyo costs a phone 245 ms of main-thread work and 403 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.

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

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

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DISCOVER THE COLLECTION”. Most of its time is element render delay (2.4 s).

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

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

Your homepage downloads 18.4 MB in 253 requests on a phone: media 13.8 MB (3), scripts 2.5 MB (114) and images 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.

10 images (1.2 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.

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

1 dropdown has no label.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

7 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 67 characters, so Google will cut it off around 60: “Atelier Wen | Chinese Craftsmanship, Independent Luxury Watchmaking”.

1 link has no real href, so search engines can't follow it.

The homepage links to 63 pages on atelierwen.com and 11 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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 17 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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.