landish.ca website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 11.0 MB and 1.3 s of main-thread time.

Shopify costs a phone 295 ms of main-thread work and 8.5 MB 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.

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

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

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

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

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

27 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 400 ms faster on a phone.

Google Tag Manager costs a phone 306 ms of main-thread work and 569 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.

rebuyengine.com costs a phone 159 ms of main-thread work and 788 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,140 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

gotolstoy.com costs a phone 60 ms of main-thread work and 629 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.

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

15 KiB could be saved by minifying JavaScript.

13 KiB could be saved by minifying CSS.

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.

Your largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Landish creatine, aqua electrolytes and omega-3”.

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

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

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

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

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

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

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

Your homepage downloads 14.2 MB in 481 requests on a phone: media 6.9 MB (2), scripts 3.1 MB (200) and images 2.1 MB (74). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example SW_PDP_INGREDIENTS.jpg at 2,880 px wide, shown at 390 px. Resized copies would save about 279 KiB.

2 images further down the page (408 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 4.01 g of CO₂e: 481.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

17 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 49 elements on the page fail this check, rated moderate 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.

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

ARIA role should be appropriate for the element: 35 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 35 elements on the page fail this check, rated minor by axe-core.

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://landish.ca/search?q={search_term_string}")”.

The homepage links to 170 pages on landish.ca and 18 external pages.

https://landish.ca/products/marine-collagen-sparkling-water and https://landish.ca/collections/all/products/marine-collagen-sparkling-water all use the title “Marine Collagen Sparkling Water - Landish”. Search engines can't tell which page to show for a search, so each competes with the others.

https://landish.ca/products/marine-collagen-sparkling-water and https://landish.ca/collections/all/products/marine-collagen-sparkling-water use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://landish.ca/collections/all/products/collagen-creatine-bundle, whose canonical is https://landish.ca/products/collagen-creatine-bundle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://landish.ca/collections, https://landish.ca/collections/all/marine-collagen-powders, https://landish.ca/collections/all/greens-berries, https://landish.ca/collections/all/superfood-latte-mixes and https://landish.ca/collections/all/smarter-proteins have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

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

The homepage carries about 460 words of visible text.

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