nanda-bebe.com website review

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

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

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

megadata.co.kr costs a phone 1.9 s of main-thread work and 231 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.

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

187 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

YouTube costs a phone 358 ms of main-thread work and 985 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.

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

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

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

Facebook costs a phone 200 ms of main-thread work and 297 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.

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.

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

Your largest element takes 66.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 21.5 s (Speed Index). Good is under 3.4 s.

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

Scripts block taps and scrolling for 2.9 s 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.

139 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 17.7 MB in 361 requests on a phone: images 13.3 MB (195), scripts 3.3 MB (65) and other files 706 KiB (77). Under 2 MB keeps phones on slow connections fast.

20 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

18 images (1.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.

1 image is downloaded at several times the size a phone draws it, for example 314dcd5e991def928c791dd0db846536.png at 956 px wide, shown at 143 px. Resized copies would save about 58 KiB.

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

1 form field has 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.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 25 characters: “난다베베 , 스타일나는 내아이를 위한 비밀공간”. 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.

No Open Graph image (also missing: og:title, og:description), 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 366 pages on nanda-bebe.com and 8 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://nanda-bebe.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.

/ and https://nanda-bebe.com/myshop/index.html all use the title “난다베베 , 스타일나는 내아이를 위한 비밀공간”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://nanda-bebe.com/myshop/index.html and https://nanda-bebe.com/product/list2.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://nanda-bebe.com/myshop/index.html, https://nanda-bebe.com/category/new5/155, https://nanda-bebe.com/product/list2.html, https://nanda-bebe.com/category/%F0%9F%91%95-%EB%93%B1%EC%9B%90%EB%A3%A9-%EB%AA%A8%EC%9D%8C/2093, https://nanda-bebe.com/category/%F0%9F%8D%AD%ED%82%A8%EB%8D%94%ED%94%8C%EB%A6%AC%EC%8A%A4/508 and https://nanda-bebe.com/category/%EC%95%84%EC%9A%B0%ED%84%B0/24 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://nanda-bebe.com/myshop/index.html and https://nanda-bebe.com/product/list2.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://nanda-bebe.com/category/%F0%9F%91%95-%EB%93%B1%EC%9B%90%EB%A3%A9-%EB%AA%A8%EC%9D%8C/2093, https://nanda-bebe.com/category/%F0%9F%8D%AD%ED%82%A8%EB%8D%94%ED%94%8C%EB%A6%AC%EC%8A%A4/508 and https://nanda-bebe.com/category/%EC%95%84%EC%9A%B0%ED%84%B0/24 took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

2 images failed to load on a phone, for example about:blank.

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

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…”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_UNKNOWN_URL_SCHEME”.

2 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Mixed content”).

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

The homepage carries about 552 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager and TikTok 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 5 cookies, 1 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.