enchantedcorset.com website review

About 408 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 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.

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

8 third-party services load with your homepage (channel.io, Google Tag Manager and Clarity and others), adding 994 KiB and 756 ms of main-thread time.

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

channel.io costs a phone 333 ms of main-thread work and 334 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 2.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Tag Manager costs a phone 157 ms of main-thread work and 299 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 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 39.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “0:00”.

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

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

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

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

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 8.4 MB in 215 requests on a phone: fonts 5.8 MB (2), scripts 1.2 MB (49) and other files 824 KiB (133). Under 2 MB keeps phones on slow connections fast.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “ENCHANTED CORSET”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 24 pages on enchantedcorset.com and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://enchantedcorset.com/collections/corset/products/oc00005 and https://enchantedcorset.com/products/oc00005 all use the title “【Made in Japan】Sirene| CORSET – ENCHANTED CORSET”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://enchantedcorset.com/collections/all, https://enchantedcorset.com/pages/recovery-story and https://enchantedcorset.com/pages/corset-knowledge have no meta description, so Google writes the search snippet from whatever text it finds.

https://enchantedcorset.com/collections/corset/products/oc00005 and https://enchantedcorset.com/products/oc00005 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://enchantedcorset.com/collections/corset/products/oc00005, whose canonical is https://enchantedcorset.com/products/oc00005. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://enchantedcorset.com/pages/recovery-story, https://enchantedcorset.com/pages/corset-knowledge and https://enchantedcorset.com/pages/faq-1 have no <h1> headline, so visitors and search engines get no clear main topic.

https://enchantedcorset.com/collections/all has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

The homepage has only about 161 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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