purenatureplus.com website review

Google Tag Manager costs a phone 1.3 s of main-thread work and 2.0 MB 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.

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

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

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

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

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

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

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

19 KiB could be saved by minifying JavaScript.

About 80 KiB of CSS is downloaded but never applied on this page.

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

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

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.

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

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

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.9 s on a phone. Good is under 1.8 s.

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We offer a wide variety of health supplements, with over 20…”. Most of its time is element render delay (2.4 s).

1 image 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.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.8 MB in 231 requests on a phone: scripts 2.8 MB (93), other files 792 KiB (115) and stylesheets 106 KiB (9). Under 2 MB keeps phones on slow connections fast.

USCare_PureNature_Plus_Logo_142861ff-b2c0-48a0-a72f-87020a63 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).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://purenatureplus.com/search?q={search_term_string}")”.

2 links have no real href, so search engines can't follow them.

The homepage links to 86 pages on purenatureplus.com and 3 external pages.

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

https://purenatureplus.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://purenatureplus.com/collections/all-products, https://purenatureplus.com/customer_authentication/redirect, https://purenatureplus.com/policies/shipping-policy, https://purenatureplus.com/collections/joint-health, https://purenatureplus.com/collections/memory-brain-health and https://purenatureplus.com/collections/sleep-mood and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://purenatureplus.com/collections/all-products and https://purenatureplus.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343128785&Ver=2&mid=94c27b7b-47c3-447b-8b8b-2c8e0b3581a5&bo=1&sid=0a2ac9d0dd7411f1af403b0a8aebd56d&vid=0a2ae260dd7411f1a255b756e71d9f56&vids=1&msclkid=N&pi=918639831&l.

13 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn16.zipify.com/205b4950fc67d51e73a63795dcfa4fe34d10c549/gs/35c0afaedcff0b172655a…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage has only about 184 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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