mayabrenner.com website review

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

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

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

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

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

8 third-party services load with your homepage (Shopify, Attentive and monkcommerce.app and others), adding 1.5 MB and 749 ms of main-thread time.

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

About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

15 KiB could be saved by minifying CSS.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gold asymmetrical initial necklace with M, J, D, a heart an…”.

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

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

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

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

Your homepage downloads 5.3 MB in 450 requests on a phone: scripts 1.9 MB (150), images 1.5 MB (30) and other files 1.2 MB (220). Under 2 MB keeps phones on slow connections fast.

mobile-menu-initial-birthstone-3x2.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).

2 images (211 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.

2 images further down the page (75 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Headings skip levels (h2 → h6), 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 meta description is 246 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 175 pages on mayabrenner.com and 7 external pages.

/collections/birthstone-necklaces-1 has no <title>, so Google invents the link text in results.

/collections/birthstone-necklaces-1 has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/personalized-bracelets, /collections/personalized-rings, /collections/personalized-earrings, /collections/necklaces-shop-all, /collections/necklaces-custom-letter-charm and /collections/necklaces-classic-layering-chains and 4 others use the same meta description. A description written for each page earns more clicks.

/collections/initial-necklaces, /collections/best-sellers-shop-all, /collections/shop-all-personalized, /collections/personalized-necklaces, /collections/personalized-rings and /collections/personalized-earrings and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://mayabrenner.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

5 errors were logged to the browser console while the page loaded, for example “document.addEventListener(...) is not a function”.

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

Before a visitor clicks anything, the page loads 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 21 cookies, 2 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.