ruti.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Yotpo and others), adding 2.9 MB and 1.8 s of main-thread time.

Google Tag Manager costs a phone 971 ms of main-thread work and 1.4 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.

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

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

12 images could be 265 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Yotpo costs a phone 152 ms of main-thread work and 331 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 64 ms of main-thread work and 459 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.

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

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

33 KiB could be saved by minifying JavaScript.

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

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.

4 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

Your homepage downloads 12.4 MB in 426 requests on a phone: media 6.2 MB (1), scripts 3.7 MB (129) and images 1.2 MB (37). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (43 KiB) 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 3.53 g of CO₂e: 423.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 147 pages on ruti.com and 4 external pages.

Your Organization JSON-LD is missing logo, 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://ruti.com/collections/all, https://ruti.com/collections/travel and https://ruti.com/collections/the-corduroy-capsule have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 35 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 64 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.