r13denim.com website review

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

47 files are served with short cache lifetimes, so returning visitors download them again (11.6 MB).

The page goes through 1 redirect before it starts loading, costing about 5.0 s. Link and advertise the final URL directly.

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

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

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

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

The page has 5,680 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 1.7 MB and 1.5 s of main-thread time.

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

Google Tag Manager costs a phone 416 ms of main-thread work and 487 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 322 ms of main-thread work and 620 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.

Clarity costs a phone 295 ms of main-thread work and 29 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.

Klaviyo costs a phone 193 ms of main-thread work and 317 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 201 ms. During a long task the page ignores taps.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 35.5 MB in 740 requests on a phone: images 28.3 MB (91), media 2.5 MB (1) and scripts 2.1 MB (159). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example FW26.2_Homepage.jpg at 2,779 px wide, shown at 195 px. Resized copies would save about 3.9 MB.

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

1 image (485 KiB) is 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.

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

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

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

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

Your title is only 17 characters: “R13 Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 19 <h1> headlines (“”, “F/W26.3 SHOP NOW” and “”). One clear main headline is easier for people and search engines.

The homepage links to 188 pages on r13denim.com and 10 external pages.

https://www.r13.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.r13.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.r13.com/customer_authentication/redirect, https://www.r13.com/policies/shipping-policy, https://www.r13.com/collections/pre-fall-2026, https://www.r13.com/collections/new-icons and https://www.r13.com/collections/pants-shorts have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.r13.com/collections/ready-to-wear-womens, https://www.r13.com/customer_authentication/redirect, https://www.r13.com/policies/shipping-policy, https://www.r13.com/collections/fall-winter-2026-drop-3, https://www.r13.com/collections/fall-winter-2026-drop-2 and https://www.r13.com/collections/fall-winter-2026-drop-1 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.r13.com/?sw=390&_su_rec=AngP8TfpYVbmqN8xZWt8imma5gmGy0D3yvb99Hs7cT-B7NQggdwYEOMUlhWsQaqxEkxsQxSmwF33ks5PTsfUc078v6u4x0iyO9KpLrFKNLQyINRHa0bny5lp1Q8kJVD0Rlsw6pNQnBWkPr_PvbHKwr-JboZ8r6d5GpiK.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 143 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 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 41 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 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.