Programmable

Website review, no card needed

maisonanje.com logo

maisonanje.com website review

Visit site (opens in a new tab)Reviewed 7 November 202627 issues · 80 checks

This review found 27 issues worth fixing on maisonanje.com, 10 of them high impact, across 80 checks. The most urgent: main-thread work: 5.3 s. 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

Site score

86B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sJun 27Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20261.8 s
Jul 11, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
89 ms78 msSep 5Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202686 ms
Sep 12, 202687 ms
Sep 19, 202682 ms
Sep 26, 202681 ms
Oct 3, 202682 ms
Oct 10, 202679 ms
Oct 17, 202684 ms
Oct 24, 202686 ms
Oct 31, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

maisonanje.com (opens in a new tab)
Full-page screenshot of maisonanje.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maisonanje.com at 1.0 s1.0 s
  2. maisonanje.com at 2.0 s2.0 s
  3. maisonanje.com at 3.0 s3.0 s
  4. maisonanje.com at 4.0 s4.0 s
  5. maisonanje.com at 5.0 s5.0 s
  6. maisonanje.com at 6.0 s6.0 s
  7. maisonanje.com at 7.0 s7.0 s
  8. maisonanje.com at 8.1 s8.1 s

Speed

5 to fix83

  • Main-thread work: 5.3 s

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

  • Mobile performance score: 83

    83/100

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

  • Reduce unused JavaScript

    150 ms · 446 KiB

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

  • Render-blocking requests

    450 ms

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

  • Shopify adds 120 ms

    120 ms

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

  • Improve image delivery

    150 ms · 246 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (weglot.com, Shopify and nfcube.com and others), adding 994 KiB and 279 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • Use efficient cache lifetimes

    146 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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.

1 checks passed

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

2 to fix100

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 100 ms

    100 ms

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

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.09

    0.09

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

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 33 ms

    33 ms

    Scripts block the page for only 33 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85

  • Page weight: 3.8 MB in 339 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 339 requests on a phone: other files 1.7 MB (250), images 1,013 KiB (20) and scripts 958 KiB (56). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.07 g

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

2 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 9090

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 tap target too small

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

  • Heading levels should only increase by one (1 element)

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9280

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (11 characters)

    Your title is only 11 characters: “Maison Anje”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 68 internal links, 2 external

    The homepage links to 68 pages on maisonanje.com and 2 external pages.

5 checks passed

  • One H1 headline

    Your main headline reads: “Maison Anje”.

  • Canonical URL set

    The canonical URL is https://maisonanje.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://maisonanje.com/sitemap.xml.

AI search readiness

1 to fix88

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://maisonanje.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90

  • 14 pages without a meta description

    https://maisonanje.com/collections/nouveautes, https://maisonanje.com/collections/les-essentiels, https://maisonanje.com/collections/ventes-privees, https://maisonanje.com/collections/soldes-mailles, https://maisonanje.com/collections/soldes-accessoires and https://maisonanje.com/pages/lookbook and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://maisonanje.com/collections/nouveautes, https://maisonanje.com/collections/les-essentiels, https://maisonanje.com/collections/ventes-privees, https://maisonanje.com/collections/soldes-mailles, https://maisonanje.com/collections/soldes-accessoires and https://maisonanje.com/pages/marque and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://maisonanje.com/collections/soldes-accessoires, https://maisonanje.com/pages/lookbook, https://maisonanje.com/pages/marque, https://maisonanje.com/pages/inscription-b2b, https://maisonanje.com/collections/archives and https://maisonanje.com/products/pull-benedian-grenat and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 20 small tap targets

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

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

  • No call to action on the first screen

    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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 256 words of copy

    The homepage carries about 256 words of visible text.

2 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “E-SHOP”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 10 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 maisonanje.com, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sc Easy Redirects · Sami B2b Lock · Instafeed · Weglot Translate Your Store · Wholesale Lock Hide Price · Pushowl · Forms · Iwish · Bestpush

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on maisonanje.com, including 7 speed issues, 3 SEO issues and 4 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