kollecteusa.com website review

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

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

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

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

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

Shopify costs a phone 621 ms of main-thread work and 1,006 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.

YouTube costs a phone 595 ms of main-thread work and 1,000 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 174 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.

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

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

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

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

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

Polyfills for old browsers add 7 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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 12.0 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 23.2 s. Good is under 3.8 s.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 103 ms to 114 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).

Your homepage downloads 4.1 MB in 244 requests on a phone: scripts 2.0 MB (109), other files 1.0 MB (95) and fonts 600 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

6 elements hidden from screen readers can still receive keyboard focus.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

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

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

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

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

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

The homepage links to 118 pages on kollecteusa.com and 5 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.

Your homepage links to https://kollecteusa.com/collections/kollecte-new-arrival, which answers with an error. Visitors hit a dead end and search engines drop it.

https://kollecteusa.com/collections/dongwon-vivid, https://kollecteusa.com/collections/the-saem, https://kollecteusa.com/collections/ssueim and https://kollecteusa.com/collections/adjustable-collection have no meta description, so Google writes the search snippet from whatever text it finds.

https://kollecteusa.com/products/kf94-cleantop-white-adj, https://kollecteusa.com/products/evergreen-kf94-cleantop-adjustable-strap-kids-smallwhite-pn95, https://kollecteusa.com/products/evergreen-kf94-cleantop-adjustable-straps-kids-smallblack-pn95, https://kollecteusa.com/products/%EC%97%90%EB%B2%84%EA%B7%B8%EB%A6%B0%ED%81%AC%EB%A6%B0%ED%83%91kf94-%EB%81%88%EC%A1%B0%EC%A0%88-%EA%B2%80%EC%A0%95-%EC%86%8C%ED%98%95 and https://kollecteusa.com/products/%EC%97%90%EB%B2%84%EA%B7%B8%EB%A6%B0%ED%81%AC%EB%A6%B0%ED%83%91kf94-%EB%81%88%EC%A1%B0%EC%A0%88-%EB%B8%94%EB%9E%99-50-%ED%9D%B0%EC%83%89-50%EB%8C%80%ED%98%95 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://kollecteusa.com/collections/kollecte-new-arrival/products/lindsay-modeling-mask-cup-pack-28g-6ea, whose canonical is https://kollecteusa.com/products/lindsay-modeling-mask-cup-pack-28g-6ea. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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 595 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, Google Tag Manager 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 21 cookies, 2 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.