relodestore.com website review

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

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

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

8 third-party services load with your homepage (lovable.app, Google Tag Manager and Shopify and others), adding 1.1 MB and 986 ms of main-thread time.

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

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

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

lovable.app costs a phone 321 ms of main-thread work and 515 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.

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

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

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

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

14 KiB JavaScript is shipped twice across bundles.

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

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 22.1 s. Good is under 3.8 s.

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

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

Real visitors wait 288 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 5.3 MB in 375 requests on a phone: images 2.7 MB (84), scripts 1.2 MB (128) and other files 1.0 MB (109). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example FSR07294.jpg at 480 px wide, shown at 31 px. Resized copies would save about 56 KiB.

12 images further down the page (307 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images (165 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.

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

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

Some list items are not inside a list.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 72 characters, so Google will cut it off around 60: “Gym Clothes & Workout Clothes for Women & Men | RELODE – relodestore.com”.

The homepage links to 267 pages on relodestore.com and 4 external pages.

https://relodestore.com/pages/athlete-club, https://relodestore.com/collections/leggings, https://relodestore.com/collections/sweatpants, https://relodestore.com/collections/shorts, https://relodestore.com/collections/tops-tank-tops and https://relodestore.com/collections/sport-bras and 9 others use the same meta description. A description written for each page earns more clicks.

https://relodestore.com/pages/athlete-club, https://relodestore.com/collections/leggings, https://relodestore.com/collections/sweatpants, https://relodestore.com/collections/shorts, https://relodestore.com/collections/tops-tank-tops and https://relodestore.com/collections/sport-bras 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 99 found) and read each the way a search engine does.

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

Chrome logged issues while loading the page (“Cookie”).

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

The homepage carries about 1,430 words of visible text.

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 19 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.