Website review, no card needed

myhouse.co.kr logo

myhouse.co.kr website review

Visit site (opens in a new tab)Reviewed 28 October 202649 issues · 84 checks

This review found 49 issues worth fixing on myhouse.co.kr, 21 of them high impact, across 84 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 myhouse.co.kr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. myhouse.co.kr at 0.9 s0.9 s
  2. myhouse.co.kr at 1.9 s1.9 s
  3. myhouse.co.kr at 2.8 s2.8 s
  4. myhouse.co.kr at 3.8 s3.8 s
  5. myhouse.co.kr at 4.7 s4.7 s
  6. myhouse.co.kr at 5.7 s5.7 s
  7. myhouse.co.kr at 6.6 s6.6 s
  8. myhouse.co.kr at 7.6 s7.6 s

Speed

13 to fix9
  • Use efficient cache lifetimes

    20.2 s · 5.6 MB

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

  • Improve image delivery

    5.5 s · 13.1 MB

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

  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    2.9 s · 945 KiB

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

  • Reduce unused CSS

    1.1 s · 247 KiB

    About 247 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Main-thread work: 12.7 s

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

  • Mobile performance score: 9

    9/100

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

  • 6,748 HTML elements

    The page has 6,748 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 (Google Tag Manager, Facebook and happytalkio.com and others), adding 1.5 MB and 1.0 s of main-thread time.

  • Minify JavaScript

    900 ms · 191 KiB

    191 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    350 ms · 59 KiB

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

  • 20 long tasks on the main thread

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

  • happytalkio.com adds 164 ms

    164 ms

    happytalkio.com costs a phone 164 ms of main-thread work and 350 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.

  • Minify CSS

    150 ms · 19 KiB

    19 KiB could be saved by minifying CSS.

  • 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: 375 ms

    375 ms

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

Core Web Vitals

7 to fix9
  • Largest Contentful Paint: 229.0 s

    229.0 s

    Your largest element takes 229.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 232.1 s

    232.1 s

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

  • Speed Index: 14.3 s

    14.3 s

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

  • Cumulative Layout Shift: 0.688

    0.688

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • 15 images without width and height

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

Images and page weight

6 to fix19
  • Page weight: 53.0 MB in 340 requests

    53.0 MB

    Your homepage downloads 53.0 MB in 340 requests on a phone: media 31.4 MB (8), images 17.3 MB (119) and scripts 2.6 MB (96). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    5117d401071d34b6a024bc3e7c70b515.png weighs 492 KiB. On a phone connection a single image that size takes seconds.

  • 17 images far larger than shown

    954 KiB

    17 images are downloaded at several times the size a phone draws them, for example 8f688524cbe4a4667855982e9333a464.jpg at 1,279 px wide, shown at 296 px. Resized copies would save about 954 KiB.

  • 25 images in older formats

    25 images (5.0 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.

  • An image on the first screen is lazy-loaded

    2a45a1c15ce09c084270e326e0028982.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images below the first screen load straight away

    3 images further down the page (325 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 15.0 g of CO₂ per visit

    15.02 g

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

Accessibility

6 to fix75
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 35 text elements with low contrast

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

  • 11 form fields without a label

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

  • 10 links without text

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

  • Malformed lists

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

  • Frames without titles

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

  • Skip links are not focusable.

    Skip links are not focusable. (2 elements).

  • Headings skip levels

    Headings skip levels (h1 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 8586
  • Title is short (13 characters)

    Your title is only 13 characters: “myhouse 마이하우스”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (27 characters)

    Your meta description is only 27 characters: “피부에 닿는 소재부터 디자인하는 침구 리빙 브랜드”. 70 to 160 characters is enough to sell the click.

  • 2 links crawlers can't follow

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

  • 129 internal links, 8 external

    The homepage links to 129 pages on myhouse.co.kr and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “마이하우스”.

  • Canonical URL set

    The canonical URL is https://myhouse.co.kr/.

  • Structured data in place

    Structured data found: OnlineStore.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://myhouse.co.kr/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,011 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://myhouse.co.kr/llms.txt (1 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

5 to fix57
  • 2 linked pages are broken

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

  • 10 pages share a title

    /, https://myhouse.co.kr/lightbox/0930_autum_festa.html, https://myhouse.co.kr/product/list_best.html, https://myhouse.co.kr/page/list_matter.html, https://myhouse.co.kr/blog and https://myhouse.co.kr/page/event.html and 4 others all use the title “myhouse 마이하우스”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://myhouse.co.kr/product/list.html has no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://myhouse.co.kr/lightbox/0930_autum_festa.html, https://myhouse.co.kr/product/list_best.html, https://myhouse.co.kr/page/list_matter.html, https://myhouse.co.kr/blog, https://myhouse.co.kr/page/event.html and https://myhouse.co.kr/page/faq.html and 3 others use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://myhouse.co.kr/board/free/list.html, whose canonical is https://myhouse.co.kr/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.

  • 1 page with very little text

    https://myhouse.co.kr/member/agreement.html has 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.

  • 4 pages slow to respond

    https://myhouse.co.kr/page/list_matter.html, https://myhouse.co.kr/blog, https://myhouse.co.kr/member/privacy.html and https://myhouse.co.kr/shopinfo/guide.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 31 small tap targets

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

  • 2 third-party cookies

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

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • No calls to action

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

  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 163 words

    The homepage has only about 163 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 4 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (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.

  • 35 other companies contacted

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

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

Analytics
Google Analytics
Hosting
Korea Telecom

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on myhouse.co.kr, including 20 speed issues, 3 SEO issues and 4 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