ruggedanddapper.com website review

About 651 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

8 third-party services load with your homepage (powrcdn.com, POWr and Google Tag Manager and others), adding 20.2 MB and 780 ms of main-thread time.

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

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

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

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

powrcdn.com costs a phone 219 ms of main-thread work and 609 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.

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

1 KiB JavaScript is shipped twice across bundles.

Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Daily Power Scrub Mens Facial Cleanser”.

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

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

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

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

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 28.5 MB in 205 requests on a phone: media 24.0 MB (2), images 2.0 MB (30) and scripts 1.3 MB (66). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example bkg-home__steps.jpg at 4,000 px wide, shown at 390 px. Resized copies would save about 1.2 MB.

bkg-home__steps.jpg weighs 545 KiB. On a phone connection a single image that size takes seconds.

12 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 71 pages on ruggedanddapper.com and 11 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://ruggedanddapper.com/collections/all, https://ruggedanddapper.com/pages/find-your-regimen, https://ruggedanddapper.com/pages/ingredients, https://ruggedanddapper.com/blogs/news, https://ruggedanddapper.com/pages/wholesale-natural-and-organic-skin-care-products-for-men and https://ruggedanddapper.com/collections/skincare and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ruggedanddapper.com/collections/all, https://ruggedanddapper.com/pages/find-your-regimen and https://ruggedanddapper.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame inste…”).

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'recurring_orders')”.

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

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

Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

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

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