sunopta.com website review

About 912 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

About 218 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (Google CDN, tagembed.com and Google Tag Manager and others), adding 1.3 MB and 661 ms of main-thread time.

8 images could be 488 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.

Google CDN costs a phone 392 ms of main-thread work and 734 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 long tasks block the main thread while loading, the longest for 461 ms. During a long task the page ignores taps.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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.

Real visitors wait 721 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “website_button_SunOpta-Refresco-hires”.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 80 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 4.0 MB in 183 requests on a phone: scripts 1.6 MB (86), images 1.3 MB (21) and other files 371 KiB (15). Under 2 MB keeps phones on slow connections fast.

50th-logo-768x355.png 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).

9 images (801 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.

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

3 images are downloaded at several times the size a phone draws them, for example Sustainability.png at 508 px wide, shown at 50 px. Resized copies would save about 204 KiB.

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

Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

The homepage links to 177 pages on sunopta.com and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/history has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /plant-based-beverages/almond, whose canonical is /plant-based-beverages/almondmilk. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, 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 4 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.