Website review, no card needed

somage.com.au logo

somage.com.au website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 78 checks

This review found 39 issues worth fixing on somage.com.au, 12 of them high impact, across 78 checks. The most urgent: page weight: 22.3 MB in 226 requests. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
6.8 s2.4 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.3 s
May 23, 20266.1 s
May 30, 20266.0 s
Jun 6, 20265.8 s
Jun 13, 20265.5 s
Jun 20, 20265.2 s
Jun 27, 20264.0 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20263.3 s
Aug 22, 20263.4 s
Aug 29, 20263.6 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20264.2 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
292 ms78 msMay 16Oct 31156 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026267 ms
May 23, 2026248 ms
May 30, 2026246 ms
Jun 6, 2026228 ms
Jun 13, 2026200 ms
Jun 20, 2026160 ms
Jun 27, 2026119 ms
Jul 4, 2026112 ms
Jul 11, 2026113 ms
Jul 18, 2026111 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026122 ms
Aug 22, 2026130 ms
Aug 29, 2026142 ms
Sep 5, 2026155 ms
Sep 12, 2026151 ms
Sep 19, 2026144 ms
Sep 26, 2026141 ms
Oct 3, 2026133 ms
Oct 10, 2026138 ms
Oct 17, 2026144 ms
Oct 24, 2026144 ms
Oct 31, 2026156 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

Full-page screenshot of somage.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. somage.com.au at 0.5 s0.5 s
  2. somage.com.au at 1.0 s1.0 s
  3. somage.com.au at 1.5 s1.5 s
  4. somage.com.au at 2.0 s2.0 s
  5. somage.com.au at 2.5 s2.5 s
  6. somage.com.au at 3.0 s3.0 s
  7. somage.com.au at 3.6 s3.6 s
  8. somage.com.au at 4.1 s4.1 s

Speed

5 to fix
  • 8 third-party services on the page

    8 third-party services load with your homepage (ContentSquare, Klaviyo and Google Tag Manager and others), adding 3.3 MB and 729 ms of main-thread time.

  • ContentSquare adds 279 ms

    279 ms

    ContentSquare costs a phone 279 ms of main-thread work and 187 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.

  • Main-thread work: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 19 ms

    19 ms

    Shopify costs a phone 19 ms of main-thread work and 2.3 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.

  • Klaviyo adds 181 ms

    181 ms

    Klaviyo costs a phone 181 ms of main-thread work and 511 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.

  • Font display

    50 ms

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

  • 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: 10 ms

    10 ms

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

Core Web Vitals

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

  • Speed Index: 9.1 s

    9.1 s

    Visually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.1 s

    3.1 s

    The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.7 s

    3.7 s

    Real visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.6 s

    2.6 s

    Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 879 ms

    879 ms

    Real visitors wait 879 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 162 ms

    162 ms

    Real visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 42% faster for real visitors

    -42%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 267 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 40% faster for real visitors

    -40%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.3 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix28
  • Page weight: 22.3 MB in 226 requests

    22.3 MB

    Your homepage downloads 22.3 MB in 226 requests on a phone: media 16.5 MB (2), images 3.4 MB (34) and scripts 1.3 MB (95). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    2.0 MB

    7 images are downloaded at several times the size a phone draws them, for example sample-black-tea-3.jpg at 2,500 px wide, shown at 265 px. Resized copies would save about 2.0 MB.

  • 1 image over 500 KB

    sample-black-tea-3.jpg weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • 5 images below the first screen load straight away

    5 images further down the page (944 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.3 g of CO₂ per visit

    6.31 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

11 to fixGoogle 6283
  • 9 buttons without a name

    9 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    6 dropdowns have no label.

  • ARIA attributes must conform to valid names (1 element)

    ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 26 images without alt text

    26 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (22 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 39 form fields without a label

    39 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (9 elements)

    ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7783
  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Specialty Tea, Chai & Drinking Chocolate”, “Wholesale login” and “Forgot your password”). One clear main headline is easier for people and search engines.

  • Meta description is long (248 characters)

    Your meta description is 248 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.

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 125 internal links, 3 external

    The homepage links to 125 pages on somage.com.au and 3 external pages.

4 checks passed
  • Title: 65 characters

    Your title is a healthy 65 characters: “Somage Australia | Organic Tea, Drinking Chocolate, Chai & Matcha”.

  • Canonical URL set

    The canonical URL is https://somage.com.au/.

  • 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://somage.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 (689 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://somage.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://somage.com.au/collections/all, https://somage.com.au/collections/fresh-chai, https://somage.com.au/collections/matcha, https://somage.com.au/collections/ingredients, https://somage.com.au/collections/gift-boxes and https://somage.com.au/collections/sample and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://somage.com.au/collections/all, https://somage.com.au/collections/tea-tisane, https://somage.com.au/collections/fresh-chai, https://somage.com.au/collections/matcha, https://somage.com.au/collections/teaware and https://somage.com.au/collections/ingredients and 5 others have 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 77 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    32 of 38 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 330 words of copy

    The homepage carries about 330 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: “APPLY” and “Apply for wholesale”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Shop All” and “Reserve Selection”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 28 cookies set on arrival

    28

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 somage.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · attn.tv · gorgias.chat · 9gtb.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

Company

Headquarters
Melbourne

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 somage.com.au, including 12 speed issues, 5 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

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