Website review, no card needed
lunxia.co.kr website review
Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 78 checks
This review found 45 issues worth fixing on lunxia.co.kr, 20 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
57FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
27.6 s · 19.3 MB39 images could be 19.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 27.6 s faster on a phone.
Use efficient cache lifetimes
3.0 s · 2.4 MB60 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Render-blocking requests
2.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Reduce unused JavaScript
1.4 s · 338 KiBAbout 338 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Minify JavaScript
900 ms · 164 KiB164 KiB could be saved by minifying JavaScript.
Document request latency
950 msThe HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Avoid multiple page redirects
751 msThe page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, poxo.com and pstatic.net and others), adding 506 KiB and 156 ms of main-thread time.
Reduce unused CSS
150 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 315 ms of it running JavaScript. That is comfortably low.
Server response: 227 ms
227 msYour server sent the HTML in 227 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 75.5 s
75.5 sYour largest element takes 75.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 79.6 s
79.6 sThe page becomes fully interactive after 79.6 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.613
0.613The layout shifts by 0.613 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
56 images without width and height
56 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: 103 ms
103 msScripts block the page for only 103 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 22.1 MB in 94 requests
22.1 MBYour homepage downloads 22.1 MB in 94 requests on a phone: images 20.8 MB (50), scripts 1.0 MB (14) and fonts 185 KiB (15). Under 2 MB keeps phones on slow connections fast.
26 images over 500 KB
26 images weigh 16.6 MB together. On a phone connection a single image that size takes seconds.
38 images far larger than shown
16.4 MB38 images are downloaded at several times the size a phone draws them, for example main2026m-0904.jpg at 2,000 px wide, shown at 368 px. Resized copies would save about 16.4 MB.
38 images in older formats
38 images (20.7 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.
20 images below the first screen load straight away
20 images further down the page (8.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.3 g of CO₂ per visit
6.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.26 g of CO₂e: 751.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (75 elements)
All page content should be contained by landmarks: 75 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.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (17 characters)
Your title is only 17 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 (66 characters)
Your meta description is only 66 characters: “Emotional Fabric. 맞춤제작, 좌식소파, 대방석, 디자인쿠션, 아기침대범퍼, 침대범퍼, 블랭킷, 아가용이불”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://lunxia.co.kr/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
94 internal links, 2 external
The homepage links to 94 pages on lunxia.co.kr and 2 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://lunxia.co.kr/.
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.
No llms.txt
There is no https://lunxia.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.
1 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.
Other pages
15 pages share 2 titles
/ and https://lunxia.co.kr/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.
14 pages without an H1
https://lunxia.co.kr/category/baby-bumpersthick/57, https://lunxia.co.kr/category/baby-bumpersthin/127, https://lunxia.co.kr/category/baby-sheets/85, https://lunxia.co.kr/category/blanket/122, https://lunxia.co.kr/category/canopy/123 and https://lunxia.co.kr/category/baby-items/7 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://lunxia.co.kr/category/canopy/123 and https://lunxia.co.kr/category/outlet/61 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
36 small tap targets
36 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.instagram.com/lunxia' from origin 'https://m.lunxia.co.kr' has been blocked by…”.
Missing source maps
Large scripts ship without source maps.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 102 words
The homepage has only about 102 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
3 calls to action
The homepage has 3 calls to action, for example “MY SHOP”, “ORDER SEARCH” and “ORDER GUIDE”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
15 other companies contacted
Loading the homepage contacts 15 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 lunxia.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
- Korea Telecom
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on lunxia.co.kr, including 14 speed issues, 6 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.