Website review, no card needed

dermavive.com.au logo

dermavive.com.au website review

Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 87 checks

This review found 37 issues worth fixing on dermavive.com.au, 12 of them high impact, across 87 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
2.3 s1.7 sJun 13Oct 32.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
207 ms155 msJun 27Oct 3201 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 2026161 ms
Sep 12, 2026189 ms
Sep 19, 2026195 ms
Sep 26, 2026201 ms
Oct 3, 2026201 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 dermavive.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dermavive.com.au at 0.7 s0.7 s
  2. dermavive.com.au at 1.3 s1.3 s
  3. dermavive.com.au at 2.0 s2.0 s
  4. dermavive.com.au at 2.6 s2.6 s
  5. dermavive.com.au at 3.3 s3.3 s
  6. dermavive.com.au at 3.9 s3.9 s
  7. dermavive.com.au at 4.6 s4.6 s
  8. dermavive.com.au at 5.3 s5.3 s

Speed

11 to fix58
  • Reduce unused JavaScript

    4.7 s · 827 KiB

    About 827 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Use efficient cache lifetimes

    2.5 s · 377 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 58

    58/100

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

  • Improve image delivery

    550 ms · 365 KiB

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

  • Reduce unused CSS

    600 ms · 81 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Clarity and octaneai.com and others), adding 1.9 MB and 478 ms of main-thread time.

  • Main-thread work: 3.2 s

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

  • 2,769 HTML elements

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

  • Klaviyo adds 199 ms

    199 ms

    Klaviyo costs a phone 199 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 52 ms

    52 ms

    Shopify costs a phone 52 ms of main-thread work and 535 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

    250 ms · 40 KiB

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

  • 6 long tasks on the main thread

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 21.0 s

    21.0 s

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

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

    +15%

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

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

    +15%

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

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

2 checks passed
  • Total Blocking Time: 77 ms

    77 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix60
  • Page weight: 4.1 MB in 263 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 263 requests on a phone: scripts 1.8 MB (99), images 1.0 MB (30) and other files 803 KiB (115). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Mobile_Banner_5.png 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).

  • 14 images in older formats

    14 images (783 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.

  • 3 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.15 g

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

10 to fixGoogle 8588
  • Scrollable region must have keyboard access (5 elements)

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

  • 5 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 29 images without alt text

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • 17 links without text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 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 8591
  • Structured data has 2 problems

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//au.neutriderm.com/cdn/shop/files/Neutriderm_Logo_256x…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • 119 internal links, 9 external

    The homepage links to 119 pages on dermavive.com.au and 9 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Discover Neutriderm’s range of dermatologist-recommended skin and hair care products. Enjoy free shipping on orders ove…”.

  • One H1 headline

    Your main headline reads: “Neutriderm: Our Story, Our Promise”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Dermatologist-Recommend Skin & Hair Care Products | Neutriderm”.

  • Canonical URL set

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

  • 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://au.neutriderm.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://au.neutriderm.com/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.

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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 4 pages without an H1

    https://au.neutriderm.com/collections/all-products, https://au.neutriderm.com/collections/bundles, https://au.neutriderm.com/collections/new-products and https://au.neutriderm.com/collections/best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9693
  • 7 small tap targets

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

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

3 to fix81
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

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

    The homepage carries about 795 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ALL” and “SUBSCRIBE & SAVE HERE”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop All”, “Shop” and “Best Sellers Shop Now”.

  • 13 short forms

    13 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 50 testimonial or review blocks, 6 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 20 cookies set on arrival

    20

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 dermavive.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

Tolstoy · Judge Me Reviews · Simprosys Google Shopping Feed · Eg Auto Add To Cart · Microsoft Clarity · Ez Ai Seo Optimizer · Upsell Kit · Klaviyo Email Marketing Sms · Forms · Essential Post Purchase Upsell · octaneai.com · instant.one

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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
WHG Hosting Services Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on dermavive.com.au, including 15 speed issues, 3 SEO issues and 3 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