Website review, no card needed

maje.qa logo

maje.qa website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 77 checks

This review found 33 issues worth fixing on maje.qa, 10 of them high impact, across 77 checks. The most urgent: page weight: 26.6 MB in 426 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of maje.qa (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maje.qa at 1.5 s1.5 s
  2. maje.qa at 3.0 s3.0 s
  3. maje.qa at 4.5 s4.5 s
  4. maje.qa at 6.0 s6.0 s
  5. maje.qa at 7.6 s7.6 s
  6. maje.qa at 9.1 s9.1 s
  7. maje.qa at 10.6 s10.6 s
  8. maje.qa at 12.1 s12.1 s

Speed

9 to fix69
  • Render-blocking requests

    1.6 s

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

  • Main-thread work: 5.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, customerfields.com and Exponea and others), adding 23.8 MB and 638 ms of main-thread time.

  • Shopify adds 24 ms

    24 ms

    Shopify costs a phone 24 ms of main-thread work and 23.3 MB 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.

  • Mobile performance score: 69

    69/100

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

  • 10 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 83 KiB

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

  • 2,548 HTML elements

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

  • Use efficient cache lifetimes

    253 KiB

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

  • Reduce unused JavaScript

    191 KiB

    About 191 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    39 KiB

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

  • Legacy JavaScript

    7 KiB

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

    Your server sent the HTML in 12 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix72
  • Time to Interactive: 10.8 s

    10.8 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 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”.

  • Total Blocking Time: 417 ms

    417 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0.061

    0.061

    The layout barely moves while loading (CLS 0.061, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 26.6 MB in 426 requests

    26.6 MB

    Your homepage downloads 26.6 MB in 426 requests on a phone: media 23.0 MB (2), other files 1.4 MB (246) and images 1.1 MB (58). Under 2 MB keeps phones on slow connections fast.

  • About 7.5 g of CO₂ per visit

    7.53 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7889
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 5 text elements with low contrast

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

  • Form elements should have a visible label (5 elements)

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

  • 1 tap target too small

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

  • All page content should be contained by landmarks (27 elements)

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

  • Zoom is disabled

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

  • 11 form fields without a label

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

  • 2 links without text

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

  • ARIA role should be appropriate for the element (3 elements)

    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)

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

2 checks passed
  • Every image has alt text

    All 156 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • 3 H1 headlines

    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.

  • Structured data has 1 problem

    Structured data found (Organization, WebSite and Website) but with 1 problem, for example “Organization: url points at a different host (https://www.maje.sa/)”.

  • 200 internal links, 28 external

    The homepage links to 200 pages on maje.qa and 28 external pages.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Find your fashion edge at Maje Qatar. Explore sophisticated, statement-making looks inspired by Paris—with free deliver…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Maje Qatar | Bold Parisian Style for Women – Free Delivery”.

  • Canonical URL set

    The canonical URL is https://www.maje.qa/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.maje.qa/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.maje.qa/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (899 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

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

  • 15 pages without an H1

    https://www.maje.qa/products/mfpts01037-t-shirt-with-small-embroidered-logo-white, https://www.maje.qa/products/mfpro04999-ruffled-maxi-dress-burgundy, https://www.maje.qa/products/mfpve00845-tweed-jacket-with-chain-trim-dark-brown, https://www.maje.qa/products/mfpve00822-short-sleeved-tweed-jacket-ecru, https://www.maje.qa/products/mfppa00876-tweed-trousers-dark-brown and https://www.maje.qa/products/mfpro05107-maje-knitted-dress-navy and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    62 of 65 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

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

  • About 1,174 words of copy

    The homepage carries about 1,174 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “TRACK MY ORDER” and “Shop Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Track my order”, “Shop Now” and “Contact us”.

  • 10 short forms

    10 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 26 other companies contacted

    Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at maje.qa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Helium Customer Fields · Boost Ai Search Filter · avada.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on maje.qa, including 14 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25