Website review, no card needed
r13.com website review
Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 73 checks
This review found 34 issues worth fixing on r13.com, 16 of them high impact, across 73 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #51,854 of 92,728 reviewed websitesbeats 39%
- #31,717 of 49,337 online storesbeats 31%
- #30,005 of 44,509 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 188 ms |
| May 9, 2026 | 187 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 202 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 192 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 265 ms |
| Aug 22, 2026 | 362 ms |
| Aug 29, 2026 | 511 ms |
| Sep 5, 2026 | 517 ms |
| Sep 12, 2026 | 521 ms |
| Sep 19, 2026 | 544 ms |
| Sep 26, 2026 | 640 ms |
| Oct 3, 2026 | 629 ms |
| Oct 10, 2026 | 566 ms |
| Oct 17, 2026 | 455 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Avoid multiple page redirects
5.9 sThe page goes through 1 redirect before it starts loading, costing about 5.9 s. Link and advertise the final URL directly.
Reduce unused JavaScript
1.4 s · 414 KiBAbout 414 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 16.0 s
A phone's processor spends 16.0 s on main-thread work while loading, 12.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 482 ms. During a long task the page ignores taps.
Reduce unused CSS
270 ms · 38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
Minify JavaScript
120 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
4 third-party services on the page
4 third-party services load with your homepage (lawwwing.com, Cloudflare CDN and Google CDN and others), adding 49 KiB and 2 ms of main-thread time.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 63.5 s
63.5 sYour largest element takes 63.5 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 21.9 s
21.9 sVisually, the page fills in at 21.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 73.8 s
73.8 sThe page becomes fully interactive after 73.8 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 172% slower for real visitors
+172%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 188 ms to 455 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 191 ms
191 msReal visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 419 ms
419 msReal visitors wait 419 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 22.3 MB in 627 requests
22.3 MBYour homepage downloads 22.3 MB in 627 requests on a phone: images 15.2 MB (65), media 2.5 MB (1) and scripts 2.1 MB (162). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
FW26.2_Homepage.jpg weighs 1.8 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.0 MB2 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 2.0 MB.
11 images below the first screen load straight away
11 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
13 images in older formats
13 images (611 KiB) are 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.
About 6.3 g of CO₂ per visit
6.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.31 g of CO₂e: 757.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
45 links without text
45 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (9 elements)
Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 3 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “R13 Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.
16 H1 headlines
There are 16 <h1> headlines (“”, “FW26.2 DENIM SHOP NOW” and “”). One clear main headline is easier for people and search engines.
182 internal links, 10 external
The homepage links to 182 pages on r13.com and 10 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “R13 cuts against the grain. Luxury denim, women’s clothes, and footwear built with precision, worn with defiance. Free …”.
Canonical URL set
The canonical URL is https://www.r13.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.r13.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.r13.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
1 page without a title
https://www.r13.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
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.
3 pages without a meta description
https://www.r13.com/customer_authentication/redirect, https://www.r13.com/policies/shipping-policy and https://www.r13.com/collections/pre-fall-2026 have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
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-2, https://www.r13.com/collections/fall-winter-2026-drop-1 and https://www.r13.com/collections/pre-fall-2026 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
3 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
3 broken images
3 images failed to load on a phone, for example https://ddrlddj86sfyk.cloudfront.net/image_scans/prd/bc082f2f-6474-42c7-892f-5c11c999a40a/r13-boy-flare-kennet-black-stretch-1259176248_3871e375.jpg.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
68 of 72 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 144 words
The homepage has only about 144 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Women's Denim” and “FW26.2 DENIM SHOP NOW”.
8 calls to action
The homepage has 8 calls to action, for example “Shop”, “FW26.2 DENIM SHOP NOW” and “THE JANINE SHOP NOW”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before 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.
36 cookies set on arrival
36Opening the homepage sets 36 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
55 other companies contacted
Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at r13.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on r13.com, including 12 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.