exotik.store website review

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

8 third-party services load with your homepage (PayPal, Google Tag Manager and Shopify and others), adding 1.5 MB and 660 ms of main-thread time.

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

PayPal costs a phone 194 ms of main-thread work and 390 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.

Shopify costs a phone 145 ms of main-thread work and 597 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 Tag Manager costs a phone 171 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

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

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

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

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

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

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

Your homepage downloads 4.5 MB in 357 requests on a phone: images 1.6 MB (62), scripts 1.2 MB (118) and other files 1.0 MB (157). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Comparisson_14_3_2000x.png at 2,000 px wide, shown at 390 px. Resized copies would save about 270 KiB.

5 images further down the page (469 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Alternative text of images should not be repeated as text: 5 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.

Your page has no <title>, so Google has to invent the blue link in search results.

There are 5 <h1> headlines (“Exotik Store”, “Combo Mascara De Pestañas Exotic + Removedor - Pi…” and “Combo Mascara De Pestañas Exotic + Removedor - Pi…”). One clear main headline is easier for people and search engines.

The homepage links to 269 pages on exotik.store and 16 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://exotik.store/collections/%E2%9C%A8nuevo-en-la-pagina%E2%9C%A8, https://exotik.store/collections/maquillaje, https://exotik.store/collections/rostro, https://exotik.store/collections/bases, https://exotik.store/collections/polvo-compacto and https://exotik.store/collections/rostro/Corrector and 9 others have no <title>, so Google invents the link text in results.

https://exotik.store/collections/%E2%9C%A8nuevo-en-la-pagina%E2%9C%A8, https://exotik.store/collections/maquillaje, https://exotik.store/collections/bases, https://exotik.store/collections/polvo-compacto, https://exotik.store/collections/iluminador-bronceador-contorneador and https://exotik.store/collections/primer-fijador and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://exotik.store/collections/rostro, https://exotik.store/collections/rostro/Corrector and https://exotik.store/collections/rostro/Rubor 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://exotik.store/collections/%E2%9C%A8nuevo-en-la-pagina%E2%9C%A8, whose canonical is https://exotik.store/collections/%e2%9c%a8nuevo-en-la-pagina%e2%9c%a8. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://exotik.store/collections/%E2%9C%A8nuevo-en-la-pagina%E2%9C%A8, https://exotik.store/collections/maquillaje, https://exotik.store/collections/rostro, https://exotik.store/collections/bases, https://exotik.store/collections/polvo-compacto and https://exotik.store/collections/rostro/Corrector and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

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