zumanutrition.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 1.6 MB and 733 ms of main-thread time.

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

Google Tag Manager costs a phone 346 ms of main-thread work and 320 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.

6 images could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Shopify costs a phone 60 ms of main-thread work and 700 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 134 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.

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

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

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

19 KiB JavaScript is shipped twice across bundles.

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.

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A dropper of Zuma Nutrition Fulvic Acid & Trace Ocean Miner…”.

Real visitors wait 902 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 276 requests on a phone: scripts 1.2 MB (98), other files 821 KiB (118) and images 701 KiB (13). Under 2 MB keeps phones on slow connections fast.

zuma-complete-amino-in-hand-hero.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example zuma-nutrition-stress-b-complex-vitamin-c-01-front.jpg at 2,000 px wide, shown at 163 px. Resized copies would save about 181 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.7 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.

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

The homepage links to 173 pages on zumanutrition.com and 8 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/policies/shipping-policy and /collections/shop-all took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 83 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_TUNNEL_CONNECTION_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.zumanutrition.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

zumanutrition.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 1,092 words of visible text.

DMARC is set to p=none, so mail pretending to be zumanutrition.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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 25 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.