beautyfrontier.com website review

18 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

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

485 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 2.1 s faster on a phone.

8 third-party services load with your homepage (route.com, Clarity and Accessibe Accessibility Overlay and others), adding 1.5 MB and 968 ms of main-thread time.

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

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

route.com costs a phone 632 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.

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

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

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

1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

3 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Introducing Eau d'Italie Acqua di Positano Candle. Escape t…”.

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

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

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

The first text or image appears after 2.0 s on a phone. Good is under 1.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 3.3 MB in 230 requests on a phone: scripts 1.8 MB (59), other files 880 KiB (143) and images 301 KiB (12). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example EDI_liquidsoap_lotion_oct2023_2000px.jpg at 2,000 px wide, shown at 358 px. Resized copies would save about 88 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 29 characters: “Beauty Frontier Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 70 pages on beautyfrontier.com and 4 external pages.

https://beautyfrontier.com/collections/altaia-fragrances and https://beautyfrontier.com/collections/fragrances all use the title “ALTAIA – Beauty Frontier”. Search engines can't tell which page to show for a search, so each competes with the others.

https://beautyfrontier.com/collections/ligne-st-barth has no meta description, so Google writes the search snippet from whatever text it finds.

https://beautyfrontier.com/collections/altaia-fragrances and https://beautyfrontier.com/collections/fragrances use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://beautyfrontier.com/collections/fragrances, whose canonical is https://beautyfrontier.com/collections/altaia-fragrances. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://beautyfrontier.com/pages/altaia and https://beautyfrontier.com/pages/eau-d-italie have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 323 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 14 cookies (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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.