kollecte.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and omnisnippet1.com and others), adding 2.3 MB and 2.1 s of main-thread time.

YouTube costs a phone 839 ms of main-thread work and 1,019 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 755 ms of main-thread work and 808 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 175 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

14 KiB could be saved by minifying JavaScript.

1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

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.

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

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

Visually, the page fills in at 12.9 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.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 98 ms to 104 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.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.1 MB in 224 requests on a phone: scripts 2.0 MB (104), other files 744 KiB (73) and fonts 666 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

15 elements use ARIA attributes their role does not allow, which confuses screen readers.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

16 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: 5 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 105 pages on kollecte.com and 9 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://kollecte.com/collections/%ED%95%9C%EA%B5%AD-%EC%8A%A4%EB%82%B5, https://kollecte.com/collections/%EB%B9%84%EB%B9%84%EB%93%9C, https://kollecte.com/collections/%EC%A0%95%EA%B4%80%EC%9E%A5, https://kollecte.com/collections/%EB%8D%94%EC%83%98, https://kollecte.com/collections/%ED%95%B4%ED%83%9C and https://kollecte.com/collections/%EB%B9%99%EA%B7%B8%EB%A0%88 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://kollecte.com/products/%EC%98%AC%EB%A6%AC%EB%B8%8C%EC%98%81-%EB%B2%A0%EC%9D%B4%EA%B8%80%EC%B9%A9-2-11oz-4%EA%B0%80%EC%A7%80-%EB%A7%9B, whose canonical is https://kollecte.com/products/%ec%98%ac%eb%a6%ac%eb%b8%8c%ec%98%81-%eb%b2%a0%ec%9d%b4%ea%b8%80%ec%b9%a9-2-11oz-4%ea%b0%80%ec%a7%80-%eb%a7%9b. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://kollecte.com/collections/new/products/%EB%A6%B0%EC%A0%9C%EC%9D%B4-%EB%AA%A8%EB%8D%B8%EB%A7%81%EB%A7%88%EC%8A%A4%ED%81%AC-%EC%BB%B5%ED%8C%A9-1pcs and https://kollecte.com/collections/skin-care-1 took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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

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