Website review, no card needed
0105.co.kr website review
Visit site (opens in a new tab)Reviewed 21 November 202642 issues · 74 checks
This review found 42 issues worth fixing on 0105.co.kr, 16 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
4.3 s31 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.
Use efficient cache lifetimes
1.8 s · 457 KiB9 files are served with short cache lifetimes, so returning visitors download them again (457 KiB).
Document request latency
1.8 sThe HTML itself could arrive about 1.8 s sooner: redirects, a slow server response or missing compression delay everything after it.
Avoid multiple page redirects
1.4 sThe page goes through 2 redirects before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
700 ms · 158 KiB5 images could be 158 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Reduce unused JavaScript
600 ms · 104 KiBAbout 104 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
350 ms · 96 KiBPolyfills for old browsers add 96 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
cdn-nhncommerce.com adds 42 ms
42 mscdn-nhncommerce.com costs a phone 42 ms of main-thread work and 438 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 JavaScript
150 ms · 16 KiB16 KiB could be saved by minifying JavaScript.
5 third-party services on the page
5 third-party services load with your homepage (cdn-nhncommerce.com, pstatic.net and naver.net and others), adding 466 KiB and 58 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 99 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NEW 블루베리 즙 [1박스, 21포]”. Most of its time is resource load duration (3.0 s).
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.25
0.25The layout shifts by 0.25 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
5 images without width and height
5 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.
1 checks passed
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
4 KiB1 image is downloaded at several times the size a phone draws it, for example 1706858648525s0.JPG at 561 px wide, shown at 180 px. Resized copies would save about 4 KiB.
4 images in older formats
4 images (195 KiB) 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.
About 0.2 g of CO₂ per visit
0.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.18 g of CO₂e: 21.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 650 KiB in 60 requests
650 KiBYour homepage downloads 650 KiB in 60 requests on a phone: scripts 356 KiB (23), images 235 KiB (12) and stylesheets 42 KiB (16). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (8 characters)
Your title is only 8 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://0105.co.kr/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
38 internal links, 0 external
The homepage links to 38 pages on 0105.co.kr and 0 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
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.
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
1 checks passed
llms.txt published
The site publishes https://0105.co.kr/llms.txt (3 KiB, 2 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://0105.co.kr/goods/goods_main.php, which answers with an error. Visitors hit a dead end and search engines drop it.
8 pages without a title
https://0105.co.kr/mypage/index.php, https://0105.co.kr/mypage/order_list.php, https://0105.co.kr/mypage/wish_list.php, https://0105.co.kr/mypage/mypage_qa.php, https://0105.co.kr/goods/goods_view.php and https://0105.co.kr/goods/goods_list.php and 2 others have no <title>, so Google invents the link text in results.
7 pages share a title
/, https://0105.co.kr/member/join_method.php, https://0105.co.kr/service/index.php, https://0105.co.kr/main/index.php, https://0105.co.kr/service/company.php and https://0105.co.kr/service/agreement.php and 1 other all use the title “밝은세상블루베리”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://0105.co.kr/member/join_method.php, https://0105.co.kr/mypage/index.php, https://0105.co.kr/mypage/order_list.php, https://0105.co.kr/mypage/wish_list.php, https://0105.co.kr/mypage/mypage_qa.php and https://0105.co.kr/service/index.php and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://0105.co.kr/member/join_method.php, https://0105.co.kr/mypage/index.php, https://0105.co.kr/mypage/order_list.php, https://0105.co.kr/mypage/wish_list.php, https://0105.co.kr/mypage/mypage_qa.php and https://0105.co.kr/service/index.php and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://0105.co.kr/service/index.php, https://0105.co.kr/main/index.php, https://0105.co.kr/service/company.php and https://0105.co.kr/service/private.php 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.
1 page slow to respond
https://0105.co.kr/member/join_method.php took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
22 of 23 tappable elements near the top are at least 24 px.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 34 words
The homepage has only about 34 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 call to action
The homepage has 1 call to action, for example “JOIN”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 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.
8 other companies contacted
Loading the homepage contacts 8 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 0105.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
- Framework
- jQuery
- 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 42 issues on 0105.co.kr, including 15 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.