Website review, no card needed

mhstaff.com.au logo

mhstaff.com.au website review

Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 69 checks

This review found 25 issues worth fixing on mhstaff.com.au, 11 of them high impact, across 69 checks. The most urgent: avoid multiple page redirects. 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 mhstaff.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mhstaff.com.au at 0.4 s0.4 s
  2. mhstaff.com.au at 0.8 s0.8 s
  3. mhstaff.com.au at 1.1 s1.1 s
  4. mhstaff.com.au at 1.5 s1.5 s
  5. mhstaff.com.au at 1.9 s1.9 s
  6. mhstaff.com.au at 2.3 s2.3 s
  7. mhstaff.com.au at 2.6 s2.6 s
  8. mhstaff.com.au at 3.0 s3.0 s

Speed

3 to fix90
  • Avoid multiple page redirects

    2.0 s

    The page goes through 2 redirects before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Shopify adds 239 ms

    239 ms

    Shopify costs a phone 239 ms of main-thread work and 517 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 third-party service on the page

    1 third-party service load with your homepage (Shopify), adding 517 KiB and 239 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 26 KiB

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

  • Improve image delivery

    42 KiB

    1 image could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    37 KiB

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

  • Legacy JavaScript

    12 KiB

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

  • Use efficient cache lifetimes

    4 KiB

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

2 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 5.7 s

    5.7 s

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Time to Interactive: 6.4 s

    6.4 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Enter your email and we'll send you a verification code”.

  • Speed Index: 3.6 s

    3.6 s

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

4 checks passed
  • Real-user INP: 107 ms

    107 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Total Blocking Time: 106 ms

    106 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.25 g

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

1 checks passed
  • Page weight: 919 KiB in 53 requests

    919 KiB

    Your homepage downloads 919 KiB in 53 requests on a phone: scripts 289 KiB (27), images 278 KiB (3) and fonts 206 KiB (4). That is a lean page.

Accessibility

2 to fixGoogle 10097
  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

  • Headings skip levels

    Headings skip levels (h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 5860
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (26 characters)

    Your title is only 26 characters: “Maison One – Maison One AU”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 165 internal links, 2 external

    The homepage links to 165 pages on mhstaff.com.au and 2 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.maisonone.com.au/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.maisonone.com.au/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://www.maisonone.com.au/collections/all, https://www.maisonone.com.au/collections/new-arrivals, https://www.maisonone.com.au/collections/armand-de-brignac, https://www.maisonone.com.au/collections/dom-perignon, https://www.maisonone.com.au/collections/krug and https://www.maisonone.com.au/collections/moet-chandon and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.maisonone.com.au/collections/all has 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 45 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://cdn.shopify.com/shopifycloud/customer-authentication-web/production/sprite-86bf53.sv…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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 direct contact details

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

  • Only about 28 words

    The homepage has only about 28 words of visible text; thin pages give Google and first-time buyers little to go on.

4 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “SHOP NOW”, “Subscribe Now” and “Contact Us”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 7 of them by other companies (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 mhstaff.com.au, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gtm Theme App · cloudfront.net · intercom.io · azureedge.net · Swym Wishlist Plus

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on mhstaff.com.au, including 11 speed issues, 4 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