rhinousainc.ca website review

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

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

8 third-party services load with your homepage (recart.com, Google Tag Manager and upstackified.com and others), adding 1.7 MB and 1.6 s of main-thread time.

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

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

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

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

recart.com costs a phone 357 ms of main-thread work and 222 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.

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

Google Tag Manager costs a phone 278 ms of main-thread work and 351 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 2,872 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

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

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

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

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' tap response (inp) went from 137 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 23.7 MB in 529 requests on a phone: media 16.6 MB (20), images 3.0 MB (63) and scripts 2.2 MB (167). Under 2 MB keeps phones on slow connections fast.

fe0c82da4a984b70bcb7a672fdb30b6f.thumbnail.0000000000.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 is downloaded at several times the size a phone draws it, for example mobilemenu-bestsellers2.webp at 500 px wide, shown at 135 px. Resized copies would save about 17 KiB.

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

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 138 pages on rhinousainc.ca and 16 external pages.

https://www.rhinousainc.com/pages/register-your-lifetime-warranty has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rhinousainc.com/collections/all-products, https://www.rhinousainc.com/pages/shipping-policy, https://www.rhinousainc.com/collections/recovery-gear, https://www.rhinousainc.com/collections/tie-down-straps-1, https://www.rhinousainc.com/collections/overlanding-camping and https://www.rhinousainc.com/collections/trailer-hitch and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rhinousainc.com/collections/accessories, https://www.rhinousainc.com/collections/deals, https://www.rhinousainc.com/pages/find-a-dealer, https://www.rhinousainc.com/pages/about-us and https://www.rhinousainc.com/products/bed-mounted-retractable-ratchet-straps-ford-trucks took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

The homepage carries about 733 words of visible text.

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