nobis.ca website review

The page goes through 2 redirects before it starts loading, costing about 4.5 s. Link and advertise the final URL directly.

Signyfyd costs a phone 1.3 s of main-thread work and 283 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Signyfyd, nobis.com and Klaviyo and others), adding 6.4 MB and 2.2 s of main-thread time.

nobis.com costs a phone 506 ms of main-thread work and 5.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.

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

About 88 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

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

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

Klaviyo costs a phone 160 ms of main-thread work and 352 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,501 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

4 KiB could be saved by minifying CSS.

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

6 KiB could be saved by minifying JavaScript.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nobis FW26 Campaign Video”.

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

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

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

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

Your homepage downloads 11.5 MB in 361 requests on a phone: media 8.9 MB (2), scripts 1.5 MB (166) and other files 720 KiB (118). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

Your title is 76 characters, so Google will cut it off around 60: “Luxury Outerwear | Parkas, Jackets and Coats | Nobis Canada – Nobis - Canada”.

Your canonical URL points to nobis.com, not nobis.ca, so Google may credit that host instead.

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

There are 2 <h1> headlines (“Nobis - Canada” and “Product title”). One clear main headline is easier for people and search engines.

The homepage links to 216 pages on nobis.ca and 3 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.

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

41 of 97 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

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

The homepage has only about 217 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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