richsolfoods.ca website review

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

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

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

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

8 third-party services load with your homepage (loox.io, Shopify and Klaviyo and others), adding 1.8 MB and 766 ms of main-thread time.

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

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

loox.io costs a phone 259 ms of main-thread work and 713 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.

7 images could be 142 KiB 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.

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

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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.

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

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

Your homepage downloads 3.8 MB in 284 requests on a phone: scripts 1.4 MB (120), images 1.2 MB (38) and other files 801 KiB (102). Under 2 MB keeps phones on slow connections fast.

11.webp 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).

4 images (439 KiB) 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.

1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Your title is only 14 characters: “Rich Sol Foods”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 88 pages on richsolfoods.ca and 1 external page.

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.

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

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

https://richsolfoods.com/collections/high-grade-healing/products/irishseamoss and https://richsolfoods.com/products/irishseamoss all use the title “Wildcrafted Irish Sea Moss from St. Lucia | Rich Sol Foods”. Search engines can't tell which page to show for a search, so each competes with the others.

https://richsolfoods.com/collections/all, https://richsolfoods.com/collections/high-grade-healing, https://richsolfoods.com/collections/seaweeds, https://richsolfoods.com/collections/mens-health, https://richsolfoods.com/a/blog and https://richsolfoods.com/pages/about-us-1 and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://richsolfoods.com/collections/high-grade-healing/products/irishseamoss and https://richsolfoods.com/products/irishseamoss use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://richsolfoods.com/collections/high-grade-healing/products/herb-cycling-womb-healing-bundle-home-remedies-for-menstrual-cramps, whose canonical is https://richsolfoods.com/products/herb-cycling-womb-healing-bundle-home-remedies-for-menstrual-cramps. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://richsolfoods.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 402 ()”.

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.

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

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