mykitsch.es website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Clarity and others), adding 1.1 MB and 813 ms of main-thread time.

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

Shopify costs a phone 377 ms of main-thread work and 409 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.

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

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

Klaviyo costs a phone 152 ms of main-thread work and 416 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 250 KiB of JavaScript is downloaded but never used on this page.

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

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

12 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.8 MB in 374 requests on a phone: scripts 1.4 MB (154), images 1.0 MB (54) and other files 896 KiB (142). Under 2 MB keeps phones on slow connections fast.

Cat_in_the_Hat_-_Mobile_-_no_copyright_text.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.08 g of CO₂e: 129.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

Your meta description is 216 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

The homepage links to 272 pages on mykitsch.es and 10 external pages.

https://www.mykitsch.com/collections/bfcm-bogo-pillowcases is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.mykitsch.com/pages/bundles-1, https://www.mykitsch.com/collections/bfcm-bogo-pillowcases, https://www.mykitsch.com/collections/holiday-arrivals, https://www.mykitsch.com/pages/lisa-frank, https://www.mykitsch.com/pages/grinch-collection and https://www.mykitsch.com/pages/take-the-kitsch-quiz and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mykitsch.com/collections/best-sellers, https://www.mykitsch.com/pages/hair-body-care-from-kitsch, https://www.mykitsch.com/pages/bundles-1, https://www.mykitsch.com/collections/bfcm-bogo-pillowcases, https://www.mykitsch.com/pages/cat-in-the-hat and https://www.mykitsch.com/collections/holiday-arrivals 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 136 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://segment.prod.bidr.io/associate-segment?buzz_key=tatari&segment_key=tatari-8843&value=&uncacheplz=1558538238.

4 errors were logged to the browser console while the page loaded, for example “Fetch error: TypeError: Failed to fetch”.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 809 words of visible text.

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