shapees-uk.com website review

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

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

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

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

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

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

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

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

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

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

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

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

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

10 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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.7 MB in 256 requests on a phone: scripts 2.4 MB (94), other files 915 KiB (102) and fonts 593 KiB (8). Under 2 MB keeps phones on slow connections fast.

US_Main_mob_2x_766f8fa1-8ad8-4c2b-bbc5-26ac03b8dc81.jpg 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).

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Google's crawler is blocked from indexing this page.

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

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 116 pages on shapees-uk.com and 32 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Your homepage links to /collections/panties, /pages/club-membership-subscription and /pages/about-us, which answer with an error. Visitors hit a dead end and search engines drop them.

/collections/bras, /collections/leggings, /collections/swimwear, /collections/4th-of-july-sale, /collections/shapewear and /collections/new-arrivals and 1 other all use the title “Shapermint Collection | Bras, Shapewear, Leggings, Undies for Every B…”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/bras, /collections/leggings, /collections/swimwear, /collections/4th-of-july-sale, /collections/shapewear and /collections/new-arrivals and 1 other use the same meta description. A description written for each page earns more clicks.

/collections/butt-lifters has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26005098&tm=gtm002&Ver=2&mid=3620f3c2-b771-4517-b184-a83b01e957fc&bo=1&sid=909c9100db0611f1a3e3791ca0936a02&vid=909cb170db0611f19fd35bf8bce529f0&vids=1&msclkid=N&pi=91.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

5 errors were logged to the browser console while the page loaded, for example “your_user_id is not defined”.

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

9 links from your homepage to your own site are broken, for example https://store.shapees.com/collections/panties (503).

2 links to other sites are dead, for example https://shapees.com/account?view=information (503).

HSTS is set, but max-age is 91 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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

shapees.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

shapees-uk.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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 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 24 cookies, 1 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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.