kerwellness.com website review

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

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

35 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

8 third-party services load with your homepage (Hotjar, Shopify and rechargecdn.com and others), adding 1.1 MB and 998 ms of main-thread time.

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

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

247 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

rechargecdn.com costs a phone 140 ms of main-thread work and 296 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.

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

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

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

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

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 8.0 MB in 366 requests on a phone: images 4.8 MB (95), scripts 1.7 MB (112) and other files 874 KiB (118). Under 2 MB keeps phones on slow connections fast.

14 images are downloaded at several times the size a phone draws them, for example hi_res-bc-kerwell_r1_Gif-5-Daily-Vegan-Gummies.gif at 1,080 px wide, shown at 243 px. Resized copies would save about 1.7 MB.

hi_res-bc-kerwell_r1_Gif-5-Daily-Vegan-Gummies.gif weighs 1.2 MB. On a phone connection a single image that size takes seconds.

20 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Links must have discernible text: 14 elements on the page fail this check, rated serious by axe-core.

7 elements have a tabindex above 0, which scrambles the keyboard order.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

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

Headings skip levels (h2 → h4, h2 → h4 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. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “Kerwell | Premium Wellness Products for Pain, Sleep, Stress and Health”.

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 230 pages on kerwellness.com and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://kerwellness.com/pages/store-locator, which answers with an error. Visitors hit a dead end and search engines drop it.

https://kerwellness.com/pages/our-story, https://kerwellness.com/blogs/news, https://kerwellness.com/pages/contact-us, https://kerwellness.com/pages/brands-directory, https://kerwellness.com/collections/supplements and https://kerwellness.com/collections/skincare and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kerwellness.com/pages/our-story, https://kerwellness.com/blogs/news, https://kerwellness.com/pages/contact-us, https://kerwellness.com/pages/brands-directory, https://kerwellness.com/collections/supplements and https://kerwellness.com/collections/skincare and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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