pipercleo.com website review

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

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

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

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

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

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

12 images could be 263 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

8 third-party services load with your homepage (reamaze.com, Yotpo and Mouseflow and others), adding 764 KiB and 422 ms of main-thread time.

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

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

7 KiB could be saved by minifying CSS.

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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

26 images have no width and height attributes, so the layout jumps as each one loads.

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 4.5 MB in 388 requests on a phone: images 2.1 MB (88), other files 1.0 MB (185) and scripts 911 KiB (77). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (288 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.29 g of CO₂e: 154.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

1 element hidden from screen readers can still receive keyboard focus.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is 85 characters, so Google will cut it off around 60: “Piper Cleo Jewelry - PiperCelo.com Jewelry that feeds made in the USA – pipercleo.com”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 69 characters: “Piper Cleo Jewelry - PiperCelo.com Jewelry that feeds made in the USA”. 70 to 160 characters is enough to sell the click.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 193 pages on pipercleo.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.pipercleo.com/pages/customer-photos, https://www.pipercleo.com/collections/solidarity, https://www.pipercleo.com/collections/nevertheless-she-persisted-jewelry-and-more, https://www.pipercleo.com/collections/reclaiming-my-time, https://www.pipercleo.com/collections/naturally-beautiful and https://www.pipercleo.com/collections/bridal and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pipercleo.com/pages/customer-photos, https://www.pipercleo.com/pages/share, https://www.pipercleo.com/collections/solidarity, https://www.pipercleo.com/collections/nevertheless-she-persisted-jewelry-and-more, https://www.pipercleo.com/collections/reclaiming-my-time and https://www.pipercleo.com/collections/naturally-beautiful and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pipercleo.com/pages/customer-photos and https://www.pipercleo.com/pages/share 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.

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

11 of 43 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 (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'apply')”.

Social proof on the homepage: 36 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 190 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.

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