shoppinkblush.com website review

68 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).

21 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and SearchSpring and others), adding 6.7 MB and 1.4 s of main-thread time.

pinkblushmaternity.com costs a phone 68 ms of main-thread work and 4.8 MB 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.

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

Google Tag Manager costs a phone 333 ms of main-thread work and 517 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.

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

ZenDesk costs a phone 314 ms of main-thread work and 478 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.

SearchSpring costs a phone 263 ms of main-thread work and 121 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.

Google CDN costs a phone 117 ms of main-thread work and 301 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.

10 long tasks block the main thread while loading, the longest for 229 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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop New Arrivals”.

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

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

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

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

Scripts block taps and scrolling for 403 ms in total while the page loads. Good is under 200 ms.

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 9.7 MB in 441 requests on a phone: images 5.4 MB (60), scripts 2.7 MB (153) and other files 1.0 MB (191). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

13 images (3.5 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example 121965_2_.jpg at 667 px wide, shown at 126 px. Resized copies would save about 271 KiB.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Maternity Clothes | Cute, Stylish & Affordable | PinkBlush Maternity”.

Your canonical URL points to pinkblushmaternity.com, not shoppinkblush.com, so Google may credit that host instead.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.pinkblushmaternity.com)”.

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

The homepage links to 876 pages on shoppinkblush.com and 23 external pages.

https://shoppinkblush.com/pages/coupon-policy has no meta description, so Google writes the search snippet from whatever text it finds.

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

10 images failed to load on a phone, for example https://images.pinkblushmaternity.com/product/large/121872_1_.jpg.

24 of 61 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.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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