roseforever.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and TikTok and others), adding 1.2 MB and 836 ms of main-thread time.

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

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

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

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

Google Tag Manager costs a phone 285 ms of main-thread work and 334 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,866 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

videowise.com costs a phone 52 ms of main-thread work and 319 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.

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

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

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

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

14 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 273 requests on a phone: scripts 1.5 MB (93), other files 799 KiB (123) and images 750 KiB (37). Under 2 MB keeps phones on slow connections fast.

HO_01_MOBILE.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).

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

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

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

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

The homepage links to 146 pages on roseforever.com and 4 external pages.

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

1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0046/6731/0173/t/51/assets/roseplus_1024x1024.png?v=128893433044797054631680768774.

4 errors were logged to the browser console while the page loaded, for example “Refused to execute script from 'https://p.veritone-ce.com/11c4e575-9c01-4242-afc8-88f39d039d27?ts=98&url=https://rosefo…”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 605 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, Klaviyo and Meta Pixel and 3 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 29 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 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.