remiscalp.com website review

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

13 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, rechargecdn.com and Shopify and others), adding 1.2 MB and 1.0 s of main-thread time.

About 562 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

About 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Klaviyo costs a phone 255 ms of main-thread work and 389 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.

rechargecdn.com costs a phone 217 ms of main-thread work and 296 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.

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

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

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

Your largest element takes 4.8 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 776 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 5.3 MB in 272 requests on a phone: images 2.7 MB (39), scripts 1.5 MB (87) and other files 859 KiB (130). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example IMG_1291.heic at 3,024 px wide, shown at 306 px. Resized copies would save about 1.6 MB.

Banner_0001.jpg 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).

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 71 pages on remiscalp.com and 11 external pages.

https://remiscalp.com/en-us and https://remiscalp.com/en-us/products/energy-reset-duo all use the title “Remi - Scalp Care | Born In Ireland”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://remiscalp.com/en-us/collections/all, https://remiscalp.com/en-us/pages/faqs, https://remiscalp.com/en-us/pages/subscribe-save, https://remiscalp.com/en-us/pages/about, https://remiscalp.com/en-us/pages/contact and https://remiscalp.com/en-ie/collections/all and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://remiscalp.com/en-ie/collections/all, whose canonical is https://remiscalp.com/en-us/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://remiscalp.com/en-us/collections/all, https://remiscalp.com/en-us/pages/faqs, https://remiscalp.com/en-us/pages/subscribe-save, https://remiscalp.com/en-us/pages/about, https://remiscalp.com/en-us/pages/contact and https://remiscalp.com/en-ie/collections/all and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

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