Website review, no card needed

studio309.com.au logo

studio309.com.au website review

Visit site (opens in a new tab)Reviewed 12 November 202626 issues · 75 checks

This review found 26 issues worth fixing on studio309.com.au, 6 of them high impact, across 75 checks. The most urgent: 2 tap targets too small. 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 studio309.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix86
  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 208 KiB

    About 208 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (cdn-website.com, Google Tag Manager and Snowplow and others), adding 1.7 MB and 356 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 72 KiB

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

  • cdn-website.com adds 174 ms

    174 ms

    cdn-website.com costs a phone 174 ms of main-thread work and 1.4 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.

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Improve image delivery

    37 KiB

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

  • 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

    2 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix82
  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.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: 6.3 s

    6.3 s

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

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

4 checks passed
  • Total Blocking Time: 122 ms

    122 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.4 s

    1.4 s

    Visually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.51 g

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

4 checks passed
  • Page weight: 1.8 MB in 84 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 84 requests on a phone: images 987 KiB (41), scripts 609 KiB (27) and fonts 106 KiB (4). That is a lean page.

  • 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

5 to fixGoogle 8391
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 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 (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 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

4 to fixGoogle 8584
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“CRAFTED IN VICTORIA”, “A TASTE OF WHAT'S IN STORE” and “For artisan details and profiles visit the artisa…”). One clear main headline is easier for people and search engines.

  • Meta description is long (182 characters)

    Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 65 internal links, 2 external

    The homepage links to 65 pages on studio309.com.au and 2 external pages.

5 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Studio 309 - local handcrafted goods”.

  • Canonical URL set

    The canonical URL is https://www.studio309.com.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.studio309.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (519 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix74
  • 1 page points its canonical at the homepage

    https://www.studio309.com.au/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://www.studio309.com.au/blank and https://www.studio309.com.au/more-infoa90bc967 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages share 2 titles

    /, https://www.studio309.com.au/home, https://www.studio309.com.au/blank and https://www.studio309.com.au/more-infoa90bc967 all use the title “Studio 309 - local handcrafted goods”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.studio309.com.au/artisan, https://www.studio309.com.au/home, https://www.studio309.com.au/contact, https://www.studio309.com.au/gallery, https://www.studio309.com.au/blank and https://www.studio309.com.au/more-infoa90bc967 use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.studio309.com.au/contact has 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.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

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

  • About 439 words of copy

    The homepage carries about 439 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “CONTACT”, “BUY VOUCHER ONLINE” and “[email protected]”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 studio309.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on studio309.com.au, including 7 speed issues, 4 SEO issues and 3 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