pinkcherry.com website review

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

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

Your mobile performance score is 56 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

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

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

Klaviyo costs a phone 99 ms of main-thread work and 310 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.

Optanon costs a phone 81 ms of main-thread work and 380 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.

8 third-party services load with your homepage (Klaviyo, Optanon and jQuery CDN and others), adding 901 KiB and 301 ms of main-thread time.

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

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

About 20 KiB of CSS is downloaded but never applied 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.

3 KiB could be saved by minifying JavaScript.

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 14.3 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 14.6 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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-03, real Chrome visitors' tap response (inp) went from 95 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 241 requests on a phone: images 3.2 MB (37), scripts 838 KiB (83) and other files 741 KiB (85). Under 2 MB keeps phones on slow connections fast.

MainBanner-PC-US-Mobile-08Oct26.gif 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 (331 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 384 pages on pinkcherry.com and 25 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies (measured from a US location before any click).

Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.