marssupplements.com website review

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

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

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

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

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

Clarity costs a phone 442 ms of main-thread work and 31 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 354 ms of main-thread work and 890 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.

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

Google Tag Manager costs a phone 226 ms of main-thread work and 429 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 long tasks block the main thread while loading, the longest for 176 ms. During a long task the page ignores taps.

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

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

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

10 KiB could be saved by minifying JavaScript.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 99 ms to 135 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.0 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The layout shifts by 0.15 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.7 MB in 451 requests on a phone: other files 1.7 MB (297), scripts 1.5 MB (84) and images 289 KiB (51). Under 2 MB keeps phones on slow connections fast.

3 images (102 KiB) 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.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

There are 5 <h1> headlines (“”, “” and “Power & Energy Products”). One clear main headline is easier for people and search engines.

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

The homepage links to 74 pages on marssupplements.com and 7 external pages.

https://marssupplements.com/collections/bundles, https://marssupplements.com/collections/weight-management, https://marssupplements.com/blogs/news, https://marssupplements.com/pages/mens-health-month-nnn-buy-3-2026 and https://marssupplements.com/pages/mens-health-month-nnn-buy-5-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://marssupplements.com/collections/power-and-energy/products/pure-ashwagandha-capsules-with-safed-musli-1-month-pack, whose canonical is https://marssupplements.com/products/pure-ashwagandha-capsules-with-safed-musli-1-month-pack. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://marssupplements.com/collections/bundles, https://marssupplements.com/collections/hair, https://marssupplements.com/collections/power-and-energy, https://marssupplements.com/collections/weight-management, https://marssupplements.com/collections/skin and https://marssupplements.com/collections/wellness and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Identifier 'origFetch' has already been declared”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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