snowjoe.com website review

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

37 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Clarity, mavenoid.com and gemcommerce.com and others), adding 5.0 MB and 2.6 s of main-thread time.

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

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

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

Clarity costs a phone 574 ms of main-thread work and 29 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.

mavenoid.com costs a phone 412 ms of main-thread work and 320 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.

gemcommerce.com costs a phone 408 ms of main-thread work and 58 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 279 ms of main-thread work and 358 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 265 ms. During a long task the page ignores taps.

23 KiB could be saved by minifying JavaScript.

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

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

Real visitors wait 230 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-10-31, real Chrome visitors' tap response (inp) went from 155 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 10.0 MB in 673 requests on a phone: images 4.1 MB (79), scripts 3.1 MB (201) and other files 1.9 MB (312). Under 2 MB keeps phones on slow connections fast.

Homepage_Header_X20_SHOVEL_1302x1476_1_04f9ed98-c448-4981-91 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 138665-gift-red-bow-download-hq.png at 3,000 px wide, shown at 25 px. Resized copies would save about 200 KiB.

11 images further down the page (374 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

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

Your <h1> is empty.

The homepage links to 303 pages on snowjoe.com and 17 external pages.

https://shopjoe.com/discount/EARLY30 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://shopjoe.com/discount/EARLY30 all use the title “Shop Joe Brands: Snow Joe®, Sun Joe®, Aqua Joe®, Auto Joe®”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shopjoe.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://shopjoe.com/discount/EARLY30, https://shopjoe.com/pages/x20-shovel, https://shopjoe.com/pages/x20-saw, https://shopjoe.com/pages/x20-stormjet, https://shopjoe.com/collections/chainsaws-pole-saws and https://shopjoe.com/collections/chippers-splitters and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://shopjoe.com/pages/x20-shovel, https://shopjoe.com/pages/x20-saw and https://shopjoe.com/pages/x20-stormjet have 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.

We fetched 15 pages linked from your homepage (of 98 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=259120306&tm=shpfy_ui&Ver=2&mid=69848210-af27-483e-a99b-3617ce123f17&bo=1&sid=de5a49c0dbb511f18f2e75acc5d952dc&vid=de5a6570dbb511f1839d09e6634f467c&vids=1&msclkid=N&pi.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

Requests the notification permission on page load.

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

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