geniethebottle.com website review

11 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.7 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 3.9 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, channel.io and Facebook and others), adding 1.8 MB and 999 ms of main-thread time.

189 KiB could be saved by minifying JavaScript.

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

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

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

Google Tag Manager costs a phone 332 ms of main-thread work and 626 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 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

channel.io costs a phone 289 ms of main-thread work and 346 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.

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

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

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 9.2 MB in 151 requests on a phone: images 5.9 MB (31), scripts 2.6 MB (43) and fonts 395 KiB (11). Under 2 MB keeps phones on slow connections fast.

771f1410d61ced5d6ac6add3edd59a94.png weighs 1.4 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 771f1410d61ced5d6ac6add3edd59a94.png at 1,080 px wide, shown at 188 px. Resized copies would save about 1.0 MB.

3 images (1.6 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.

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

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

2 elements hidden from screen readers can still receive keyboard focus.

1 link inside paragraphs relies on colour alone to stand out.

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

All page content should be contained by landmarks: 3 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 7 characters: “아임낫어베이비”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to gtbcos.com, not geniethebottle.com, so Google may credit that host instead.

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

Your meta description is only 24 characters: “내 아이를 위해 엄마가 만든, 아임낫어베이비”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 133 pages on geniethebottle.com 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.

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

https://geniethebottle.com/myshop/board_list.html and https://geniethebottle.com/board/consult/list.html have no <title>, so Google invents the link text in results.

/, https://geniethebottle.com/myshop/wish_list.html, https://geniethebottle.com/myshop/mileage/historyList.html, https://geniethebottle.com/myshop/deposits/historyList.html, https://geniethebottle.com/myshop/likeit/product.html and https://geniethebottle.com/myshop/coupon/coupon.html and 5 others all use the title “아임낫어베이비”. Search engines can't tell which page to show for a search, so each competes with the others.

https://geniethebottle.com/myshop/board_list.html, https://geniethebottle.com/board/free/list.html, https://geniethebottle.com/board/gallery/list.html, https://geniethebottle.com/board/product/list.html, https://geniethebottle.com/board/review/list.html and https://geniethebottle.com/board/consult/list.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://geniethebottle.com/myshop/wish_list.html, https://geniethebottle.com/myshop/mileage/historyList.html, https://geniethebottle.com/myshop/deposits/historyList.html, https://geniethebottle.com/myshop/likeit/product.html, https://geniethebottle.com/myshop/coupon/coupon.html and https://geniethebottle.com/product/recent_view_product.html use the same meta description. A description written for each page earns more clicks.

https://geniethebottle.com/myshop/board_list.html and https://geniethebottle.com/board/consult/list.html have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 404 ()”.

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

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.

The homepage has only about 73 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, Meta Pixel 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 24 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.