leonieandco.ca website review

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

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

alia-prod.com costs a phone 1.2 s of main-thread work and 342 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

7 third-party services load with your homepage (alia-prod.com, Shopify and Klaviyo and others), adding 1.6 MB and 1.7 s of main-thread time.

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

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

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

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

4 images could be 86 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Klaviyo costs a phone 205 ms of main-thread work and 306 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.

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

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

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

Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying JavaScript.

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.

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

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

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 “Three women wearing Leonie 3D leggings in teal, black and b…”.

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

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

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

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

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

Your homepage downloads 3.9 MB in 512 requests on a phone: other files 1.5 MB (279), scripts 1.4 MB (186) and images 420 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

1 image has 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.

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

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

The homepage links to 80 pages on leonieandco.ca and 2 external pages.

https://leonieandco.com/en-ca/collections/best-sellers and https://leonieandco.com/en-ca/apps/tracking are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://leonieandco.com/en-ca/collections/3d-leggings, https://leonieandco.com/en-ca/collections/3d-pocket-leggings, https://leonieandco.com/en-ca/collections/3d-shorts, https://leonieandco.com/en-ca/collections/3d-tshirts, https://leonieandco.com/en-ca/collections/3d-tshirts-copy and https://leonieandco.com/en-ca/products/bundle-legging-short-tshirt and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://leonieandco.com/en-ca/products/3d-anti-cellulite-legging-black, whose canonical is https://leonieandco.com/en-ca/products/3d-anti-cellulite-legging. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://leonieandco.com/en-ca/collections/3d-leggings, https://leonieandco.com/en-ca/collections/3d-pocket-leggings, https://leonieandco.com/en-ca/collections/3d-shorts, https://leonieandco.com/en-ca/collections/3d-tshirts, https://leonieandco.com/en-ca/collections/3d-tshirts-copy and https://leonieandco.com/en-ca/products/bundle-legging-short-tshirt and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://leonieandco.com/en-ca/collections/3d-tshirts, https://leonieandco.com/en-ca/collections/3d-tshirts-copy, https://leonieandco.com/en-ca/pages/contact and https://leonieandco.com/en-ca/blogs/news have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 13 fields (0 required). Every extra field lowers completion.

The homepage carries about 725 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 26 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.