rosierees.com website review

8 third-party services load with your homepage (route.com, Klaviyo and rebuyengine.com and others), adding 1.5 MB and 1.1 s of main-thread time.

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

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

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

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

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

route.com costs a phone 424 ms of main-thread work and 542 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.

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

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

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

rebuyengine.com costs a phone 193 ms of main-thread work and 332 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.

6 images could be 165 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 70 KiB of CSS is downloaded but never applied on this page.

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

6 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.

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

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

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

26 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 3.3 MB in 200 requests on a phone: scripts 1.6 MB (67), images 818 KiB (22) and other files 698 KiB (96). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Your title is 81 characters, so Google will cut it off around 60: “Founder and CEO of Yoni Pleasure Palace, Splash Blanket & Yinn Body. – rosie rees”.

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

The homepage links to 114 pages on rosierees.com and 31 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.

https://rosierees.com/en-us/collections/clearance, https://rosierees.com/en-us/collections/shop-all, https://rosierees.com/en-us/collections/whats-new, https://rosierees.com/en-us/collections/blankets, https://rosierees.com/en-us/collections/glass-wands and https://rosierees.com/en-us/collections/vibrators and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://rosierees.com/en-us/collections/blankets has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Load widget data error: Failed to execute 'json' on 'Response': Unexpected end of JSON input”.

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

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

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