rudsak.com website review

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

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

8 third-party services load with your homepage (Signyfyd, Yotpo and Klaviyo and others), adding 1.6 MB and 1.4 s of main-thread time.

Your mobile performance score is 50 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

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

Signyfyd costs a phone 787 ms of main-thread work and 259 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.

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

About 601 KiB of JavaScript is downloaded but never used on this page.

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

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

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

39 KiB could be saved by minifying CSS.

1 image could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

11 KiB JavaScript is shipped twice across bundles.

10 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Destination: Fall/Winter 2026”.

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

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

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

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

Your homepage downloads 14.1 MB in 326 requests on a phone: media 9.9 MB (2), scripts 1.9 MB (169) and images 953 KiB (29). Under 2 MB keeps phones on slow connections fast.

cddd995c493243fb902ab73d13511115.thumbnail.0000000000.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).

1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

There are 2 <h1> headlines (“Rudsak” and “Fall/Winter 2026”). One clear main headline is easier for people and search engines.

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

The homepage links to 341 pages on rudsak.com and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://rudsak.com/collections/pre-fall-2026, https://rudsak.com/collections/harvard, https://rudsak.com/collections/bombers and https://rudsak.com/collections/womens-heritage have no meta description, so Google writes the search snippet from whatever text it finds.

https://rudsak.com/collections/pre-fall-2026, https://rudsak.com/collections/harvard, https://rudsak.com/collections/bombers, https://rudsak.com/collections/base-collection, https://rudsak.com/collections/bestsellers and https://rudsak.com/collections/womens-new-arrivals and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://rudsak.com/collections/pre-fall-2026, https://rudsak.com/collections/harvard, https://rudsak.com/collections/base-collection, https://rudsak.com/collections/bestsellers, https://rudsak.com/collections/womens-new-arrivals and https://rudsak.com/collections/mens-new-arrivals and 8 others 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.

https://rudsak.com/collections/womens-heritage took over 3 s to send its HTML from our server.

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

5 images failed to load on a phone, for example https://us.rudsak.com/cdn/shop/files/MENU_PROMO_DROP_DOWN_-_DESKTOP_-_1_-_NEW_9.jpg?v=1790346994&width=332.

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

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

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

Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 247 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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