maje.sa website review

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

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

8 third-party services load with your homepage (POWr, customerfields.com and Clarity and others), adding 589 KiB and 1.4 s of main-thread time.

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

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

POWr costs a phone 528 ms of main-thread work and 13 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.

customerfields.com costs a phone 351 ms of main-thread work and 232 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.

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

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

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

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

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

Polyfills for old browsers add 7 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.

5 KiB could be saved by minifying JavaScript.

4 KiB could be saved by minifying CSS.

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.

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Singles Day Online Event 22% Off Full-Priced Styles”.

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 387 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 26.9 MB in 396 requests on a phone: media 23.0 MB (2), images 1.5 MB (62) and other files 1.3 MB (221). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (116 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

3 dropdowns have no label.

Form elements should have a visible label: 5 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

There are 3 <h1> headlines (“”, “Singles Day Online Event22% Off Full-Priced Styles” and “SaleUp to 50% off*”). One clear main headline is easier for people and search engines.

The homepage links to 225 pages on maje.sa and 26 external pages.

https://maje.sa/pages/faq and https://maje.sa/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

https://maje.sa/products/mfpro04615-rhinestone-knit-maxi-dress-black, https://maje.sa/products/mfpro05091-ruffled-knit-maxi-dress-black, https://maje.sa/products/mfpro04719-mirrored-crochet-dress-red, https://maje.sa/products/mfpju01410-long-embroidered-skirt-black, https://maje.sa/products/mfpro04263-long-babydoll-knit-dress-white and https://maje.sa/products/mfpro04965-beaded-and-rhinestone-shirt-dress-white and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://maje.sa/products/mfpju01410-long-embroidered-skirt-black and https://maje.sa/products/mfpca00691-rhinestone-knit-cardigan-black took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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

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