peachymean.com website review

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

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

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

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

2 third-party services load with your homepage (Shopify and shop.app), adding 66 KiB and 38 ms of main-thread time.

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

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.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.1 MB in 205 requests on a phone: images 996 KiB (25), other files 831 KiB (112) and scripts 176 KiB (37). Under 2 MB keeps phones on slow connections fast.

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

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

Your meta description is only 57 characters: “Jewelry and home goods handmade at home in Austin, Texas.”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 40 pages on peachymean.com and 7 external pages.

/collections/all and /pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

/products/darcy-earrings and /products/piper-earrings use the same meta description. A description written for each page earns more clicks.

/pages/contact has 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.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

Opening the homepage sets 6 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.