montrealweights.ca website review

The page goes through 1 redirect before it starts loading, costing about 7.8 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and Clarity and others), adding 1.9 MB and 683 ms of main-thread time.

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

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

1 image could be 60 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 2.4 s on main-thread work while loading, 858 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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.

Your largest element takes 28.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Montreal Weights athletes training with adjustable dumbbells”.

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

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

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

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

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

Your homepage downloads 8.2 MB in 296 requests on a phone: fonts 2.8 MB (36), scripts 2.8 MB (113) and images 2.1 MB (50). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

2 tap targets are too small or too close together to hit reliably with a finger.

9 images have no alt text, which hurts accessibility and image search.

[role]s are not contained by their required parent element (4 elements).

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 155 pages on montrealweights.ca and 5 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/customer_authentication/redirect, /policies/shipping-policy, /collections/bestsellers, /collections/bundles, /collections/walking-pads and /collections/cable-machines have no meta description, so Google writes the search snippet from whatever text it finds.

/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Contentsquare tag 304568 skipped: another Contentsquare tag already runs”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://montrealweights.ca/customer_authentication/redirect?locale=en&region_country=CA.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

montrealweights.ca has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

montrealweights.ca's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be montrealweights.ca is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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