riamiranda.com website review

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

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

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

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

Shopify costs a phone 181 ms of main-thread work and 403 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,016 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Shopify, growave.io and qiscus.com and others), adding 859 KiB and 435 ms of main-thread time.

About 157 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 110 ms faster on a phone.

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

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

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

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

11 KiB could be saved by minifying CSS.

Desktop scores 82 but mobile only 41. 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.

3 KiB could be saved by minifying JavaScript.

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

The layout shifts by 0.63 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 3.8 MB in 319 requests on a phone: images 1.8 MB (49), scripts 1,005 KiB (153) and other files 763 KiB (101). Under 2 MB keeps phones on slow connections fast.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

Document should not have more than one main landmark: 1 element on the page fails 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is only 10 characters: “RiaMiranda”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

6 links have no real href, so search engines can't follow them.

The homepage links to 167 pages on riamiranda.com and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://riamiranda.com/pages/riamiranda-signature, https://riamiranda.com/collections/denim-series, https://riamiranda.com/collections/riamiranda-x-melahyar, https://riamiranda.com/collections/online-exclusive, https://riamiranda.com/collections/sura-fall-2026 and https://riamiranda.com/collections/new-in and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://riamiranda.com/pages/riamiranda-signature, https://riamiranda.com/collections/denim-series, https://riamiranda.com/collections/riamiranda-x-melahyar, https://riamiranda.com/collections/online-exclusive, https://riamiranda.com/collections/sura-fall-2026 and https://riamiranda.com/collections/new-in and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d38dvuoodjuw9x.cloudfront.net/ml-flag.css' from origin 'https://riamiranda.com' ha…”.

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

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