rheafashion.com website review

hcaptcha.com costs a phone 5.1 s of main-thread work and 4.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

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

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Google CDN and customerfields.com and others), adding 7.3 MB and 6.2 s of main-thread time.

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

Google CDN costs a phone 647 ms of main-thread work and 774 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.

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

6 images could be 88 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.

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

5 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

7 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

6 images 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 9.2 MB in 166 requests on a phone: scripts 4.2 MB (68), HTML 1.8 MB (11) and media 1.8 MB (1). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

14 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h6, h2 → h4 and 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.

284 links have no real href, so search engines can't follow them.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 463 pages on rheafashion.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://rheafashion.com/cdn/shop/files/HV_Florentino_Regular.ttf?v=1718611736' because its…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 customer or partner logo. 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 382 words of visible text.

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