piercedco.com website review

About 337 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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, omnisnippet1.com and loox.io and others), adding 991 KiB and 786 ms of main-thread time.

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

28 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

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

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

43 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

2 images 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' tap response (inp) went from 82 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 178 requests on a phone: images 1.1 MB (20), other files 1.1 MB (72) and scripts 910 KiB (72). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 81 characters, so Google will cut it off around 60: “Best hypoallergenic screwback earrings for girls with sensitive ears – Pierced Co”.

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

Your <h1> is empty.

The homepage links to 119 pages on piercedco.com and 5 external pages.

There is no https://www.piercedco.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.piercedco.com/pages/pierced-subscription, https://www.piercedco.com/collections/polly-pocket-x-pierced and https://www.piercedco.com/collections/halloween-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.piercedco.com/pages/pierced-subscription has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.piercedco.com/collections/polly-pocket-x-pierced took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-app.sealsubscriptions.com/shopify/public/css/style.css?shop=knotted-bow-co.mys…”.

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 carries about 828 words of visible text.

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