miadonna.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and okendo.io and others), adding 1.0 MB and 779 ms of main-thread time.

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

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

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.

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

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

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

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

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.

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.

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

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “4 ctw Certified Stud Earrings”.

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

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

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

1 image 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' largest content (lcp) went from 2.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 508 requests on a phone: other files 2.3 MB (238), images 1.6 MB (123) and scripts 1.2 MB (100). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “Shop Lab Grown Diamond Engagement Rings, Wedding Bands & Fine Jewelry”.

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

Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “ld+json block 4 is not valid JSON (Bad control character in string literal in JSON at position )”.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 269 pages on miadonna.com and 29 external pages.

https://www.miadonna.com/pages/lab-grown-diamond-education and https://www.miadonna.com/pages/education all use the title “Lab-Grown Diamond Education | MiaDonna Buying Guide”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.miadonna.com/pages/miadonna-rewards has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miadonna.com/pages/lab-grown-diamond-education and https://www.miadonna.com/pages/education use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.miadonna.com/collections/lab-created-diamonds, whose canonical is https://www.miadonna.com/collections/loose-lab-grown-diamonds. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.miadonna.com/collections/lab-grown-diamond-jewelry, https://www.miadonna.com/collections/lab-grown-diamond-engagement-rings, https://www.miadonna.com/collections/shop-all-wedding, https://www.miadonna.com/collections/lab-grown-diamond-solitaire-engagement-rings and https://www.miadonna.com/collections/lab-grown-diamond-side-stone-engagement-rings have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.miadonna.com/collections/lab-grown-diamond-jewelry and https://www.miadonna.com/collections/shop-all-wedding have 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.

https://www.miadonna.com/collections/lab-created-diamonds, https://www.miadonna.com/pages/lab-grown-diamond-education, https://www.miadonna.com/pages/about-us and https://www.miadonna.com/pages/customer-care took over 3 s to send their HTML from our server.

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

1 error was 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.

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

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.

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

The page uses urgency cues (a countdown or limited-time wording).

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