magicscoop.com website review

3 images could be 520 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and rechargecdn.com and others), adding 1.7 MB and 315 ms of main-thread time.

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

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

Shopify costs a phone 18 ms of main-thread work and 1.1 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.

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

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

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

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

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

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

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “you're probably dehydrated.”.

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

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

5 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' tap response (inp) went from 136 ms to 146 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 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 200 requests on a phone: media 3.3 MB (1), images 2.3 MB (23) and scripts 826 KiB (77). Under 2 MB keeps phones on slow connections fast.

4 images (1.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.

3 images are downloaded at several times the size a phone draws them, for example magic-scoop-greens-starter-kit-subscription.webp at 1,080 px wide, shown at 350 px. Resized copies would save about 424 KiB.

1 image further down the page (424 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 2.18 g of CO₂e: 261.5 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.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

There are 3 <h1> headlines (“Magic Scoop Magic Scoop”, “you're probably dehydrated.” and “we've paused orders to the united states.”). One clear main headline is easier for people and search engines.

The homepage links to 54 pages on magicscoop.com and 10 external pages.

https://magicscoop.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://magicscoop.com/customer_authentication/redirect and https://magicscoop.com/en-us/policies/refund-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://magicscoop.com/collections/all/products/electrolytes-creatine and https://magicscoop.com/products/electrolytes-creatine all use the title “Electrolytes + Creatine for Hydration | Shop | Magic Scoop”. Search engines can't tell which page to show for a search, so each competes with the others.

https://magicscoop.com/customer_authentication/redirect, https://magicscoop.com/pages/ingredients-electrolytes-creatine, https://magicscoop.com/blogs/study-buddy and https://magicscoop.com/en-us/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://magicscoop.com/collections/all/products/electrolytes-creatine and https://magicscoop.com/products/electrolytes-creatine use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://magicscoop.com/collections/all/products/electrolytes-creatine, whose canonical is https://magicscoop.com/en-us/products/electrolytes-creatine. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://magicscoop.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

The homepage carries about 425 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 23 cookies (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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.