Website review, no card needed
graceandmaggie.com.au website review
Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 82 checks
This review found 33 issues worth fixing on graceandmaggie.com.au, 9 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
86B- #12,337 of 126,661 reviewed websitesbeats 87%
- #7,357 of 70,542 online storesbeats 85%
- #7,121 of 64,026 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 759 ms |
| Jun 6, 2026 | 867 ms |
| Jun 13, 2026 | 968 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 988 ms |
| Jul 4, 2026 | 991 ms |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 99 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 116 ms |
| Oct 31, 2026 | 115 ms |
| Nov 7, 2026 | 113 ms |
| Nov 14, 2026 | 115 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
0.5 s
0.9 s
1.4 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Improve image delivery
1.4 s · 3.5 MB30 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused JavaScript
3.3 s · 779 KiBAbout 779 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 516 KiB18 files are served with short cache lifetimes, so returning visitors download them again (516 KiB).
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (pop-convert.com, Klaviyo and Shopify and others), adding 1.6 MB and 568 ms of main-thread time.
Legacy JavaScript
300 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 992 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,326 HTML elements
The page has 2,326 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 124 ms
124 msKlaviyo costs a phone 124 ms of main-thread work and 331 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 66 ms
66 msShopify costs a phone 66 ms of main-thread work and 405 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.
Reduce unused CSS
150 ms · 29 KiBAbout 29 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Minify JavaScript
8 KiB8 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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.5 s
25.5 sYour largest element takes 25.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Boho design reversible waterproof baby playmat creating sty…”.
Time to Interactive: 26.4 s
26.4 sThe page becomes fully interactive after 26.4 s. Good is under 3.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 100 ms to 115 ms 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: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 475 ms
475 msReal visitors wait 475 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.06
0.06The layout barely moves while loading (CLS 0.06, good is under 0.1).
Total Blocking Time: 94 ms
94 msScripts block the page for only 94 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.9 MB in 295 requests
6.9 MBYour homepage downloads 6.9 MB in 295 requests on a phone: images 4.0 MB (32), scripts 1.6 MB (92) and other files 935 KiB (124). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
award-winning-memory-foam-rug-playmat.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (211 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 1.9 g of CO₂ per visit
1.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 233.3 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
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h1 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
49 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: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “More About The Best Baby Play Mats in Australia”). One clear main headline is easier for people and search engines.
Meta description is long (229 characters)
Your meta description is 229 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
98 internal links, 6 external
The homepage links to 98 pages on graceandmaggie.com.au and 6 external pages.
6 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Grace & Maggie | Baby Play Mats, Sensory Rugs & Loungers”.
Canonical URL set
The canonical URL is https://graceandmaggie.com.au/.
Structured data in place
Structured data found: FAQPage.
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://graceandmaggie.com.au/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
46%The HTML your server sends has 997 of the 2,161 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://graceandmaggie.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.
1 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.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
7 checks passed
Linked pages load
7 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.
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: e is not a function”.
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 2,161 words of copy
The homepage carries about 2,161 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 Reversible Play Mats” and “Shop Snuggle Rug Range”.
13 calls to action
The homepage has 13 calls to action, for example “Shop Reversible Padded Playmats”, “Shop All” and “Shop Plush Memory Foam Rugs”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks, a star rating and 7 trust badges.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
46 other companies contacted
Loading the homepage contacts 46 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 graceandmaggie.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on graceandmaggie.com.au, including 16 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.