cannariver.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Yotpo, Klaviyo and Shopify and others), adding 2.5 MB and 778 ms of main-thread time.

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

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

65 KiB could be saved by minifying JavaScript.

1 image could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Yotpo costs a phone 231 ms of main-thread work and 654 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.

Klaviyo costs a phone 184 ms of main-thread work and 498 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.

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

tidio.co costs a phone 64 ms of main-thread work and 517 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.

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

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

14 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.

Your largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 383 requests on a phone: scripts 2.5 MB (153), other files 2.1 MB (142) and images 821 KiB (43). Under 2 MB keeps phones on slow connections fast.

cr-bogo-homepage-gif-mobile-750x1000.gif 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 (409 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.78 g of CO₂e: 213.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Alternative text of images should not be repeated as text: 30 elements on the page fail this check, rated minor by axe-core.

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

Elements use prohibited ARIA attributes (1 element).

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

The homepage links to 109 pages on cannariver.com and 4 external pages.

https://www.cannariver.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Unexpected token 'const'”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,754 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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