jsnadistribution.com website review

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

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

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

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

5 third-party services load with your homepage (Shopify, shop.app and Mailchimp and others), adding 601 KiB and 175 ms of main-thread time.

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

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

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

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

5 KiB JavaScript is shipped twice across bundles.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Raspberry-Lime-Ginger Kombucha, J's Kombucha”.

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

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

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

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.

Sauna-Water_-Forest-Fields_-Final-Can-Mockup-_9.14.26.gif 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).

1 image (39 KiB) is 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 0.50 g of CO₂e: 60.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 38 pages on jsnadistribution.com and 4 external pages.

https://jsnadistribution.com/collections/all, https://jsnadistribution.com/pages/quick-order, https://jsnadistribution.com/policies/shipping-policy and https://jsnadistribution.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://jsnadistribution.com/collections/all, https://jsnadistribution.com/collections/aqua-virgo-sparkling-water, https://jsnadistribution.com/collections/huxley-energy-refresher, https://jsnadistribution.com/collections/jinx-tea, https://jsnadistribution.com/collections/js-kombucha and https://jsnadistribution.com/collections/sauna-water-1 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

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.

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.

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

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

The homepage has only about 186 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 Analytics and Google Tag Manager (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 9 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.