Website review, no card needed
toolbox.id.au website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 72 checks
This review found 32 issues worth fixing on toolbox.id.au, 8 of them high impact, across 72 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
75C- #63,524 of 96,272 reviewed websitesbeats 30%
- #38,651 of 52,120 online storesbeats 22%
- #417 of 1,086 Squarespace websitesbeats 55%
Closest competitors among online stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Reduce unused JavaScript
2.4 s · 470 KiBAbout 470 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.1 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
3 third-party services on the page
3 third-party services load with your homepage (Squarespace, sqspcdn.com and squarespace-cdn.com), adding 2.3 MB and 921 ms of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Squarespace adds 858 ms
858 msSquarespace costs a phone 858 ms of main-thread work and 1.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.
Reduce unused CSS
760 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Improve image delivery
846 KiB7 images could be 846 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
300 ms · 94 KiBPolyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 329 ms. During a long task the page ignores taps.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 870 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 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.
Use efficient cache lifetimes
150 ms · 13 KiB1 file is served with short cache lifetimes, so returning visitors download them again (13 KiB).
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
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 61 ms
61 msYour server sent the HTML in 61 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 333 ms
333 msScripts block taps and scrolling for 333 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 66 requests
2.5 MBYour homepage downloads 2.5 MB in 66 requests on a phone: images 1.1 MB (8), scripts 1.0 MB (39) and stylesheets 169 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.6 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
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
14 H1 headlines
There are 14 <h1> headlines (“GRAPHIC DESIGN /”, “BRANDING /” and “PUBLICATIONS /”). One clear main headline is easier for people and search engines.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/69d722534d12ac6223a…”.
47 internal links, 3 external
The homepage links to 47 pages on toolbox.id.au and 3 external pages.
5 checks passed
Title: 33 characters
Your title is a healthy 33 characters: “Graphic Design Adelaide | TOOLBOX”.
Canonical URL set
The canonical URL is https://www.toolbox.id.au/.
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.toolbox.id.au/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.toolbox.id.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.
2 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, description and contact details; logo and sameAs (social profiles) would complete it.
Other pages
2 pages share a title
https://www.toolbox.id.au/our-work and https://www.toolbox.id.au/work all use the title “Graphic Design Portfolio Adelaide | Our Work — TOOLBOX”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.toolbox.id.au/our-work and https://www.toolbox.id.au/work use the same meta description. A description written for each page earns more clicks.
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.toolbox.id.au/work, whose canonical is https://www.toolbox.id.au/our-work. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.toolbox.id.au/about has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.toolbox.id.au/packaging, https://www.toolbox.id.au/identity, https://www.toolbox.id.au/signage, https://www.toolbox.id.au/publications, https://www.toolbox.id.au/digital and https://www.toolbox.id.au/contact 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Every page has a meta description
All 9 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/69d722534d12ac6223a6e824/108/5c5…”.
2 checks passed
Tap targets are thumb-sized
17 of 18 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
Only about 87 words
The homepage has only about 87 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “CONTACT” and “CONTACT US”.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 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 toolbox.id.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on toolbox.id.au, including 17 speed issues, 3 SEO issues and 6 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.