savouree.ca website review

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

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

6 images could be 725 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.

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

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

1 long task block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.

4 third-party services load with your homepage (Shopify, Bugsnag and YouTube and others), adding 108 KiB and 42 ms of main-thread time.

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

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.

5 KiB could be saved by minifying JavaScript.

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

9 images are downloaded at several times the size a phone draws them, for example IMG_5851.heic at 4,284 px wide, shown at 244 px. Resized copies would save about 1.4 MB.

Your homepage downloads 3.1 MB in 143 requests on a phone: images 2.0 MB (15), other files 652 KiB (64) and scripts 338 KiB (50). Under 2 MB keeps phones on slow connections fast.

u1562863268_a_website_hero_image_with_cardamom_plants_all_sp 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).

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

Page should contain a level-one heading: 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.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 8 characters: “Savouree”. 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.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 63 pages on savouree.ca and 2 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.

https://savouree.ca/collections/all, https://savouree.ca/blogs/recipes and https://savouree.ca/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://savouree.ca/collections/all, https://savouree.ca/blogs/recipes, https://savouree.ca/products/baharat, https://savouree.ca/products/5-spice, https://savouree.ca/products/smokehouse-spice-1 and https://savouree.ca/products/gift-pack and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Opening the homepage sets 7 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.