theperfectcosmetics.com website review

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

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

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

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

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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.

Your homepage downloads 2.2 MB in 233 requests on a phone: scripts 714 KiB (87), other files 674 KiB (67) and images 660 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

6 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: 1 element on the page fails this check, rated minor by axe-core.

Your title is 83 characters, so Google will cut it off around 60: “The Perfect Cosmetics Company by Penny Lane – The Perfect Cosmetics Company Pty Ltd”.

There are 2 <h1> headlines (“” and “Real Results, Real People”). One clear main headline is easier for people and search engines.

The homepage links to 58 pages on theperfectcosmetics.com and 10 external pages.

https://theperfectcosmetics.com/collections/bundles and https://theperfectcosmetics.com/pages/gallery-of-before-and-afters have no meta description, so Google writes the search snippet from whatever text it finds.

https://theperfectcosmetics.com/collections/bundles, https://theperfectcosmetics.com/pages/our-story, https://theperfectcosmetics.com/pages/contact, https://theperfectcosmetics.com/pages/faqs and https://theperfectcosmetics.com/pages/gallery-of-before-and-afters have no <h1> headline, so visitors and search engines get no clear main topic.

https://theperfectcosmetics.com/collections/bundles has 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.

https://theperfectcosmetics.com/products/my-perfect-night took over 3 s to send its HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 521 words of visible text.

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.

Opening the homepage sets 18 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.