Website review, no card needed

activeskin.com.au logo

activeskin.com.au website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 83 checks

This review found 38 issues worth fixing on activeskin.com.au, 16 of them high impact, across 83 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.5 s2.3 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
147 ms108 msMay 9Oct 24127 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026133 ms
May 23, 2026116 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026114 ms
Jul 4, 2026114 ms
Jul 11, 2026113 ms
Jul 18, 2026112 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026113 ms
Aug 22, 2026114 ms
Aug 29, 2026113 ms
Sep 5, 2026118 ms
Sep 12, 2026116 ms
Sep 19, 2026114 ms
Sep 26, 2026120 ms
Oct 3, 2026120 ms
Oct 10, 2026121 ms
Oct 17, 2026123 ms
Oct 24, 2026127 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 activeskin.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. activeskin.com.au at 0.8 s0.8 s
  2. activeskin.com.au at 1.6 s1.6 s
  3. activeskin.com.au at 2.4 s2.4 s
  4. activeskin.com.au at 3.2 s3.2 s
  5. activeskin.com.au at 4.0 s4.0 s
  6. activeskin.com.au at 4.9 s4.9 s
  7. activeskin.com.au at 5.7 s5.7 s
  8. activeskin.com.au at 6.5 s6.5 s

Speed

13 to fix17
  • Reduce unused JavaScript

    4.5 s · 1,013 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 293 KiB

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

  • Mobile performance score: 17

    17/100

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

  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google CDN and others), adding 3.2 MB and 1.6 s of main-thread time.

  • Render-blocking requests

    600 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.

  • Google Tag Manager adds 463 ms

    463 ms

    Google Tag Manager costs a phone 463 ms of main-thread work and 1.1 MB 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

    450 ms · 28 KiB

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

  • Google CDN adds 331 ms

    331 ms

    Google CDN costs a phone 331 ms of main-thread work and 996 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.

  • Other Google APIs/SDKs adds 370 ms

    370 ms

    Other Google APIs/SDKs costs a phone 370 ms of main-thread work and 348 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.

  • Facebook adds 246 ms

    246 ms

    Facebook costs a phone 246 ms of main-thread work and 460 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 266 ms. During a long task the page ignores taps.

  • 2,563 HTML elements

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

  • Reduce unused CSS

    37 KiB

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 43 ms

    43 ms

    Your server sent the HTML in 43 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.

  • Real-user CLS: 1.08

    1.08

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

  • Largest Contentful Paint: 20.1 s

    20.1 s

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

  • Time to Interactive: 27.4 s

    27.4 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • Cumulative Layout Shift: 0.874

    0.874

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 137 ms

    137 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 544 ms

    544 ms

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

Images and page weight

2 to fix64
  • Page weight: 4.6 MB in 195 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 195 requests on a phone: scripts 2.3 MB (73), other files 1.9 MB (92) and images 232 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • About 1.3 g of CO₂ per visit

    1.30 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8092
  • Hidden but focusable

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

  • 2 text elements with low contrast

    2 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 (3 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 13 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 80 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • Structured data has 2 problems

    Structured data found (ItemList and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • 530 internal links, 8 external

    The homepage links to 530 pages on activeskin.com.au and 8 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Activeskin is Australia's destination for all your favourite cosmetics online. Shop now pay later with Afterpay. Free D…”.

  • One H1 headline

    Your main headline reads: “Australia's Premium Online Beauty Destination”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Activeskin | Beauty Products & Cosmetics Online | We love beauty!”.

  • Canonical URL set

    The canonical URL is https://www.activeskin.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://www.activeskin.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.

  • No llms.txt

    There is no https://www.activeskin.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.

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

Other pages

1 to fix95
  • 11 pages without an H1

    https://www.activeskin.com.au/gifts/christmas, https://www.activeskin.com.au/brands/omnilux, https://www.activeskin.com.au/brands/medik8, https://www.activeskin.com.au/brands/dermalogica, https://www.activeskin.com.au/brands/skinceuticals and https://www.activeskin.com.au/brands/asap and 5 others 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 188 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5318342&Ver=2&mid=d82d4605-81b3-4dbd-9ffd-18223ad8f98c&bo=1&sid=a42de370d54d11f194e9e128595690be&vid=a42e0b30d54d11f1ac75fb8451ca20e1&vids=1&msclkid=N&pi=918639831&lg=.

  • 20 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 281 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 15 calls to action

    The homepage has 15 calls to action, for example “subscribe”, “SHOP NOW” and “Contact Us”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 activeskin.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Gatsby
Analytics
Google Analytics
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on activeskin.com.au, including 21 speed issues, 1 SEO issue 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