Programmable

Website review, no card needed

ttracing.com.au logo

ttracing.com.au website review

Visit site (opens in a new tab)Reviewed 11 November 202641 issues · 92 checks

This review found 41 issues worth fixing on ttracing.com.au, 15 of them high impact, across 92 checks. The most urgent: page weight: 17.9 MB in 1,279 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

80B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.9 s1.5 sMay 23Nov 71.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Nov 7, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
138 ms120 msMay 23Nov 7126 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026129 ms
May 30, 2026132 ms
Jun 6, 2026133 ms
Jun 13, 2026135 ms
Jun 20, 2026136 ms
Jun 27, 2026132 ms
Jul 4, 2026130 ms
Jul 11, 2026129 ms
Jul 18, 2026125 ms
Jul 25, 2026123 ms
Aug 1, 2026122 ms
Aug 8, 2026127 ms
Aug 15, 2026128 ms
Aug 22, 2026129 ms
Aug 29, 2026130 ms
Sep 5, 2026131 ms
Sep 12, 2026129 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026125 ms
Oct 10, 2026127 ms
Oct 17, 2026127 ms
Oct 24, 2026127 ms
Oct 31, 2026128 ms
Nov 7, 2026126 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

ttracing.com.au (opens in a new tab)
Full-page screenshot of ttracing.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ttracing.com.au at 1.1 s1.1 s
  2. ttracing.com.au at 2.2 s2.2 s
  3. ttracing.com.au at 3.3 s3.3 s
  4. ttracing.com.au at 4.4 s4.4 s
  5. ttracing.com.au at 5.5 s5.5 s
  6. ttracing.com.au at 6.6 s6.6 s
  7. ttracing.com.au at 7.7 s7.7 s
  8. ttracing.com.au at 8.8 s8.8 s

Speed

10 to fix45

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8,199 HTML elements

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

  • Main-thread work: 6.2 s

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

  • Improve image delivery

    150 ms · 2.2 MB

    27 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    750 ms · 146 KiB

    About 146 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

    450 ms · 343 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, jQuery CDN and productessentials.app and others), adding 1,005 KiB and 682 ms of main-thread time.

  • Font display

    350 ms

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

  • Shopify adds 260 ms

    260 ms

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

  • Use efficient cache lifetimes

    201 KiB

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

  • 16 long tasks on the main thread

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

  • Legacy JavaScript

    48 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

1 checks passed

  • Server response: 38 ms

    38 ms

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

Core Web Vitals

6 to fix100

  • Largest Contentful Paint: 47.0 s

    47.0 s

    Your largest element takes 47.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Eight Friends, One Comfy Seat”.

  • Time to Interactive: 56.3 s

    56.3 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 527 ms

    527 ms

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

  • 27 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • 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.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 158 ms

    158 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 420 ms

    420 ms

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

  • Cumulative Layout Shift: 0.096

    0.096

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

Images and page weight

3 to fix53

  • Page weight: 17.9 MB in 1,279 requests

    17.9 MB

    Your homepage downloads 17.9 MB in 1,279 requests on a phone: images 16.6 MB (962), scripts 935 KiB (85) and HTML 185 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    DESK_POWER_PACK_-_AU_7ab0e05c-84ad-4a06-b994-73969f197b30.jp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    122 KiB

    2 images are downloaded at several times the size a phone draws them, for example VAN-nav-img.png at 1,200 px wide, shown at 61 px. Resized copies would save about 122 KiB.

  • About 5.1 g of CO₂ per visit

    5.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.07 g of CO₂e: 608.1 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

12 to fixGoogle 6784

  • 16 buttons without a name

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

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 15 text elements with low contrast

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

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 2 images without alt text

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

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

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

  • Alternative text of images should not be repeated as text (99 elements)

    Alternative text of images should not be repeated as text: 99 elements on the page fail this check, rated minor by axe-core.

  • 66 form fields without a label

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

  • Hidden but focusable

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

  • 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), which makes the page harder to scan with a screen reader.

1 checks passed

  • 48 automated accessibility rules passed

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

4 to fixGoogle 6984

  • 79 links with vague text

    79 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Best Gaming Chair, Standing Desk & Office Chair | TTRacing Australia”.

  • Meta description is long (303 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 582 internal links, 16 external

    The homepage links to 582 pages on ttracing.com.au and 16 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “TTRacing Australia”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://ttracing.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90

  • 4 pages without a meta description

    https://ttracing.com.au/pages/bundle-sale-13, https://ttracing.com.au/pages/bundle-sale-14, https://ttracing.com.au/pages/bundle-sale-15 and https://ttracing.com.au/pages/bundle-sale-12 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://ttracing.com.au/pages/bt21-ora-sofa, https://ttracing.com.au/pages/bundle-deals, https://ttracing.com.au/pages/bundle-sale-2, https://ttracing.com.au/pages/bundle-sale-10, https://ttracing.com.au/pages/bundle-sale-3 and https://ttracing.com.au/pages/bundle-sale-13 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://ttracing.com.au/pages/bt21-ora-sofa, https://ttracing.com.au/pages/bundle-deals, https://ttracing.com.au/pages/bundle-sale-2, https://ttracing.com.au/pages/bundle-sale-10, https://ttracing.com.au/pages/bundle-sale-3 and https://ttracing.com.au/pages/bundle-sale-13 and 8 others 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.

  • 7 pages slow to respond

    https://ttracing.com.au/pages/bundle-sale-13, https://ttracing.com.au/pages/bundle-sale-7, https://ttracing.com.au/pages/bundle-sale-15, https://ttracing.com.au/pages/bundle-sale-5, https://ttracing.com.au/pages/bundle-sale-9 and https://ttracing.com.au/pages/bundle-sale-12 and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

    324 of 326 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: 2 trust badges. 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 1,811 words of copy

    The homepage carries about 1,811 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “Contact”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop Now”, “Contact” and “Contact Us”.

  • 27 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix

  • 2 trackers load before any consent

    2

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

  • 7 cookies set on arrival

    7

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

  • 22 other companies contacted

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

Apps your storefront loads

Judge Me Reviews · Microsoft Clarity · Assortion · Mp Instagram Feed · Eg Auto Add To Cart · Powerful Form Builder · Orbe Geolocation · Forms · Frontend · Pdf Generator · cloudfront.net · trackedlink.net

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 | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on ttracing.com.au, including 16 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

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