belleattheball.com website review

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Judge.me and others), adding 1.1 MB and 1.0 s of main-thread time.

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

Shopify costs a phone 373 ms of main-thread work and 629 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 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

10 KiB could be saved by minifying JavaScript.

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

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

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

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

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

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SHOP NOW”.

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

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

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

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

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

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.7 MB in 225 requests on a phone: scripts 1.3 MB (67), other files 842 KiB (129) and images 381 KiB (18). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.0 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.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://belleattheball.com{{ routes.search…”.

The homepage links to 33 pages on belleattheball.com and 2 external pages.

https://belleattheball.com/collections/nailspark%E2%84%A2, https://belleattheball.com/collections/daily-protection and https://belleattheball.com/collections/winter-essentials have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://belleattheball.com/collections/nailspark%E2%84%A2, whose canonical is https://belleattheball.com/collections/nailspark%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

11 errors were logged to the browser console during Google's test (“Access to XMLHttpRequest at 'chrome-extension://epcpfbncpjfomakgdophbanbkdeonkhc/img/logo.svg' from…”).

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

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

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

The homepage carries about 373 words of visible text.