duderobe.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.3 MB and 1.7 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page.

7 images could be 417 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

Google Tag Manager costs a phone 602 ms of main-thread work and 704 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 375 ms of main-thread work and 837 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 219 ms. During a long task the page ignores taps.

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

73 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 64 KiB JavaScript that modern phones do not need.

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

38 KiB JavaScript is shipped twice across bundles.

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

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

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A dad receiving a DudeRobe on Christmas morning, surrounded…”.

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

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

Real visitors wait 945 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 9.4 MB in 683 requests on a phone: images 4.4 MB (121), scripts 3.1 MB (155) and other files 1.5 MB (345). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Shark_Tank_TV_logo_svg.png at 2,560 px wide, shown at 28 px. Resized copies would save about 69 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.68 g of CO₂e: 321.2 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The homepage links to 104 pages on duderobe.com and 2 external pages.

https://duderobe.com/cdn/shop/videos/c/vp/01cda63bb2394c0cbea9d735af5091be/01cda63bb2394c0cbea9d735af5091be.m3u8 has no <title>, so Google invents the link text in results.

https://duderobe.com/collections/gift-bundles and https://duderobe.com/cdn/shop/videos/c/vp/01cda63bb2394c0cbea9d735af5091be/01cda63bb2394c0cbea9d735af5091be.m3u8 have no meta description, so Google writes the search snippet from whatever text it finds.

https://duderobe.com/pages/our-story-1 and https://duderobe.com/cdn/shop/videos/c/vp/01cda63bb2394c0cbea9d735af5091be/01cda63bb2394c0cbea9d735af5091be.m3u8 have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97198232&Ver=2&mid=c93c9152-9874-4c3a-b2e4-4e55bd3c40b9&bo=2&sid=12f551a0dccb11f1bdb0697b98d38380&vid=12f5ac90dccb11f1a410ddb89674d777&vids=1&msclkid=N&pi=918639831&lg.

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

4 errors were logged to the browser console while the page loaded, for example “Clarity pixel failed to start... TypeError: Failed to fetch”.

Your longest form asks for 11 fields (6 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.

The homepage carries about 436 words of visible text.

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