supplynow.ca website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Affirm and Shopify and others), adding 803 KiB and 739 ms of main-thread time.

Google Tag Manager costs a phone 546 ms of main-thread work and 510 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

About 260 KiB of JavaScript is downloaded but never used on this page.

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

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

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

3 KiB could be saved by minifying JavaScript.

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

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

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.

4 KiB could be saved by minifying CSS.

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 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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. Most of its time is resource load delay (3.4 s).

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

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

The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 3.0 MB in 224 requests on a phone: images 1.0 MB (29), scripts 894 KiB (47) and other files 849 KiB (125). Under 2 MB keeps phones on slow connections fast.

homepage-banner-1.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).

3 images are downloaded at several times the size a phone draws them, for example 8127b_compressed__86333.png at 800 px wide, shown at 171 px. Resized copies would save about 180 KiB.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 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: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 89 characters, so Google will cut it off around 60: “Your Trusted Safety Equipment Supplier in Markham Ontario - SupplyNow – Supplynow Limited”.

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

Your <h1> is empty.

The homepage links to 712 pages on supplynow.ca and 7 external pages.

https://www.supplynow.ca/collections/arc-flash-clothing, https://www.supplynow.ca/collections/arc-rated-gloves, https://www.supplynow.ca/collections/arc-flash-helmets-hoods-and-sheilds, https://www.supplynow.ca/collections/arc-flash-jackets-overalls-and-coveralls, https://www.supplynow.ca/collections/arc-flash-t-shirts and https://www.supplynow.ca/collections/arc-flash-suits-and-kits and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.supplynow.ca/collections/arc-flash-clothing, https://www.supplynow.ca/collections/arc-rated-gloves, https://www.supplynow.ca/collections/arc-flash-suits-and-kits, https://www.supplynow.ca/collections/high-visibility-fr-clothing and https://www.supplynow.ca/collections/disposable-gloves have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 200 found) 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: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,564 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 13 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.