Website review, no card needed

buzzpatch.com.au logo

buzzpatch.com.au website review

Visit site (opens in a new tab)Reviewed 16 November 202642 issues · 90 checks

This review found 42 issues worth fixing on buzzpatch.com.au, 18 of them high impact, across 90 checks. The most urgent: render-blocking 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
3.1 s2.4 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Oct 31, 20263.0 s
Nov 7, 20263.0 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
295 ms168 msMay 30Nov 14272 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026188 ms
Jun 6, 2026183 ms
Jun 13, 2026185 ms
Jun 20, 2026192 ms
Jun 27, 2026203 ms
Jul 4, 2026214 ms
Jul 11, 2026221 ms
Jul 18, 2026226 ms
Jul 25, 2026229 ms
Aug 1, 2026229 ms
Aug 8, 2026231 ms
Aug 15, 2026244 ms
Aug 22, 2026249 ms
Aug 29, 2026258 ms
Sep 5, 2026258 ms
Sep 12, 2026256 ms
Sep 19, 2026256 ms
Sep 26, 2026257 ms
Oct 3, 2026261 ms
Oct 10, 2026271 ms
Oct 17, 2026275 ms
Oct 24, 2026278 ms
Oct 31, 2026280 ms
Nov 7, 2026273 ms
Nov 14, 2026272 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 buzzpatch.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. buzzpatch.com.au at 1.1 s1.1 s
  2. buzzpatch.com.au at 2.3 s2.3 s
  3. buzzpatch.com.au at 3.4 s3.4 s
  4. buzzpatch.com.au at 4.5 s4.5 s
  5. buzzpatch.com.au at 5.6 s5.6 s
  6. buzzpatch.com.au at 6.8 s6.8 s
  7. buzzpatch.com.au at 7.9 s7.9 s
  8. buzzpatch.com.au at 9.0 s9.0 s

Speed

12 to fix45
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 10.1 s

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

  • 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,288 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Clarity and others), adding 2.4 MB and 2.0 s of main-thread time.

  • Improve image delivery

    800 ms · 1.4 MB

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

  • Use efficient cache lifetimes

    200 ms · 893 KiB

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

  • Reduce unused JavaScript

    150 ms · 664 KiB

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

  • Google Tag Manager adds 593 ms

    593 ms

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

  • alia-prod.com adds 382 ms

    382 ms

    alia-prod.com costs a phone 382 ms of main-thread work and 568 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.

  • Klaviyo adds 211 ms

    211 ms

    Klaviyo costs a phone 211 ms of main-thread work and 615 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 183 ms

    183 ms

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

  • 16 long tasks on the main thread

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

  • Legacy JavaScript

    40 KiB

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

  • Reduce unused CSS

    37 KiB

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

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 82 ms

    82 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Time to Interactive: 30.5 s

    30.5 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Total Blocking Time: 650 ms

    650 ms

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

  • 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: 2.8 s

    2.8 s

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

  • Real-user INP: 324 ms

    324 ms

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

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

    +47%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 33 images without width and height

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0.028

    0.028

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

Images and page weight

2 to fix50
  • Page weight: 7.9 MB in 600 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 600 requests on a phone: images 2.7 MB (108), scripts 2.4 MB (167) and other files 1.8 MB (243). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    536 KiB

    2 images are downloaded at several times the size a phone draws them, for example natpat-mosquito-protection-patches-for-kids-safe-easy-to-use at 1,841 px wide, shown at 44 px. Resized copies would save about 536 KiB.

  • 2 images below the first screen load straight away

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

  • About 2.2 g of CO₂ per visit

    2.24 g

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

6 to fixGoogle 8190
  • 62 buttons without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 13 text elements with low contrast

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

  • 9 tap targets too small

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 82 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 90 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 6 H1 headlines

    There are 6 <h1> headlines (“Born inAustralia”, “12-hour bite defence. No DEET. No spray battle.” and “Peel. Stick. Sleep.”). One clear main headline is easier for people and search engines.

  • 5 links with vague text

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

  • 157 internal links, 20 external

    The homepage links to 157 pages on buzzpatch.com.au and 20 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Elevate your health journey with innovative Health and Wellness Stickers. Experience a holistic boost for vitality and …”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “NATPAT Health and Wellness Patches: Your Path to Wellbeing”.

  • Canonical URL set

    The canonical URL is https://www.natpat.com/.

  • 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://www.natpat.com/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 (2,905 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 4 linked pages hidden from search

    https://www.natpat.com/collections/bundles, https://www.natpat.com/pages/community, https://www.natpat.com/pages/science and https://www.natpat.com/pages/natpat-reviews are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.natpat.com/pages/bundle-builder, https://www.natpat.com/pages/awards, https://www.natpat.com/pages/science and https://www.natpat.com/pages/natpat-reviews have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://www.natpat.com/pages/community took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=52011094&tm=gtm002&Ver=2&mid=18a1b16d-69ac-4d01-b76d-cb1d822ea07e&bo=1&sid=7a4d1ec0e1e911f1b7bb27dc3013c2ba&vid=7a54ad40e1e911f1a96b7fbfaeebb444&vids=1&msclkid=N&gtm_t.

  • 15 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 1,658 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP SLEEPYPATCH”.

  • 30 calls to action

    The homepage has 30 calls to action, for example “Shop”, “Shop All” and “Where to Buy”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks, a star rating, 1 trust badge and “100,000+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 12 trackers load before any consent

    12

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 7 mores (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.

  • 38 cookies set on arrival

    38

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

  • 70 other companies contacted

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

Apps your storefront loads

Blotout Edgetag · Intelligems A B Testing · Sitemap Noindex Pro Seo · Layerkick For Natpat · Np Datalayer · Klaviyo Email Marketing Sms · Judge Me Reviews · Icart Cart Upsell · Smart Seo · Klickly Connector · Np Cart Tiers · provesrc.com · elfsight.com · amazonaws.com · cloudfront.net · socialsnowball.io · identixweb.com · goaffpro.com · onetext.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 | 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 42 issues on buzzpatch.com.au, including 24 speed issues, 2 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