rodial.com website review

126 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).

About 975 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Yotpo and Klaviyo and others), adding 3.2 MB and 2.4 s of main-thread time.

Google Tag Manager costs a phone 815 ms of main-thread work and 648 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.

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

Yotpo costs a phone 458 ms of main-thread work and 1.4 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.

29 KiB could be saved by minifying JavaScript.

Klaviyo costs a phone 303 ms of main-thread work and 344 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 265 ms of main-thread work and 293 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.

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

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

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

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

11 KiB JavaScript is shipped twice across bundles.

Desktop scores 54 but mobile only 27. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 16.9 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 18.8 s (Speed Index). Good is under 3.4 s.

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

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

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

Real visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 9.5 MB in 431 requests on a phone: images 5.1 MB (143), scripts 2.7 MB (124) and other files 797 KiB (135). Under 2 MB keeps phones on slow connections fast.

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

By the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 323.2 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.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Structured data found (WebSite) but with 2 problems, for example “WebSite: logo is not an absolute URL ("//www.rodial.com/cdn/shop/files/rodial-logo-digital-only-202…”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 221 pages on rodial.com and 8 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://www.rodial.com/pages/subscribe-and-save has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rodial.com/collections/shop-all-skincare, https://www.rodial.com/collections/glass-skin, https://www.rodial.com/pages/travel-minis-bundle-builder, https://www.rodial.com/pages/ai-skin-assistant, https://www.rodial.com/pages/subscribe-and-save and https://www.rodial.com/pages/the-peel-range and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rodial.com/collections/shop-all-skincare has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/instagram/56/18117758635933956/standard_resolution.jpg?format=webp&fit=crop&height=352&width=352.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

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

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