oudroma.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and rapidsearch.dev and others), adding 4.4 MB and 347 ms of main-thread time.

11 images could be 276 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.

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

b-cdn.net costs a phone 0 ms of main-thread work and 3.8 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.

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

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

Klaviyo costs a phone 147 ms of main-thread work and 313 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 files are served with short cache lifetimes, so returning visitors download them again (63 KiB).

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

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

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

2 KiB JavaScript is shipped twice across bundles.

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

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

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

3 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 128 ms to 126 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 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 323 requests on a phone: media 3.2 MB (1), images 1.3 MB (32) and other files 941 KiB (146). Under 2 MB keeps phones on slow connections fast.

Diseno_sin_titulo_33.png 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).

1 image (40 KiB) is 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 1.87 g of CO₂e: 224.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

5 images have no alt text, which hurts accessibility and image search.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 17 characters: “OudRoma – Oudroma”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 76 pages on oudroma.com and 4 external pages.

https://oudroma.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://oudroma.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://oudroma.com/collections/all, https://oudroma.com/customer_authentication/redirect, https://oudroma.com/policies/shipping-policy, https://oudroma.com/collections/mas-vendidos, https://oudroma.com/collections/perfumes-arabes and https://oudroma.com/collections/perfumes-de-disenador and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://oudroma.com/customer_authentication/redirect and https://oudroma.com/pages/mayoreo have no <h1> headline, so visitors and search engines get no clear main topic.

https://oudroma.com/customer_authentication/redirect, https://oudroma.com/products/lattafa-yara-edp-100ml and https://oudroma.com/collections/mas-vendidos took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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 3,331 words of visible text.

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