Website review, no card needed

maisonwheat.com logo

maisonwheat.com website review

Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 74 checks

This review found 24 issues worth fixing on maisonwheat.com, 4 of them high impact, across 74 checks. The most urgent: aRIA attributes must conform to valid values (1 element). 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 maisonwheat.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maisonwheat.com at 0.6 s0.6 s
  2. maisonwheat.com at 1.2 s1.2 s
  3. maisonwheat.com at 1.8 s1.8 s
  4. maisonwheat.com at 2.4 s2.4 s
  5. maisonwheat.com at 2.9 s2.9 s
  6. maisonwheat.com at 3.5 s3.5 s
  7. maisonwheat.com at 4.1 s4.1 s
  8. maisonwheat.com at 4.7 s4.7 s

Speed

6 to fix71
  • Improve image delivery

    750 ms · 252 KiB

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

  • Mobile performance score: 71

    71/100

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

  • Render-blocking requests

    750 ms

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

  • Klaviyo adds 181 ms

    181 ms

    Klaviyo costs a phone 181 ms of main-thread work and 386 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.

  • 1,650 HTML elements

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

  • Shopify adds 36 ms

    36 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Klaviyo, Shopify and shareasale.com and others), adding 803 KiB and 218 ms of main-thread time.

  • Legacy JavaScript

    200 ms · 19 KiB

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

  • Use efficient cache lifetimes

    200 ms · 13 KiB

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

  • Reduce unused JavaScript

    140 ms · 72 KiB

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

  • Reduce unused CSS

    140 ms · 20 KiB

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

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 75 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.

  • Forced reflow

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 698 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 8.6 s

    8.6 s

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

  • Time to Interactive: 10.2 s

    10.2 s

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

  • Speed Index: 4.8 s

    4.8 s

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

7 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.2 s

    1.2 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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.

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.038

    0.038

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

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 169 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 169 requests on a phone: images 883 KiB (24), scripts 628 KiB (66) and other files 624 KiB (62). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.3 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

5 to fixGoogle 8994
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 tap target too small

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

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

  • 3 links without text

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

  • 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 69 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Meta description is short (35 characters)

    Your meta description is only 35 characters: “Foundational luxury for every wear.”. 70 to 160 characters is enough to sell the click.

  • No robots.txt

    There is no robots.txt at maisonwheat.com/robots.txt, the first file search crawlers ask for.

  • 216 internal links, 12 external

    The homepage links to 216 pages on maisonwheat.com and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “MAISON WHEAT”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “MAISON WHEAT - Casual Luxury Apparel”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

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

  • XML sitemap found

    Your XML sitemap is reachable at https://maisonwheat.com/sitemap.xml.

AI search readiness

100
2 checks passed
  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 6 pages share 3 titles

    https://maisonwheat.com/collections/best-sellers/women and https://maisonwheat.com/collections/best-sellers/men all use the title “Best Sellers”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://maisonwheat.com/collections/best-sellers/women, https://maisonwheat.com/collections/best-sellers/men, https://maisonwheat.com/collections/scents, https://maisonwheat.com/pages/fabric-guide, https://maisonwheat.com/pages/sets and https://maisonwheat.com/collections/womens and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://maisonwheat.com/collections/best-sellers/women, https://maisonwheat.com/collections/best-sellers/men, https://maisonwheat.com/collections/scents, https://maisonwheat.com/pages/fabric-guide, https://maisonwheat.com/pages/sets and https://maisonwheat.com/collections/womens and 8 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 110 found) and read each the way a search engine does.

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

  • 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 10093
  • 21 small tap targets

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

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

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 561 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “SHOP ALL”, “SHOP NOW” and “Shop NOW”.

  • 2 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 maisonwheat.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Loop Returns · shareasale.com

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 24 issues on maisonwheat.com, including 9 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