shopbeamazing.com website review

127 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.5 s faster on a phone.

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

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

Signyfyd costs a phone 1.1 s of main-thread work and 281 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.

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

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

8 third-party services load with your homepage (Signyfyd, alia-prod.com and JSDelivr CDN and others), adding 7.6 MB and 3.0 s of main-thread time.

28 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

Kaltura Video Platform costs a phone 232 ms of main-thread work and 4.6 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.

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

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

alia-prod.com costs a phone 492 ms of main-thread work and 656 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 241 ms of main-thread work and 916 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.

JSDelivr CDN costs a phone 329 ms of main-thread work and 15 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.

13 KiB could be saved by minifying JavaScript.

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

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

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 73.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

14 images 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.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.3 MB in 778 requests on a phone: images 10.1 MB (174), scripts 3.5 MB (182) and other files 1.7 MB (341). Under 2 MB keeps phones on slow connections fast.

Gym_Candid.jpg weighs 1.5 MB. On a phone connection a single image that size takes seconds.

4 images (2.2 MB) are 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.

4 images are downloaded at several times the size a phone draws them, for example Dole_Final.jpg at 1,000 px wide, shown at 272 px. Resized copies would save about 229 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Your <h1> is empty.

The homepage links to 284 pages on shopbeamazing.com and 39 external pages.

https://shopbeamazing.com/products/beam-be-amazing-vegan-plant-based-protein-powder-supplement and https://shopbeamazing.com/products/beam-vegan-protein-powder-supplement all use the title “Be Amazing Premium vegan protein Powder Supplement l plant based prot…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shopbeamazing.com/collections/all and https://shopbeamazing.com/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.

https://shopbeamazing.com/products/beam-be-amazing-vegan-plant-based-protein-powder-supplement and https://shopbeamazing.com/products/beam-vegan-protein-powder-supplement use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shopbeamazing.com/products/beam-vegan-protein-powder-supplement, whose canonical is https://shopbeamazing.com/products/beam-be-amazing-vegan-plant-based-protein-powder-supplement. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shopbeamazing.com/products/beam-be-amazing-vegan-plant-based-protein-powder-supplement, https://shopbeamazing.com/products/beam-vegan-protein-powder-supplement and https://shopbeamazing.com/pages/about have no <h1> headline, so visitors and search engines get no clear main topic.

https://shopbeamazing.com/products/beam-be-amazing-vegan-plant-based-protein-powder-supplement has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://shopbeamazing.com/collections/merch, https://shopbeamazing.com/collections/be-amazing-x-ihop, https://shopbeamazing.com/collections/be-amazing-x-dole and https://shopbeamazing.com/collections/be-amazing-x-sunny-d took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://shopbeamazing.com/.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: 6 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 929 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 52 cookies, 1 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 76 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.