ehplabs.ca website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and Clarity and others), adding 144.2 MB and 837 ms of main-thread time.

Shopify costs a phone 48 ms of main-thread work and 142.9 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 57. Pages that score under 90 lose visitors before the first paint.

15 images could be 415 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.

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

alia-prod.com costs a phone 285 ms of main-thread work and 636 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.

Google Tag Manager costs a phone 171 ms of main-thread work and 343 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 1,723 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

3 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 131 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 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 146.7 MB in 374 requests on a phone: media 142.7 MB (18), scripts 1.4 MB (110) and images 1.3 MB (24). Under 2 MB keeps phones on slow connections fast.

Homepage_Collection_Tile_OxyShred_Range_Non-Stim.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).

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

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

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Your title is 80 characters, so Google will cut it off around 60: “Online Sports Supplement Store | The Official Home of OxyShred™ – EHPlabs Canada”.

There are 2 <h1> headlines (“Shop the OxyShred Range” and “Explore the whole range”). One clear main headline is easier for people and search engines.

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

The homepage links to 124 pages on ehplabs.ca and 18 external pages.

Your homepage links to https://ehplabs.ca/products/isopept-zero-hydrolyzed-whey-protein-isolate, https://ehplabs.ca/products/oxyglow-natural-marine-collagen and https://ehplabs.ca/products/beyond-bcaa-eaa-intra-workout, which answer with an error. Visitors hit a dead end and search engines drop them.

https://ehplabs.ca/collections/all, https://ehplabs.ca/collections/protein-1, https://ehplabs.ca/collections/all-supplements and https://ehplabs.ca/collections/summer-sale have no meta description, so Google writes the search snippet from whatever text it finds.

https://ehplabs.ca/collections/summer-sale has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://files.alia-prod.com/13345/877613dafea76021.webp.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The page uses urgency cues (a countdown or limited-time wording).

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