rizoscurls.com website review

5 images could be 853 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

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

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

About 55 KiB of CSS is downloaded but never applied 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 (go2sdk.com, Shopify and JSDelivr CDN and others), adding 315 KiB and 2 ms of main-thread time.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.45 (75th percentile). Good is under 0.1.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 143 ms to 145 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 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.5 MB in 100 requests on a phone: images 8.6 MB (55), scripts 511 KiB (34) and fonts 182 KiB (4). Under 2 MB keeps phones on slow connections fast.

RizosCurlsCurlDefiningMoussewithCoconutWater.webp weighs 558 KiB. On a phone connection a single image that size takes seconds.

8 images (2.4 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example 3f0b5349-e037-4b3d-ad2a-564f799c68c3.jpg at 982 px wide, shown at 313 px. Resized copies would save about 41 KiB.

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

10 tap targets are too small or too close together to hit reliably with a finger.

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

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//rizoscurls.com/cdn/shop/files/Logo_50_Smaller_copy.pn…”.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 116 pages on rizoscurls.com and 8 external pages.

https://rizoscurls.com/products/travel-size-bundle, https://rizoscurls.com/pages/blogs, https://rizoscurls.com/pages/rizos-curls-ingredients-new, https://rizoscurls.com/pages/founder-page, https://rizoscurls.com/pages/rizos-curls-sustainability-new and https://rizoscurls.com/pages/rizos-curls-recycle-new and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://rizoscurls.com/products/travel-size-bundle, https://rizoscurls.com/pages/blogs, https://rizoscurls.com/pages/rizos-curls-ingredients-new, https://rizoscurls.com/pages/founder-page, https://rizoscurls.com/pages/rizos-curls-sustainability-new and https://rizoscurls.com/pages/rizos-curls-recycle-new and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 200 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads 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 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.