riobec.ca website review

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

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

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

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

8 third-party services load with your homepage (weglot.com, Shopify and automizely-analytics.com and others), adding 1.5 MB and 1.5 s of main-thread time.

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

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

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

weglot.com costs a phone 668 ms of main-thread work and 112 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.

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

About 93 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.

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

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

61 KiB JavaScript is shipped twice across bundles.

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

31 KiB could be saved by minifying JavaScript.

11 KiB could be saved by minifying CSS.

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.

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 18.8 s. Good is under 3.8 s.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Manteau d'hiver Timberland Ironhide - Riobec”.

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

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

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

Real visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 145 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 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 392 requests on a phone: other files 2.8 MB (190), scripts 1.5 MB (131) and images 1.4 MB (28). Under 2 MB keeps phones on slow connections fast.

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

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

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

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your <h1> is empty.

The homepage links to 457 pages on riobec.ca and 6 external pages.

https://riobec.ca/products/timberland-boondock-ultralight-8-impermeable-boa, https://riobec.ca/products/couvre-chaussure-neos-n5p3, https://riobec.ca/products/manteau-timberland-pro-ironhide and https://riobec.ca/products/mitaines-doublees-deluxe-35 have no <h1> headline, so visitors and search engines get no clear main topic.

https://riobec.ca/products/mitaines-doublees-deluxe-35 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://riobec.ca/products/couvre-chaussure-neos-n5p3 and https://riobec.ca/products/mitaines-doublees-deluxe-35 took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The `disableRemotePlayback` attribute should be used in order to disable the default Cast integrati…”).

3 errors were logged to the browser console while the page loaded, for example “Identifier 'pmUserInteractions' has already been declared”.

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map 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 2,422 words of visible text.

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