wellnessresources.com website review

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

55 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Shopify, Google CDN and rebuyengine.com and others), adding 2.3 MB and 717 ms of main-thread time.

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

About 622 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

Shopify costs a phone 168 ms of main-thread work and 1,016 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.

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

Google CDN costs a phone 158 ms of main-thread work and 298 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.

rebuyengine.com costs a phone 154 ms of main-thread work and 297 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.

Klaviyo costs a phone 141 ms of main-thread work and 407 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.

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

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

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

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

20 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 20.4 s. Good is under 3.8 s.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 119 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 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 404 requests on a phone: images 2.8 MB (64), scripts 1.8 MB (144) and other files 1.4 MB (146). Under 2 MB keeps phones on slow connections fast.

14 images are downloaded at several times the size a phone draws them, for example Q10-ubiquinol-rev1_left.jpg at 2,019 px wide, shown at 151 px. Resized copies would save about 839 KiB.

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

6 buttons have no accessible name, so screen readers announce just “button”.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 tap target is too small or too close together to hit reliably with a finger.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 69 characters, so Google will cut it off around 60: “Discover Wellness Resources: Superior Quality Nutritional Supplements”.

There are 2 <h1> headlines (“” and “Family Owned Since 1985”). One clear main headline is easier for people and search engines.

The homepage links to 193 pages on wellnessresources.com and 19 external pages.

There is no https://wellnessresources.com/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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.

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: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

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

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