soupercubes.com website review

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

11 images could be 610 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 56. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (heatmap.com, rebuyengine.com and Klaviyo and others), adding 1.3 MB and 746 ms of main-thread time.

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

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

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

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

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

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

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

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.

Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mashed sweet potatoes portioned into two green Souper Cubes…”.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 350 requests on a phone: other files 1.3 MB (210), scripts 1.1 MB (85) and images 840 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

There are 2 <h1> headlines (“Souper Cubes®” and “Prep now. Enjoy later.”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 60 pages on soupercubes.com and 9 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.

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

https://www.soupercubes.com/collections/all and https://www.soupercubes.com/products/gift-card have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.soupercubes.com/pages/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).

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

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