cakebeauty.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Other Google APIs/SDKs and Bazaarvoice and others), adding 1.3 MB and 494 ms of main-thread time.

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

Shopify costs a phone 86 ms of main-thread work and 358 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.

1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.

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

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 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

18 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.5 MB in 330 requests on a phone: scripts 1.3 MB (137), images 986 KiB (35) and other files 850 KiB (129). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example TheBigWigVolumizingMousse238gBI_823168005843_3_In-Use_1024x1 at 1,024 px wide, shown at 330 px. Resized copies would save about 236 KiB.

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

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

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 50 pages on cakebeauty.com and 11 external pages.

Your homepage links to https://www.cakebeauty.com/apps/iwish, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.cakebeauty.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.cakebeauty.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.cakebeauty.com/customer_authentication/redirect, https://www.cakebeauty.com/collections/new-hair-products, https://www.cakebeauty.com/collections/hair, https://www.cakebeauty.com/collections/hair-travel-size, https://www.cakebeauty.com/collections/shampoo-conditioner and https://www.cakebeauty.com/collections/treatments and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://www.cakebeauty.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.cakebeauty.com/collections/hair-travel-size, https://www.cakebeauty.com/collections/treatments and https://www.cakebeauty.com/collections/body-travel-size have 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.

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

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.cakebeauty.com/cdn/shop/t/156/assets/powerreviews.css?v=5378' because its MIME…”.

2 images are served at too low a resolution for sharp phone screens.

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

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

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 99 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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