Website review, no card needed

truff.com.au logo

truff.com.au website review

Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 79 checks

This review found 31 issues worth fixing on truff.com.au, 12 of them high impact, across 79 checks. The most urgent: page weight: 20.1 MB in 370 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sJun 27Sep 261.8 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
214 ms120 msJun 27Aug 29203 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 2026152 ms
Jul 4, 2026162 ms
Jul 11, 2026156 ms
Jul 18, 2026137 ms
Jul 25, 2026135 ms
Aug 1, 2026131 ms
Aug 8, 2026132 ms
Aug 15, 2026162 ms
Aug 22, 2026180 ms
Aug 29, 2026203 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 truff.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix57
  • Render-blocking requests

    1.5 s

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Main-thread work: 5.6 s

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. 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 (Google Tag Manager, Hubspot and tidio.co and others), adding 1.4 MB and 813 ms of main-thread time.

  • Reduce unused CSS

    750 ms · 102 KiB

    About 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused JavaScript

    300 ms · 388 KiB

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

  • Google Tag Manager adds 297 ms

    297 ms

    Google Tag Manager costs a phone 297 ms of main-thread work and 315 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.

  • 2,464 HTML elements

    The page has 2,464 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • tidio.co adds 115 ms

    115 ms

    tidio.co costs a phone 115 ms of main-thread work and 515 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 88 ms

    88 ms

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

  • Improve image delivery

    192 KiB

    5 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 13 long tasks on the main thread

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

  • Use efficient cache lifetimes

    184 KiB

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

  • Legacy JavaScript

    32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

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

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix57
  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 30.8 s

    30.8 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 358 ms

    358 ms

    Scripts block taps and scrolling for 358 ms in total while the page loads. Good is under 200 ms.

  • Largest content (LCP) held steady for real visitors

    -9%

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

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

    0.001

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

Images and page weight

3 to fix45
  • Page weight: 20.1 MB in 370 requests

    20.1 MB

    Your homepage downloads 20.1 MB in 370 requests on a phone: media 11.8 MB (4), images 5.3 MB (60) and scripts 1.5 MB (86). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (4.5 MB) 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 5.7 g of CO₂ per visit

    5.70 g

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

2 checks passed
  • 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

6 to fixGoogle 7890
  • 12 text elements with low contrast

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 5 tap targets too small

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 43 images without alt text

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

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

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 48 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: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9291
  • Meta description is long (161 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • 161 internal links, 8 external

    The homepage links to 161 pages on truff.com.au and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “TRUFF High Quality Truffle Products”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “TRUFF® ANZ | Truffle Sauces, Oils and Salts – TRUFF-ANZ”.

  • Canonical URL set

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

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 1 page slow to respond

    https://www.truff.com.au/products/variety-pack took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was 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

    24 of 26 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: 5 customer or partner logos. 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 335 words of copy

    The homepage carries about 335 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 NOW”.

  • 28 calls to action

    The homepage has 28 calls to action, for example “SHOP”, “Shop all gifts” and “Shop all oil”.

  • 23 short forms

    23 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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, HubSpot and Klaviyo 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 3 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.

  • 32 other companies contacted

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

Apps your storefront loads

Schema Plus For Seo · Klaviyo Email Marketing Sms · Pumper Bundles · Yotpo Product Reviews · Simprosys Google Shopping Feed · Trymry · nfcube.com · usefomo.com · hubapi.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 Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on truff.com.au, including 16 speed issues, 2 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