mairesale.com website review

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

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

29 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 82 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Intercom, Klaviyo and firebaseapp.com and others), adding 814 KiB and 499 ms of main-thread time.

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

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

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

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.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sell with Mai - Learn more”.

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

Your homepage downloads 5.9 MB in 320 requests on a phone: images 3.7 MB (63), scripts 1,001 KiB (90) and other files 867 KiB (128). Under 2 MB keeps phones on slow connections fast.

2 images (230 KiB) 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 1.67 g of CO₂e: 200.9 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.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 36 elements on the page fail this check, rated minor by axe-core.

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

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

Your <h1> is empty.

The homepage links to 377 pages on mairesale.com and 2 external pages.

https://mairesale.com/en/collections/klanningar, https://mairesale.com/en/collections/byxor, https://mairesale.com/en/collections/ytterklader, https://mairesale.com/en/collections/stickat-sweatshirts, https://mairesale.com/en/collections/toppar-t-shirts and https://mairesale.com/en/collections/skjortor-blusar and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://mairesale.com/en/collections/damklader/Woman, whose canonical is https://mairesale.com/en/collections/damklader/woman. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

44 of 80 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 422 words of visible text.

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