wem.ca website review

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

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

3 third-party services load with your homepage (Vimeo, cdn-cookieyes.com and Adobe TypeKit), adding 13.9 MB and 51 ms of main-thread time.

Vimeo costs a phone 42 ms of main-thread work and 13.8 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 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

Desktop scores 94 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mall Walk Video Thumbnail”.

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

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

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

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

Your homepage downloads 15.6 MB in 118 requests on a phone: other files 13.4 MB (24), scripts 1,011 KiB (39) and images 895 KiB (27). Under 2 MB keeps phones on slow connections fast.

977-398-3.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).

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“Discover More Than You Imagined.”, “Every Style. Every Taste.” and “Turn Your Visit Into a Getaway.”). One clear main headline is easier for people and search engines.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 104 pages on wem.ca and 13 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.wem.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.wem.ca/hours has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/tgg2zoa.css' violates the following Content Security Policy directive: "connect-…”.

Chrome logged issues while loading the page (“Cookie”).

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

Opening the homepage sets 4 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.