Website review, no card needed

quickchangewraps.com.au logo

quickchangewraps.com.au website review

Visit site (opens in a new tab)Reviewed 11 November 202627 issues · 71 checks

This review found 27 issues worth fixing on quickchangewraps.com.au, 7 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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 quickchangewraps.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. quickchangewraps.com.au at 0.4 s0.4 s
  2. quickchangewraps.com.au at 0.8 s0.8 s
  3. quickchangewraps.com.au at 1.3 s1.3 s
  4. quickchangewraps.com.au at 1.7 s1.7 s
  5. quickchangewraps.com.au at 2.1 s2.1 s
  6. quickchangewraps.com.au at 2.5 s2.5 s
  7. quickchangewraps.com.au at 2.9 s2.9 s
  8. quickchangewraps.com.au at 3.3 s3.3 s

Speed

5 to fix72
  • Use efficient cache lifetimes

    1.2 s · 404 KiB

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

  • Font display

    1.0 s

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

  • Mobile performance score: 72

    72/100

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

  • Improve image delivery

    600 ms · 341 KiB

    12 images could be 341 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    150 ms · 173 KiB

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

  • Legacy JavaScript

    200 ms · 29 KiB

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

  • Reduce unused CSS

    150 ms · 29 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, 9gtb.com and Yotpo and others), adding 247 KiB and 71 ms of main-thread time.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix68
  • Largest Contentful Paint: 7.3 s

    7.3 s

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

    10.8 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • 17 images without width and height

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

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

3 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 14 ms

    14 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.0 MB in 99 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 99 requests on a phone: other files 745 KiB (26), images 609 KiB (19) and scripts 524 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    55 KiB

    2 images are downloaded at several times the size a phone draws them, for example logo-dh.png at 600 px wide, shown at 150 px. Resized copies would save about 55 KiB.

  • 4 images in older formats

    4 images (245 KiB) 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.

  • 4 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.57 g

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

Accessibility

4 to fixGoogle 9195
  • 23 text elements with low contrast

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 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 9281
  • Title is long (105 characters)

    Your title is 105 characters, so Google will cut it off around 60: “QuickChange Maximum Absorbency Wrap for Male Incontinence – QuickChange Men's Incontinenc…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “QUICKCHANGE®”). One clear main headline is easier for people and search engines.

  • Meta description is long (285 characters)

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

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

  • 53 internal links, 5 external

    The homepage links to 53 pages on quickchangewraps.com.au and 5 external pages.

5 checks passed
  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://quickchangewraps.com.au/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

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

Other pages

4 to fix41
  • 1 linked page is broken

    Your homepage links to https://quickchangewraps.com.au/blogs/news, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a title

    https://quickchangewraps.com.au/products/quickchange-male-incontinence-wrap-maximum-absorbency-1-size-10-count-trial-pack, https://quickchangewraps.com.au/products/quickchange-mens-incontinence-wrap-maximum-absorbency-one-size-100-count, https://quickchangewraps.com.au/pages/professional, https://quickchangewraps.com.au/pages/clinical-studies, https://quickchangewraps.com.au/pages/professional-use-sample-pack and https://quickchangewraps.com.au/pages/how-to-use and 8 others have no <title>, so Google invents the link text in results.

  • 14 pages without a meta description

    https://quickchangewraps.com.au/products/quickchange-male-incontinence-wrap-maximum-absorbency-1-size-10-count-trial-pack, https://quickchangewraps.com.au/products/quickchange-mens-incontinence-wrap-maximum-absorbency-one-size-100-count, https://quickchangewraps.com.au/pages/professional, https://quickchangewraps.com.au/pages/clinical-studies, https://quickchangewraps.com.au/pages/professional-use-sample-pack and https://quickchangewraps.com.au/pages/how-to-use and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://quickchangewraps.com.au/products/quickchange-male-incontinence-wrap-maximum-absorbency-1-size-10-count-trial-pack, https://quickchangewraps.com.au/products/quickchange-mens-incontinence-wrap-maximum-absorbency-one-size-100-count, https://quickchangewraps.com.au/pages/professional, https://quickchangewraps.com.au/pages/clinical-studies, https://quickchangewraps.com.au/pages/professional-use-sample-pack and https://quickchangewraps.com.au/pages/how-to-use and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://quickchangewraps.com.au/products/quickchange-male-incontinence-wrap-maximum-absorbency-1-size-10-count-trial-pack, https://quickchangewraps.com.au/products/quickchange-mens-incontinence-wrap-maximum-absorbency-one-size-100-count, https://quickchangewraps.com.au/pages/professional, https://quickchangewraps.com.au/pages/clinical-studies, https://quickchangewraps.com.au/pages/professional-use-sample-pack and https://quickchangewraps.com.au/pages/how-to-use 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.

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • Thin social proof

    Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 627 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Trial 10-Pack”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy Now”, “Request a Sample Pack” and “Order Status”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 1 cookie set on arrival

    1

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 quickchangewraps.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

Consentmo Gdpr · Yotpo Product Reviews Ugc · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Hulk Form Builder · Triplewhale · shopifyapps.com · googleapis.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

  • The footer still says © 2025.

Stack

E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on quickchangewraps.com.au, including 9 speed issues, 4 SEO issues and 1 conversion gap. 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