Website review, no card needed

hydropeptide.au logo

hydropeptide.au website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 78 checks

This review found 31 issues worth fixing on hydropeptide.au, 10 of them high impact, across 78 checks. The most urgent: 5,653 HTML elements. 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 hydropeptide.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hydropeptide.au at 0.9 s0.9 s
  2. hydropeptide.au at 1.8 s1.8 s
  3. hydropeptide.au at 2.6 s2.6 s
  4. hydropeptide.au at 3.5 s3.5 s
  5. hydropeptide.au at 4.4 s4.4 s
  6. hydropeptide.au at 5.3 s5.3 s
  7. hydropeptide.au at 6.1 s6.1 s
  8. hydropeptide.au at 7.0 s7.0 s

Speed

7 to fix66
  • 5,653 HTML elements

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

  • Main-thread work: 4.4 s

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

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. 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 (Klaviyo, Google Tag Manager and cloudfront.net and others), adding 1.3 MB and 472 ms of main-thread time.

  • Reduce unused JavaScript

    387 KiB

    About 387 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    260 KiB

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

  • Klaviyo adds 128 ms

    128 ms

    Klaviyo costs a phone 128 ms of main-thread work and 417 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.

  • 7 long tasks on the main thread

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

  • Improve image delivery

    88 KiB

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

  • Legacy JavaScript

    47 KiB

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

  • Reduce unused CSS

    13 KiB

    About 13 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: 28 ms

    28 ms

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

Core Web Vitals

6 to fix65
  • Time to Interactive: 18.3 s

    18.3 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Total Blocking Time: 274 ms

    274 ms

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

  • 5 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix64
  • Page weight: 4.1 MB in 347 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 347 requests on a phone: scripts 1.4 MB (87), images 1.1 MB (35) and other files 951 KiB (195). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HP-Web-2025-Holiday-Navigation-Image-Retail_600x.webp 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).

  • 1 image in older formats

    1 image (38 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.2 g of CO₂ per visit

    1.17 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9088
  • 7 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Interactive controls must not be nested (6 elements)

    Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • ARIA role should be appropriate for the element (59 elements)

    ARIA role should be appropriate for the element: 59 elements on the page fail this check, rated minor by axe-core.

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 169 images in the HTML carry an alt attribute.

  • 46 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: 46 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 9289
  • No structured data

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

  • 25 links with vague text

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

  • Meta description is long (240 characters)

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

  • 238 internal links, 2 external

    The homepage links to 238 pages on hydropeptide.au and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “HydroPeptide Australia”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “HydroPeptide Australian Official Site | Luxury Anti-Aging”.

  • Canonical URL set

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

  • llms.txt published

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

Other pages

100
  • 2 pages slow to respond

    https://www.hydropeptide.au/collections/cleansers-toners and https://www.hydropeptide.au/collections/exfoliators-masks took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “this.forceOkendoRefresh is not a function”.

2 checks passed
  • Tap targets are thumb-sized

    66 of 82 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 3 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.

  • About 2,739 words of copy

    The homepage carries about 2,739 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

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

  • 20 calls to action

    The homepage has 20 calls to action, for example “SHOP”, “SHOP BY CONCERN” and “SHOP BY CATEGORY”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • 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
  • 5 trackers load before any consent

    5

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

  • 16 cookies set on arrival

    16

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 hydropeptide.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

Okendo · Klaviyo Email Marketing Sms · Dr Free Gift · Accentuate · Event Promotion Bar · Store Locator · Selleasy · Page Speed Optimizer · roseperl.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
Vue.js
E-commerce
Shopify
Analytics
Google Analytics
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 hydropeptide.au, including 13 speed issues, 3 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