shopieum.com website review

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

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

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

About 310 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

192 KiB could be saved by minifying JavaScript.

About 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (pstatic.net, poxo.com and kakaocdn.net and others), adding 296 KiB and 131 ms of main-thread time.

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

Your largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “26416_메인배너_m_01”.

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

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

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

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

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

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

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 8.1 MB in 58 requests on a phone: images 3.9 MB (20), fonts 3.0 MB (5) and scripts 962 KiB (18). Under 2 MB keeps phones on slow connections fast.

9dd7a8162f09a787b1d2f7c8eefecb61.jpg weighs 594 KiB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example 328803f23190743d1776dde90c3ccff6.jpg at 1,000 px wide, shown at 175 px. Resized copies would save about 932 KiB.

13 images (3.9 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

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

The skip-link target should exist and be focusable: 2 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 7 characters: “이음 IEUM”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 32 characters: “함께하는 일상 속 ‘사이의 순간들’을 잇는 반려동물 브랜드”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“{#item}” and “{#item}”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 58 pages on shopieum.com and 4 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.

There is no https://shopieum.com/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.

Your homepage links to https://shopieum.com/%7B, which answers with an error. Visitors hit a dead end and search engines drop it.

/, https://shopieum.com/brand.html, https://shopieum.com/board/index.html, https://shopieum.com/member/agreement.html and https://shopieum.com/member/nonmember.html all use the title “이음 IEUM”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shopieum.com/product/list.html, https://shopieum.com/product/clover-scarf/22/category/1/display/3 and https://shopieum.com/product/frill-scarf/24/category/1/display/3 have no meta description, so Google writes the search snippet from whatever text it finds.

https://shopieum.com/brand.html, https://shopieum.com/board/index.html, https://shopieum.com/member/agreement.html and https://shopieum.com/member/nonmember.html use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://shopieum.com/board/free/list.html, whose canonical is https://shopieum.com/board/%EC%9E%90%EC%9C%A0%EA%B2%8C%EC%8B%9C%ED%8C%902/1002. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shopieum.com/category/shop/24, https://shopieum.com/category/best/25, https://shopieum.com/category/new/26, https://shopieum.com/brand.html, https://shopieum.com/board/index.html and https://shopieum.com/board/free/list.html and 5 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.

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

1 image failed to load on a phone, for example https://shopieum.com/.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration')”.

Large scripts ship without source maps.

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

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

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

Opening the homepage sets 17 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.