madebymary.com website review

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

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

32 images could be 991 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.

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

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

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

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

7 third-party services load with your homepage (Shopify, cloudfront.net and Google Fonts and others), adding 143 KiB and 35 ms of main-thread time.

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

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.

Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A blonde woman with a warm maroon background wearing multip…”.

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

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

Real visitors wait 858 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 7.2 MB in 328 requests on a phone: images 5.4 MB (148), other files 733 KiB (82) and fonts 455 KiB (10). Under 2 MB keeps phones on slow connections fast.

initial-disc-necklace-1-4-necklace-13512737062985.gif weighs 550 KiB. On a phone connection a single image that size takes seconds.

made-by-mary-earring-ember-baguette-drop-hoop-gold-onfigure- 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).

3 images (935 KiB) 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.

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

Your title is 85 characters, so Google will cut it off around 60: “Hand Stamped Disc Necklaces, Personalized Bar Necklaces | Made by Mary – Made By Mary”.

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

Structured data found (JewelryStore and Organization) but with 1 problem, for example “Organization: url points at a different host (https://checkout.madebymary.com)”.

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

Your <h1> is empty.

The homepage links to 244 pages on madebymary.com and 9 external pages.

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

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

5 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,060 words of visible text.

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