remmiebyriley.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, omnisnippet1.com and gotolstoy.com and others), adding 1.5 MB and 870 ms of main-thread time.

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

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

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

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

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

Polyfills for old browsers add 28 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.

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile_565750df-ebcf-4fd6-9563-0f6ae86f9e79.png”.

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

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

The layout shifts by 0.45 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 556 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 104 ms to 112 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.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 361 requests on a phone: images 2.5 MB (63), scripts 1.6 MB (93) and other files 1.4 MB (179). Under 2 MB keeps phones on slow connections fast.

7 images (338 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.64 g of CO₂e: 196.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 elements hidden from screen readers can still receive keyboard focus.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is 79 characters, so Google will cut it off around 60: “REMMIE BY RILEY | Riley Hemson | Women's Lounge & Leisurewear – Remmie By Riley”.

There are 6 <h1> headlines (“”, “Good Days” and “Fleece”). One clear main headline is easier for people and search engines.

Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 249 pages on remmiebyriley.com and 5 external pages.

https://remmiebyriley.com/pages/black-friday-landing-page-swim-boxes, https://remmiebyriley.com/collections, https://remmiebyriley.com/collections/good-days, https://remmiebyriley.com/collections/in-motion, https://remmiebyriley.com/collections/lime-sorbet and https://remmiebyriley.com/collections/fleece use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://remmiebyriley.com/collections/new-arrivals/New-Arrivals, whose canonical is https://remmiebyriley.com/collections/new-arrivals. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

16 of 74 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: the server responded with a status of 404 ()”.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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