bibs.co.kr website review

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

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

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

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

megadata.co.kr costs a phone 1.2 s of main-thread work and 218 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (megadata.co.kr, Google Tag Manager and Facebook and others), adding 2.0 MB and 2.3 s of main-thread time.

12 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

About 219 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.

The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 579 ms of main-thread work and 1.0 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.

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

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

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

36 KiB could be saved by minifying JavaScript.

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

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 78.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

18 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 20.5 MB in 247 requests on a phone: images 17.0 MB (101), scripts 2.3 MB (55) and fonts 729 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

1 dropdown has no label.

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

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 19 characters: “[브랜드관] > 빕스 > 브랜드소개”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 62 characters: “프리미엄 유아용품 전문 종합 쇼핑몰, 기저귀, 물티슈, 장난감, 범보의자, 물놀이용품, 쏘서 ☎1544-3096”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at http://www.mowm.co.kr/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mowm.co.kr/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 65 pages on bibs.co.kr and 11 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://www.mowm.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.

Your homepage links to https://www.mowm.co.kr/shop/page.html, https://www.mowm.co.kr/shop/member.html and https://www.mowm.co.kr/shop/idinfo.html, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.mowm.co.kr/board/board.html has no <title>, so Google invents the link text in results.

https://www.mowm.co.kr/board/board.html has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mowm.co.kr/shop/todaygoods.html, /, https://www.mowm.co.kr/shop/plan_list.html and https://www.mowm.co.kr/shop/faq.html use the same meta description. A description written for each page earns more clicks.

https://www.mowm.co.kr/shop/todaygoods.html, https://www.mowm.co.kr/board/board.html, /, https://www.mowm.co.kr/shop/plan_list.html and https://www.mowm.co.kr/shop/faq.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mowm.co.kr/shop/todaygoods.html, https://www.mowm.co.kr/shop/plan_list.html and https://www.mowm.co.kr/shop/faq.html 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.mowm.co.kr/shop/todaygoods.html and https://www.mowm.co.kr/board/board.html took over 3 s to send their HTML from our server.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 502 (Bad Gateway)”.

1 image is served at too low a resolution for sharp phone screens.

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.

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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 26 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 Criteo and Google Tag Manager (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 6 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.