shapermint.com website review

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 885 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

12 images could be 434 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.

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

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

Insider costs a phone 276 ms of main-thread work and 321 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.

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

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

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.

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

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

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

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

Real visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 237 ms to 295 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The layout shifts by 0.126 while loading, so content jumps under the reader's thumb. Good is under 0.1.

5 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' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 299 requests on a phone: scripts 4.9 MB (89), images 594 KiB (41) and other files 566 KiB (152). Under 2 MB keeps phones on slow connections fast.

6 images (312 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.8 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 tap target is too small or too close together to hit reliably with a finger.

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

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

Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

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

The homepage links to 102 pages on shapermint.com and 9 external pages.

/collections/best-sellers, /collections/shapewear, /collections/bras, /collections/tanks-camis, /collections/leggings and /collections/bodysuits and 6 others took over 3 s to send their HTML from our server.

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

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 297 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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