bigassluxuries.com website review

40 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Klaviyo, loox.io and Google Tag Manager and others), adding 1.5 MB and 1.0 s of main-thread time.

About 419 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

Klaviyo costs a phone 320 ms of main-thread work and 694 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.

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

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

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

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

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

Your largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

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

The first text or image appears after 2.6 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 145 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.8 MB in 440 requests on a phone: media 5.8 MB (3), images 3.6 MB (112) and scripts 1.7 MB (180). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

There are 2 <h1> headlines (“Gift Big This Season” and “Gift Big This Season”). One clear main headline is easier for people and search engines.

The homepage links to 307 pages on bigassluxuries.com and 4 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://bigassluxuries.com/collections/holiday-collection, https://bigassluxuries.com/collections/big-ass-candle-holders and https://bigassluxuries.com/collections/signature-scents have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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.

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

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.