vivaia.kr website review

21 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, Yotpo and ptengine.com and others), adding 1.8 MB and 1.1 s of main-thread time.

About 640 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

Shopify costs a phone 683 ms of main-thread work and 1.1 MB 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 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

7 KiB could be saved by minifying CSS.

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.

5 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

6 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 127 ms to 131 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 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 314 requests on a phone: images 2.5 MB (55), scripts 1.3 MB (83) and other files 769 KiB (104). Under 2 MB keeps phones on slow connections fast.

banner-en-m-a_5.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).

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 109 pages on vivaia.kr and 7 external pages.

https://www.vivaia.kr/collections/all, https://www.vivaia.kr/pages/vivaia-august-sale, https://www.vivaia.kr/pages/korea-warehouse-shoes, https://www.vivaia.kr/pages/new-arrivals, https://www.vivaia.kr/collections/best-sellers and https://www.vivaia.kr/collections/%EC%8A%A4%EB%8B%88%EC%BB%A4%EC%A6%88 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.vivaia.kr/collections/%ED%8E%B8%EC%95%88%ED%95%A8%EA%B3%BC-%EC%8A%A4%ED%83%80%EC%9D%BC%EC%9D%84-%ED%92%88%EC%9D%80-%EC%8A%88%EC%A6%88, whose canonical is https://www.vivaia.kr/collections/%ed%8e%b8%ec%95%88%ed%95%a8%ea%b3%bc-%ec%8a%a4%ed%83%80%ec%9d%bc%ec%9d%84-%ed%92%88%ec%9d%80-%ec%8a%88%ec%a6%88. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.vivaia.kr/collections/all, https://www.vivaia.kr/pages/korea-warehouse-shoes, https://www.vivaia.kr/pages/the-other-side-of-nature, https://www.vivaia.kr/pages/new-arrivals, https://www.vivaia.kr/collections/best-sellers and https://www.vivaia.kr/collections/%ED%8E%B8%EC%95%88%ED%95%A8%EA%B3%BC-%EC%8A%A4%ED%83%80%EC%9D%BC%EC%9D%84-%ED%92%88%EC%9D%80-%EC%8A%88%EC%A6%88 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vivaia.kr/collections/all, https://www.vivaia.kr/pages/the-other-side-of-nature, https://www.vivaia.kr/collections/best-sellers, https://www.vivaia.kr/collections/%ED%8E%B8%EC%95%88%ED%95%A8%EA%B3%BC-%EC%8A%A4%ED%83%80%EC%9D%BC%EC%9D%84-%ED%92%88%EC%9D%80-%EC%8A%88%EC%A6%88, https://www.vivaia.kr/collections/%EC%9A%B4%EB%8F%99%ED%99%94%EB%B3%B4%EB%8B%A4-%ED%8E%B8%ED%95%9C-%ED%94%8C%EB%9E%AB%EC%8A%88%EC%A6%88 and https://www.vivaia.kr/collections/%EC%9A%B4%EB%8F%99%ED%99%94%EC%B2%98%EB%9F%BC-%ED%8E%B8%ED%95%9C-%EB%A1%9C%ED%8D%BC%EC%8A%88%EC%A6%88/%EC%8B%A0%EB%B0%9C and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.vivaia.kr/pages/korea-warehouse-shoes and https://www.vivaia.kr/collections/%EB%9F%B0%EB%8B%9D%ED%9E%90/%EC%8B%A0%EB%B0%9C took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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 Ads, Google Analytics, 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 15 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.