ragingmammoth.com website review

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

About 255 KiB 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.

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

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

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

8 third-party services load with your homepage (Shopify, Facebook and Snapchat and others), adding 1.7 MB and 688 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.4 MB in 400 requests on a phone: images 2.8 MB (67), scripts 1.2 MB (142) and other files 843 KiB (163). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

7 images (2.1 MB) are 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.

Shotski-Red-Black-floral.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).

By the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Your meta description is only 69 characters: “Raging Mammoth. We make legendary products for bros who love to rage.”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 91 pages on ragingmammoth.com and 1 external page.

https://ragingmammoth.com/collections/ultimate-beer-opening-tools, https://ragingmammoth.com/collections/shotskis and https://ragingmammoth.com/collections/extras have no meta description, so Google writes the search snippet from whatever text it finds.

https://ragingmammoth.com/products/floral-shotski, https://ragingmammoth.com/products/miami-vices-shotski, https://ragingmammoth.com/products/raging-mammoth-shotski, https://ragingmammoth.com/products/college-shotski and https://ragingmammoth.com/products/blank-shotski use the same meta description. A description written for each page earns more clicks.

https://ragingmammoth.com/collections/ultimate-beer-opening-tools, https://ragingmammoth.com/collections/shotskis and https://ragingmammoth.com/collections/extras have no <h1> headline, so visitors and search engines get no clear main topic.

https://ragingmammoth.com/collections/ultimate-beer-opening-tools and https://ragingmammoth.com/products/the-america-sleeve 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 27 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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

Social proof on the homepage: 4 customer or partner logos. 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.

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

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