takingshape.com website review

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 700 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.

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

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

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

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

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

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

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

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

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

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.

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 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Buy & Save - up to 40% off*”.

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

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

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

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 4.4 MB in 158 requests on a phone: scripts 2.4 MB (60), images 1.4 MB (34) and stylesheets 208 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

14 buttons have no accessible name, so screen readers announce just “button”.

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Headings should not be empty: 24 elements on the page fail this check, rated minor by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (8 elements).

There are 2 <h1> headlines (“SELECTED STYLES $49 & UNDER* Shop Now” and “Plus Size Clothing Australia”). One clear main headline is easier for people and search engines.

Structured data found (FAQPage and Organization) but with 1 problem, for example “Organization: missing name”.

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

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

The homepage links to 580 pages on takingshape.com and 4 external pages.

There is no /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.

/AU/storelocator, /AU/new-in/dresses, /AU/new-in/pants, /AU/new-in/denim-and-jeans, /AU/new-in/knitwear and /AU/new-in/sleepwear all use the title “Sites-TakingShapeAU-Site”. Search engines can't tell which page to show for a search, so each competes with the others.

/AU/storelocator, /AU/new-in/dresses, /AU/new-in/pants, /AU/new-in/denim-and-jeans, /AU/new-in/knitwear and /AU/new-in/sleepwear have no meta description, so Google writes the search snippet from whatever text it finds.

/AU/storelocator, /AU/new-in/dresses, /AU/new-in/pants, /AU/new-in/denim-and-jeans, /AU/new-in/knitwear and /AU/new-in/sleepwear have no <h1> headline, so visitors and search engines get no clear main topic.

/AU/new-in/denim-and-jeans took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 156 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=11005466&tm=gtm002&Ver=2&mid=8ec324d0-5957-4cd7-881a-24555ba2f5e8&bo=1&sid=ce4ee020d85c11f1b53bed720610467b&vid=ce4f21b0d85c11f1a46e83074c852922&vids=1&msclkid=N&pi=91.

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

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 “ReferenceError: _etmc is not defined”.

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 30 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://takingshape.com/AU/storelocator?showMap=true&isForm=true.

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.

takingshape.com is registered until Feb 2027. Make sure auto-renew is on and the card on file is current.

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

takingshape.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 1 trust badge. 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 465 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 Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 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 29 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.