Website review, no card needed
toypark.com.au website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 91 checks
This review found 46 issues worth fixing on toypark.com.au, 21 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
67D- #112,935 of 126,070 reviewed websitesbeats 9%
- #66,496 of 70,349 online storesbeats 4%
- #60,958 of 63,885 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 184 ms |
| May 23, 2026 | 192 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 193 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 199 ms |
| Jul 18, 2026 | 207 ms |
| Jul 25, 2026 | 203 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 201 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 215 ms |
| Sep 5, 2026 | 226 ms |
| Sep 12, 2026 | 234 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 225 ms |
| Oct 3, 2026 | 222 ms |
| Oct 10, 2026 | 228 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 251 ms |
| Oct 31, 2026 | 254 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.4 s
2.7 s
4.1 s
5.4 s
6.8 s
8.1 s
9.5 s
10.8 s
Speed
Reduce unused JavaScript
2.1 s · 903 KiBAbout 903 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Improve image delivery
1.1 s · 674 KiB18 images could be 674 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.6 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 11.9 s
A phone's processor spends 11.9 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,661 HTML elements
The page has 6,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, rebuyengine.com and Google Tag Manager and others), adding 3.1 MB and 1.9 s of main-thread time.
Shopify adds 874 ms
874 msShopify costs a phone 874 ms of main-thread work and 1.7 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 818 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
500 ms · 306 KiB17 files are served with short cache lifetimes, so returning visitors download them again (306 KiB).
Reduce unused CSS
450 ms · 123 KiBAbout 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
rebuyengine.com adds 377 ms
377 msrebuyengine.com costs a phone 377 ms of main-thread work and 766 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.
Google Tag Manager adds 268 ms
268 msGoogle Tag Manager costs a phone 268 ms of main-thread work and 162 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.
Minify JavaScript
150 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
Legacy JavaScript
93 KiBPolyfills for old browsers add 93 KiB JavaScript that modern phones do not need.
Font display
50 msWeb 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 CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 0.41
0.41For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 66.4 s
66.4 sYour largest element takes 66.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 85.3 s
85.3 sThe page becomes fully interactive after 85.3 s. Good is under 3.8 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Real-user INP: 400 ms
400 msReal visitors wait 400 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 184 ms to 254 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 442 ms
442 msReal visitors wait 442 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 25.8 MB in 536 requests
25.8 MBYour homepage downloads 25.8 MB in 536 requests on a phone: images 21.4 MB (125), scripts 2.2 MB (159) and other files 1.4 MB (195). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (44 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.3 g of CO₂ per visit
7.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.31 g of CO₂e: 876.9 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
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (17 elements)
Alternative text of images should not be repeated as text: 17 elements on the page fail this check, rated minor by axe-core.
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.
1 checks passed
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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Montessori Wooden Toys and Kids Furniture in Australia — Toypark Australia”.
Meta description is long (305 characters)
Your meta description is 305 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.
439 internal links, 13 external
The homepage links to 439 pages on toypark.com.au and 13 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.toypark.com.au/.
Structured data in place
Structured data found: BreadcrumbList, OnlineStore, 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.toypark.com.au/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,978 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.toypark.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.toypark.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.toypark.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.toypark.com.au/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.toypark.com.au/pages/return-policy, whose canonical is https://www.toypark.com.au/pages/shipping-return-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.toypark.com.au/customer_authentication/redirect 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 150 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
5 broken images
5 images failed to load on a phone, for example https://review-images.judgeme.com/toypark-australia/1779696593__img_6498__original.jpeg?quality=80&width=480.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
2 checks passed
Tap targets are thumb-sized
169 of 169 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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 2,341 words of copy
The homepage carries about 2,341 words of visible text.
8 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop By Age”, “Santa's Shop” and “Call”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 19 trust badges and “200+ Brands”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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, Klaviyo and Meta Pixel 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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 2 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 toypark.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Schema Plus For Seo · Judge Me Reviews · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Trymry · Swym Wishlist Plus · gorgias.chat · nfcube.com · rebuyengine.com · vidjet.io · 9gtb.com · goaffpro.com · rise-ai.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on toypark.com.au, including 23 speed issues, 4 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.