elsenutrition.ca website review

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

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

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

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

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

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

8 third-party services load with your homepage (jQuery CDN, Shopify and Outbrain and others), adding 627 KiB and 270 ms of main-thread time.

About 74 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.

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

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

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

2 KiB could be saved by minifying JavaScript.

Your largest element takes 7.4 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 7.5 s. Good is under 3.8 s.

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

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

6 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 2.9 MB in 264 requests on a phone: images 1.3 MB (40), other files 712 KiB (78) and scripts 517 KiB (65). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (221 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

39 images have no alt text, which hurts accessibility and image search.

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

Headings should not be empty: 24 elements on the page fail this check, rated minor by axe-core.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 23 characters: “Else Nutrition | Canada”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

Your <h1> is empty.

The homepage links to 61 pages on elsenutrition.ca and 11 external pages.

Your homepage links to https://elsenutrition.ca/products/else-adult-nutrition-vanilla-ready-to-drink-shakes and https://elsenutrition.ca/products/else-toddler-omega-plant-based-complete-balanced-nutrition, which answer with an error. Visitors hit a dead end and search engines drop them.

/ and https://elsenutrition.ca/fr all use the title “Else Nutrition | Canada”. Search engines can't tell which page to show for a search, so each competes with the others.

https://elsenutrition.ca/collections/infant-cereal, https://elsenutrition.ca/collections/kids, https://elsenutrition.ca/blogs/else-blog, https://elsenutrition.ca/pages/faq, https://elsenutrition.ca/pages/awards-accreditations and https://elsenutrition.ca/pages/reasons-to-love and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://elsenutrition.ca/collections/infant-cereal, https://elsenutrition.ca/collections/kids, https://elsenutrition.ca/tools/perfect-product-finder/best-product-for-you, https://elsenutrition.ca/pages/faq, https://elsenutrition.ca/pages/contact and https://elsenutrition.ca/pages/retail-stores and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.ecomposer.app/vendors/css/ecom-base.css?v=1.6' from origin 'https://elsenutrit…”.

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.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 456 words of visible text.

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