Website review, no card needed
emamaco.com.au website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 88 checks
This review found 39 issues worth fixing on emamaco.com.au, 12 of them high impact, across 88 checks. The most urgent: page weight: 11.4 MB in 419 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #39,685 of 117,615 reviewed websitesbeats 61%
- #26,539 of 66,923 online storesbeats 54%
- #25,602 of 61,018 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 157 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 105 ms |
| Nov 7, 2026 | 109 ms |
| Nov 14, 2026 | 111 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
5.9 s
6.9 s
7.9 s
Speed
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.3 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 (YouTube, Google Tag Manager and myshopishop.com and others), adding 7.6 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
YouTube adds 956 ms
956 msYouTube costs a phone 956 ms of main-thread work and 1.9 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: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
150 ms · 688 KiB40 files are served with short cache lifetimes, so returning visitors download them again (688 KiB).
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Google Tag Manager adds 437 ms
437 msGoogle Tag Manager costs a phone 437 ms of main-thread work and 523 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.
Shopify adds 32 ms
32 msShopify costs a phone 32 ms of main-thread work and 4.1 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.
myshopishop.com adds 306 ms
306 msmyshopishop.com costs a phone 306 ms of main-thread work and 815 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 288 ms. During a long task the page ignores taps.
2,160 HTML elements
The page has 2,160 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 217 KiB20 images could be 217 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.
Reduce unused CSS
112 KiBAbout 112 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
95 KiB95 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 37.0 s
37.0 sThe page becomes fully interactive after 37.0 s. Good is under 3.8 s.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 588 ms
588 msScripts block taps and scrolling for 588 ms in total while the page loads. Good is under 200 ms.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 649 ms
649 msReal visitors wait 649 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 137 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Images and page weight
Page weight: 11.4 MB in 419 requests
11.4 MBYour homepage downloads 11.4 MB in 419 requests on a phone: media 3.4 MB (2), scripts 3.3 MB (105) and images 2.8 MB (142). Under 2 MB keeps phones on slow connections fast.
12 images below the first screen load straight away
12 images further down the page (715 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (325 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 3.2 g of CO₂ per visit
3.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.24 g of CO₂e: 388.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
122 buttons without a name
122 buttons have no accessible name, so screen readers announce just “button”.
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.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
37 images without alt text
37 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail 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).
1 checks passed
47 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: 47 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “Maternity Leggings, Shapewear & Activewear -Australia Online | Emamaco – emamaco”.
Meta description is long (203 characters)
Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
78 internal links, 5 external
The homepage links to 78 pages on emamaco.com.au and 5 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.emamaco.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.emamaco.com.au/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.emamaco.com.au/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 (2,140 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.emamaco.com.au/collections/mum-life-activewear and https://www.emamaco.com.au/pages/pregnancy-recovery-ctr have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.emamaco.com.au/collections/off-duty-mum-drop, https://www.emamaco.com.au/collections/all-emamaco-pregnancy, https://www.emamaco.com.au/collections/post-partum, https://www.emamaco.com.au/collections/mum-life-activewear, https://www.emamaco.com.au/collections/gift-vouchers and https://www.emamaco.com.au/pages/shaper-sizing-information and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://www.emamaco.com.au/collections/off-duty-mum-drop, https://www.emamaco.com.au/collections/all-emamaco-pregnancy, https://www.emamaco.com.au/collections/post-partum, https://www.emamaco.com.au/collections/mum-life-activewear, https://www.emamaco.com.au/collections/gift-vouchers and https://www.emamaco.com.au/pages/shaper-sizing-information and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
173 of 174 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 526 words of copy
The homepage carries about 526 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “SHOP”, “Shop more mum brands” and “Shop All”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 2 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 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.
32 other companies contacted
Loading the homepage contacts 32 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 emamaco.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Judge Me Reviews · googleapis.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
- 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 39 issues on emamaco.com.au, including 18 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.