Website review, no card needed

thetapwareoutlet.com.au logo

thetapwareoutlet.com.au website review

Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 96 checks

This review found 47 issues worth fixing on thetapwareoutlet.com.au, 20 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. 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
1.1 s889 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026967 ms
May 23, 2026947 ms
May 30, 2026915 ms
Jun 6, 2026914 ms
Jun 13, 2026932 ms
Jun 20, 2026956 ms
Jun 27, 2026963 ms
Jul 4, 2026962 ms
Jul 11, 2026958 ms
Jul 18, 2026922 ms
Jul 25, 2026928 ms
Aug 1, 2026942 ms
Aug 8, 2026934 ms
Aug 15, 2026967 ms
Aug 22, 2026986 ms
Aug 29, 2026975 ms
Sep 5, 2026997 ms
Sep 12, 20261.0 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
87 ms78 msMay 16Oct 3183 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202680 ms
May 30, 202681 ms
Jun 6, 202683 ms
Jun 13, 202682 ms
Jun 20, 202684 ms
Jun 27, 202685 ms
Jul 4, 202685 ms
Jul 11, 202686 ms
Jul 18, 202683 ms
Jul 25, 202680 ms
Aug 1, 202680 ms
Aug 8, 202680 ms
Aug 15, 202681 ms
Aug 22, 202683 ms
Aug 29, 202682 ms
Sep 5, 202681 ms
Sep 12, 202682 ms
Sep 19, 202683 ms
Sep 26, 202682 ms
Oct 3, 202682 ms
Oct 10, 202681 ms
Oct 17, 202680 ms
Oct 24, 202681 ms
Oct 31, 202683 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 thetapwareoutlet.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thetapwareoutlet.com.au at 1.5 s1.5 s
  2. thetapwareoutlet.com.au at 3.0 s3.0 s
  3. thetapwareoutlet.com.au at 4.5 s4.5 s
  4. thetapwareoutlet.com.au at 6.0 s6.0 s
  5. thetapwareoutlet.com.au at 7.5 s7.5 s
  6. thetapwareoutlet.com.au at 9.0 s9.0 s
  7. thetapwareoutlet.com.au at 10.5 s10.5 s
  8. thetapwareoutlet.com.au at 12.0 s12.0 s

Speed

14 to fix35
  • Reduce unused JavaScript

    9.3 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.

  • YouTube adds 1.4 s

    1.4 s

    YouTube costs a phone 1.4 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 12.6 s

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

  • Mobile performance score: 35

    35/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, chatra.io and reputon.com and others), adding 3.5 MB and 3.1 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 1.1 MB

    35 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Improve image delivery

    50 ms · 1.1 MB

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

  • chatra.io adds 932 ms

    932 ms

    chatra.io costs a phone 932 ms of main-thread work and 386 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.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • reputon.com adds 275 ms

    275 ms

    reputon.com costs a phone 275 ms of main-thread work and 236 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,463 HTML elements

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

  • Shopify adds 206 ms

    206 ms

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

  • Heroku adds 51 ms

    51 ms

    Heroku costs a phone 51 ms of main-thread work and 413 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.

  • Legacy JavaScript

    150 ms · 37 KiB

    Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    161 KiB

    161 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

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

  • Reduce unused CSS

    97 KiB

    About 97 KiB of CSS is downloaded but never applied on this page.

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

    5 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

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

  • Time to Interactive: 34.8 s

    34.8 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user CLS: 0.14

    0.14

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

  • Cumulative Layout Shift: 0.148

    0.148

    The layout shifts by 0.148 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

    1 image 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-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 110 ms

    110 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 798 ms

    798 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

Images and page weight

4 to fix25
  • Page weight: 6.3 MB in 339 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 339 requests on a phone: scripts 3.6 MB (128), images 1.5 MB (35) and other files 718 KiB (143). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    8f88cb5db341c12a293812fb67eafb5c.png weighs 771 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    608 KiB

    1 image is downloaded at several times the size a phone draws it, for example 8f88cb5db341c12a293812fb67eafb5c.png at 1,829 px wide, shown at 280 px. Resized copies would save about 608 KiB.

  • 1 image in older formats

    1 image (771 KiB) is 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 1.8 g of CO₂ per visit

    1.79 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7587
  • 155 text elements with low contrast

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

  • Certain ARIA roles must be contained by particular parents (12 elements)

    Certain ARIA roles must be contained by particular parents: 12 elements on the page fail this check, rated critical by axe-core.

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

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 5 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 2 links without text

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

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is short (18 characters)

    Your title is only 18 characters: “The Tapware Outlet”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (57 characters)

    Your meta description is only 57 characters: “Australia's best range of bathroom tapware & accessories!”. 70 to 160 characters is enough to sell the click.

  • 225 internal links, 3 external

    The homepage links to 225 pages on thetapwareoutlet.com.au and 3 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “The Tapware Outlet”.

  • Canonical URL set

    The canonical URL is https://thetapwareoutlet.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://thetapwareoutlet.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 (1,436 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 11 pages without a meta description

    https://thetapwareoutlet.com.au/collections/antique-brass-range, https://thetapwareoutlet.com.au/collections/matt-black-range, https://thetapwareoutlet.com.au/collections/brushed-nickel-range, https://thetapwareoutlet.com.au/collections/gunmetal-range, https://thetapwareoutlet.com.au/collections/matt-white-range and https://thetapwareoutlet.com.au/collections/chrome-range and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 128 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

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

Best practices

2 to fixGoogle 7391
  • 16 small tap targets

    16 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

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

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,572 words of copy

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

  • Urgency cues

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

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Sign up”, “Contact Us” and “SHOP NOW”.

  • 2 short forms

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

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 13 cookies set on arrival

    13

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

  • 41 other companies contacted

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

Apps your storefront loads

App Salespop · stamped.io · chatra.io · reputon.com · herokuapp.com · nfcube.com · seasoneffects.com · hextom.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

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