timeleaf.co.kr website review

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

10 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

The page goes through 1 redirect before it starts loading, costing about 2.7 s. Link and advertise the final URL directly.

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

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

8 third-party services load with your homepage (Shopify, bestfreecdn.com and b-cdn.net and others), adding 2.5 MB and 1.9 s of main-thread time.

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

bestfreecdn.com costs a phone 520 ms of main-thread work and 852 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.

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

b-cdn.net costs a phone 480 ms of main-thread work and 810 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.

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

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

1 image could be 8 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.

About 73 KiB of CSS is downloaded but never applied on this page.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

Your homepage downloads 6.0 MB in 591 requests on a phone: scripts 3.1 MB (134), images 1.6 MB (242) and other files 868 KiB (157). Under 2 MB keeps phones on slow connections fast.

ca943297-5b10-4e31-87f3-c21334da6b81.png 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).

4 images are downloaded at several times the size a phone draws them, for example ac.svg at 1,000 px wide, shown at 24 px. Resized copies would save about 335 KiB.

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

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

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

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

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

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

There are 3 <h1> headlines (“”, “Leading Distributor of Aesthetic and Cosmetic Pro…” and “Global Beauty, Direct to You”). One clear main headline is easier for people and search engines.

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

The homepage links to 65 pages on timeleaf.co.kr and 4 external pages.

There is no https://timeleaf.co.kr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://timeleaf.co.kr/collections/collagen-regeneraion-pdrn-pla-plla-pcl-ca and https://timeleaf.co.kr/collections/iv-injection are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://timeleaf.co.kr/collections/collagen-regeneraion-pdrn-pla-plla-pcl-ca and https://timeleaf.co.kr/collections/iv-injection all use the title “Professionals Only – TIMELEAF”. Search engines can't tell which page to show for a search, so each competes with the others.

https://timeleaf.co.kr/pages/our-story, https://timeleaf.co.kr/pages/faq-1, https://timeleaf.co.kr/collections/collagen-regeneraion-pdrn-pla-plla-pcl-ca and https://timeleaf.co.kr/collections/iv-injection have no meta description, so Google writes the search snippet from whatever text it finds.

https://timeleaf.co.kr/pages/our-story, https://timeleaf.co.kr/pages/faq-1, https://timeleaf.co.kr/pages/shipping-policy, https://timeleaf.co.kr/collections/collagen-regeneraion-pdrn-pla-plla-pcl-ca and https://timeleaf.co.kr/collections/iv-injection have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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 Analytics, Google Tag Manager, LinkedIn Insight 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 18 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.