originalremi.com website review

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

5 third-party services load with your homepage (hcaptcha.com, Shopify and shop.app and others), adding 4.3 MB and 1.5 s of main-thread time.

hcaptcha.com costs a phone 922 ms of main-thread work and 1.2 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.

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

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

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

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

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Original remi bundle hair”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.8 MB in 544 requests on a phone: images 3.2 MB (48), scripts 2.1 MB (254) and other files 1.5 MB (177). Under 2 MB keeps phones on slow connections fast.

BlackDiamond_TapeIn_mockup.png 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).

2 images are downloaded at several times the size a phone draws them, for example orbundle-wide.jpg at 2,000 px wide, shown at 360 px. Resized copies would save about 159 KiB.

1 image further down the page (22 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 2.21 g of CO₂e: 265.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is only 13 characters: “Original Remi”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “DIY”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 200 pages on originalremi.com and 11 external pages.

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

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

https://www.originalremi.com/collections/all, https://www.originalremi.com/customer_authentication/redirect, https://www.originalremi.com/collections/new-bestsellers, https://www.originalremi.com/policies/shipping-policy, https://www.originalremi.com/pages/originalremi-store-locator and https://www.originalremi.com/pages/apply-for-b2b-account and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.originalremi.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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