ridgewallet.ca website review

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.0 MB 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.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Shopify and others), adding 3.7 MB and 2.4 s of main-thread time.

8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

alia-prod.com costs a phone 449 ms of main-thread work and 1.7 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.

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

Shopify costs a phone 280 ms of main-thread work and 493 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.

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

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

About 10 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alt attribute not provided for this image”.

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

Real visitors wait 957 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 6.7 MB in 388 requests on a phone: scripts 2.7 MB (152), images 2.6 MB (88) and other files 717 KiB (118). Under 2 MB keeps phones on slow connections fast.

M_HeroFull_4fde3548-3481-41a2-861c-70599cc6fe8e.jpg 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).

1 image (64 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.91 g of CO₂e: 229.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

There are 6 <h1> headlines (“Black Friday IS ON”, “Built better. Priced better.” and “For every guy on the list”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 146 pages on ridgewallet.ca and 13 external pages.

There is no https://ca.ridge.com/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://ca.ridge.com/collections/gift-guide has no meta description, so Google writes the search snippet from whatever text it finds.

https://ca.ridge.com/pages/tech-capsule has no <h1> headline, so visitors and search engines get no clear main topic.

https://ca.ridge.com/collections/holiday-sale, https://ca.ridge.com/collections/wallets, https://ca.ridge.com/collections/mens-rings and https://ca.ridge.com/pages/tech-capsule took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5439936&tm=gtm002&Ver=2&mid=53460f92-648c-4ab7-83b3-bc42ee41cb34&bo=1&sid=6128b670de0811f186f26b604ec3e9a0&vid=6128d430de0811f1946541d319a0814d&vids=1&msclkid=N&pi=918.

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

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

Social proof on the homepage: 168 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 584 words of visible text.

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