stance.ca website review

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

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

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

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

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

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

8 third-party services load with your homepage (Clarity, PowerReviews and kiwisizing.com and others), adding 576 KiB and 437 ms of main-thread time.

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

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

1 image could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 66 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.

5 KiB JavaScript is shipped twice across bundles.

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

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.

Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GIVE THE GIFT OF STANCE”.

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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 5.6 MB in 410 requests on a phone: images 3.0 MB (160), other files 1.0 MB (170) and scripts 804 KiB (58). Under 2 MB keeps phones on slow connections fast.

imgi_74_101526_Homepage_Mobile_540x.gif weighs 564 KiB. On a phone connection a single image that size takes seconds.

1 image (564 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

[role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.

2 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

100 links have no real href, so search engines can't follow them.

There are 5 <h1> headlines (“Give the Gift Of Stance”, “CHOOSE WISELY” and “BUNDLE AND SAVE”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, ClothingStore, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

The homepage links to 441 pages on stance.ca and 11 external pages.

https://stance.ca/pages/socks, https://stance.ca/collections/icon-shop and https://stance.ca/collections/butter-blend have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=148017013&tm=shpfy_ui&Ver=2&mid=54e4c39d-a0f5-4e06-98a0-d8ef2d492d33&bo=1&sid=9a1e3810d94411f1a8580bd020ecb654&vid=9a1e74a0d94411f1a681fd33dff2eef9&vids=1&msclkid=N&pi.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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