bigwax.io website review

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

8 third-party services load with your homepage (Framer CDN, cdn-cookieyes.com and Shopify and others), adding 3.2 MB and 812 ms of main-thread time.

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

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

Framer CDN costs a phone 411 ms of main-thread work and 2.9 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.

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

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

cdn-cookieyes.com costs a phone 291 ms of main-thread work and 39 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.

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

About 174 KiB of JavaScript is downloaded but never used on this page.

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

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

Polyfills for old browsers add 11 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.

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 JavaScript.

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Borga Revolution Ghanaian Music In The Digital Age - 1979 -…”.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 341 requests on a phone: images 3.0 MB (38), other files 1,013 KiB (156) and scripts 800 KiB (133). Under 2 MB keeps phones on slow connections fast.

1 image (115 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.

1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

14 elements use ARIA attributes their role does not allow, which confuses screen readers.

95 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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 meta description is 247 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 202 pages on bigwax.io and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://miniwax.club/fr-us/collections/op-limited-offer and https://miniwax.club/fr-us/collections/merch-limited-offer all use the title “Promotions – Miniwax”. Search engines can't tell which page to show for a search, so each competes with the others.

https://miniwax.club/fr-us/collections/genre-electronic, https://miniwax.club/fr-us/collections/genre-groove, https://miniwax.club/fr-us/collections/genre-jazz, https://miniwax.club/fr-us/collections/genre-reggae-dub, https://miniwax.club/fr-us/collections/genre-hip-hop and https://miniwax.club/fr-us/collections/genre-alternative and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://miniwax.club/fr-us/collections/genre-electronic, https://miniwax.club/fr-us/collections/genre-groove, https://miniwax.club/fr-us/collections/genre-jazz, https://miniwax.club/fr-us/collections/genre-reggae-dub, https://miniwax.club/fr-us/collections/genre-hip-hop and https://miniwax.club/fr-us/collections/genre-alternative and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “GorgiasChat is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 922 words of visible text.

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

Opening the homepage sets 5 cookies (measured from a US location before any click).

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