Website review, no card needed

beaumonde.co.kr logo

beaumonde.co.kr website review

Visit site (opens in a new tab)Reviewed 21 November 202653 issues · 86 checks

This review found 53 issues worth fixing on beaumonde.co.kr, 23 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of beaumonde.co.kr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beaumonde.co.kr at 1.6 s1.6 s
  2. beaumonde.co.kr at 3.2 s3.2 s
  3. beaumonde.co.kr at 4.8 s4.8 s
  4. beaumonde.co.kr at 6.4 s6.4 s
  5. beaumonde.co.kr at 8.0 s8.0 s
  6. beaumonde.co.kr at 9.6 s9.6 s
  7. beaumonde.co.kr at 11.2 s11.2 s
  8. beaumonde.co.kr at 12.8 s12.8 s

Speed

13 to fix57
  • Use efficient cache lifetimes

    3.1 s · 12.9 MB

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

  • Improve image delivery

    1.1 s · 10.8 MB

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

  • Render-blocking requests

    4.3 s

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

  • Document request latency

    2.5 s

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

  • Avoid multiple page redirects

    1.4 s

    The page goes through 2 redirects before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.

  • 8,411 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and cdn-nhncommerce.com and others), adding 9.3 MB and 334 ms of main-thread time.

  • Reduce unused JavaScript

    760 ms · 258 KiB

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

  • Mobile performance score: 57

    57/100

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

  • cdn-nhncommerce.com adds 36 ms

    36 ms

    cdn-nhncommerce.com costs a phone 36 ms of main-thread work and 8.8 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.

  • Legacy JavaScript

    450 ms · 107 KiB

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

  • Reduce unused CSS

    380 ms · 35 KiB

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

  • Main-thread work: 2.5 s

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

  • Minify JavaScript

    190 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Minify CSS

    190 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 7 long tasks on the main thread

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 186 ms

    186 ms

    Your server sent the HTML in 186 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix68
  • Speed Index: 15.2 s

    15.2 s

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LOUISE MISHA”. Most of its time is resource load delay (5.1 s).

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • 111 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

  • Total Blocking Time: 56 ms

    56 ms

    Scripts block the page for only 56 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix33
  • Page weight: 23.8 MB in 330 requests

    23.8 MB

    Your homepage downloads 23.8 MB in 330 requests on a phone: images 22.9 MB (274), scripts 754 KiB (29) and stylesheets 64 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 6.7 g of CO₂ per visit

    6.74 g

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

Accessibility

15 to fixGoogle 4947
  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (25 elements).

  • 18 images without alt text

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

  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (3 elements).

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 291 text elements with low contrast

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

  • No main landmark

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

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

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

  • Hidden but focusable

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

  • 15 tap targets too small

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

  • Malformed lists

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

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (3 elements).

  • Orphan list items

    Some list items are not inside a list.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (3 elements).

1 checks passed
  • 4 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 8560
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “보몽드 | 수입 키즈 브랜드 편집샵”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (68 characters)

    Your meta description is only 68 characters: “보보쇼즈, 타오, 루이스미샤, 미샤앤퍼프, 페페슈즈 등 유럽 프리미엄 브랜드를 만나볼 수 있는 수입 아동복 셀렉트샵 보몽드”. 70 to 160 characters is enough to sell the click.

  • No XML sitemap

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

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 596 internal links, 5 external

    The homepage links to 596 pages on beaumonde.co.kr and 5 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.beaumonde.co.kr/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    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.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

6 to fix57
  • 6 pages without a title

    https://beaumonde.co.kr/mypage/order_list.php, https://beaumonde.co.kr/mypage/index.php, https://beaumonde.co.kr/goods/goods_list.php, https://beaumonde.co.kr/board/list.php, https://beaumonde.co.kr/board/view.php and https://beaumonde.co.kr/goods/goods_view.php have no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://beaumonde.co.kr/main/index.php declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 5 pages share a title

    /, https://beaumonde.co.kr/main/index.php, https://beaumonde.co.kr/member/join_method.php, https://beaumonde.co.kr/goods/brand.php and https://beaumonde.co.kr/event/couponzone.php all use the title “보몽드 | 수입 키즈 브랜드 편집샵”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://beaumonde.co.kr/mypage/order_list.php, https://beaumonde.co.kr/mypage/index.php, https://beaumonde.co.kr/goods/goods_list.php, https://beaumonde.co.kr/board/list.php, https://beaumonde.co.kr/board/view.php and https://beaumonde.co.kr/goods/goods_view.php have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://beaumonde.co.kr/main/index.php, https://beaumonde.co.kr/member/join_method.php, https://beaumonde.co.kr/goods/brand.php and https://beaumonde.co.kr/event/couponzone.php use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://beaumonde.co.kr/main/index.php, https://beaumonde.co.kr/member/join_method.php, https://beaumonde.co.kr/mypage/order_list.php, https://beaumonde.co.kr/mypage/index.php, https://beaumonde.co.kr/goods/goods_list.php and https://beaumonde.co.kr/goods/brand.php and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://beaumonde.co.kr/main/index.php took over 3 s to send its HTML from our server.

  • 10 internal pages checked

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

2 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 7370
  • No mobile viewport

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

  • 4 low-resolution images

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

1 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

Content and conversion

2 to fix70
  • No call to action on the first screen

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

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 3,638 words of copy

    The homepage carries about 3,638 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “JOIN +2,000P”, “ORDER” and “NEW MEMBER JOIN (+ 3000won)”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at beaumonde.co.kr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Nhn As Kr Kr Nhncloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on beaumonde.co.kr, including 18 speed issues, 8 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25