exabeauty.com website review

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.1 s faster on a phone.

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

moonshot-ai.com costs a phone 2.4 s of main-thread work and 62 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (moonshot-ai.com, Google Tag Manager and gotolstoy.com and others), adding 3.2 MB and 4.4 s of main-thread time.

Google Tag Manager costs a phone 693 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.

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

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

5 images could be 429 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.

gotolstoy.com costs a phone 457 ms of main-thread work and 458 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.

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

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

Yotpo costs a phone 280 ms of main-thread work and 426 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 costs a phone 218 ms of main-thread work and 904 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

38 KiB could be saved by minifying JavaScript.

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.

5 KiB could be saved by minifying CSS.

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.

Your largest element takes 34.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Want 10% off? YES, PLEASE No thanks, I’ll pay full price ✕”.

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

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

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

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

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

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

Your homepage downloads 7.8 MB in 565 requests on a phone: scripts 3.9 MB (155), other files 1.4 MB (239) and images 1.2 MB (82). Under 2 MB keeps phones on slow connections fast.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

38 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

[aria-*] attributes are not valid or misspelled (1 element).

Document should not have more than one banner landmark: 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.

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

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

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

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

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.

5 links have no real href, so search engines can't follow them.

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

The homepage links to 782 pages on exabeauty.com and 14 external pages.

https://credobeauty.com/pages/services and https://credobeauty.com/collections/sun-care-bestsellers have no meta description, so Google writes the search snippet from whatever text it finds.

https://credobeauty.com/pages/refer-a-friend, https://credobeauty.com/pages/services, https://credobeauty.com/collections/makeup-bestsellers, https://credobeauty.com/collections/hair-bestsellers and https://credobeauty.com/collections/sun-care-bestsellers have no <h1> headline, so visitors and search engines get no clear main topic.

https://credobeauty.com/collections/sun-care-bestsellers took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://assets.tapcart.com/app-config/J9oM5ibd7W_67d8905518995b556bc6298a.jpg.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 791 words of visible text.

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