maisonorient.com website review

About 250 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (ContentSquare, Shopify and Klaviyo and others), adding 986 KiB and 714 ms of main-thread time.

ContentSquare costs a phone 517 ms of main-thread work and 185 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.

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

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

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

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

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

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

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.

Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tweed Jacket - Maison OrientLalo CardigansMaison OrientJack…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.2 MB in 289 requests on a phone: images 1.1 MB (34), scripts 1.1 MB (144) and other files 652 KiB (91). Under 2 MB keeps phones on slow connections fast.

1 image (92 KiB) is 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 0.90 g of CO₂e: 107.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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.

Structured data found (BreadcrumbList, OnlineStore, Product and WebSite) but with 1 problem, for example “Product: image is not an absolute URL ("https:files/khai-mini-bag-bambi-8903861.jpg")”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 276 pages on maisonorient.com and 1 external page.

https://maisonorient.com/collections/all and https://maisonorient.com/collections/clothing-1 use the same meta description. A description written for each page earns more clicks.

https://maisonorient.com/collections/new-arrivals, https://maisonorient.com/collections/the-chroma-edit-red-cobalt, https://maisonorient.com/collections/new-in-this-week, https://maisonorient.com/collections/the-jacket-edit, https://maisonorient.com/collections/the-statement-makers and https://maisonorient.com/collections/all and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API 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 “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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.

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.

The homepage carries about 635 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 15 cookies, 1 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.