waxwax.com website review

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

Clarity costs a phone 1.0 s of main-thread work and 31 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.

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

8 third-party services load with your homepage (Clarity, Google Tag Manager and Klaviyo and others), adding 3.1 MB and 2.3 s of main-thread time.

About 1.0 MB of JavaScript is downloaded but never used on this page.

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

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

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

Google Tag Manager costs a phone 418 ms of main-thread work and 700 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.

rebuyengine.com costs a phone 200 ms of main-thread work and 723 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.

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

Klaviyo costs a phone 213 ms of main-thread work and 368 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 102 ms of main-thread work and 504 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.

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

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

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

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

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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stop compromising between a smooth finish and calm skin. Ou…”. Most of its time is element render delay (2.6 s).

1 image 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' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.7 MB in 647 requests on a phone: media 7.6 MB (1), scripts 3.1 MB (193) and other files 1.6 MB (320). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example hard-wax-beads-white-raw-2-5-lb-pouch-front_400x400.webp at 400 px wide, shown at 68 px. Resized copies would save about 102 KiB.

1 image (139 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (42 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 3.88 g of CO₂e: 465.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 3 <h1> headlines (“”, “The #1 Specialist Hard Wax For Sensitive Skin” and “Find Your Perfect Waxing Solution”). One clear main headline is easier for people and search engines.

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 100 pages on waxwax.com and 23 external pages.

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

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

https://www.waxwax.com/pages/bulk and https://www.waxwax.com/collections/bulk-wax all use the title “Bulk Wax – WAX WAX”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.waxwax.com/collections/all, https://www.waxwax.com/customer_authentication/redirect, https://www.waxwax.com/policies/shipping-policy, https://www.waxwax.com/pages/bulk, https://www.waxwax.com/pages/pro-account-guide and https://www.waxwax.com/collections/bulk-wax 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.waxwax.com/pages/bulk, whose canonical is https://www.waxwax.com/collections/bulk-wax. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.waxwax.com/collections/all, https://www.waxwax.com/customer_authentication/redirect, https://www.waxwax.com/pages/waxing-products, https://www.waxwax.com/collections/hard-wax, https://www.waxwax.com/collections/waxing-kits and https://www.waxwax.com/collections/waxing-supplies and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 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 1,573 words of visible text.

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