Who this decision is for
- An overseas e-commerce or subscription brand whose Korean traffic is mostly phone-based but whose checkout was designed on desktop.
- A B2B company seeing Korean visitors open emails and links on mobile, then abandon a long inquiry form.
- A tourism marketer whose Korean campaign ads run on social feeds and lead to a page that was never tested on a phone.
- A product manager deciding whether to invest in a mobile redesign or in a Korean app.
The decision to make
The decision is where to spend limited effort: layout, speed, forms, payment or messaging. Most Korean users reach websites on phones, so mobile is the primary experience rather than a variant. Yet fixing everything at once is rarely realistic, so the useful question is which step loses the most visitors.
The trade-off is between a broad redesign and targeted fixes. A redesign can solve structural problems but takes time and risks new errors. Targeted changes to a slow hero image, a crowded form or an unreachable button are quicker to test. Measure the current funnel first, then decide.
Options compared
| Option | Best when | Watch out for |
|---|---|---|
| Targeted fixes to the existing mobile site | Analytics show drop-off at specific steps and the overall layout is sound. | Leaves deeper structural problems in place if the layout itself was designed for desktop. |
| Mobile-first redesign of key pages | Traffic is mostly phones and templates were built for large screens with mobile squeezed in. | Higher cost and longer approval; needs testing on real devices, not only browser emulation. |
| Separate Korean mobile landing flow for campaigns | Campaign traffic behaves differently from organic visitors and needs a shorter path. | Adds another flow to maintain and can disagree with the main site. |
Risks to manage
- Testing only on desktop emulation. Emulators miss real touch, network and browser behavior. Test on several actual phones and connection conditions before launch.
- Heavy pages. Large images, fonts and scripts slow first view. Measure real loading, remove what is not needed and re-test after each change.
- Forms that ask too much. Long fields on a small screen cause abandonment. Keep required fields to what you will act on and check input types on phones.
- Payment or contact dead ends. A route that needs a desktop or unfamiliar login stops mobile visitors. Walk the whole path on a phone, including confirmation screens.
Evidence to gather first
- Analytics showing the share of Korean traffic by device and where mobile visitors leave the funnel, checked with consent rules in mind.
- Screen recordings or session tests on real phones, if your privacy setup permits, to see where taps fail or text is unreadable.
- Page speed measurements from real devices and networks, rather than a single lab score run on a fast office connection.
- A list of conversion actions and how each is currently completed on mobile, including forms, calls and messaging.
Recommended process
- Baseline the mobile funnel. SWIN reviews your analytics and pages to identify where Korean mobile visitors drop off and which steps carry the most value.
- Test on real devices. We run key journeys on several phones and browsers, recording issues with layout, tapping, loading and input fields.
- Rank the fixes. Findings are grouped into quick fixes, structural changes and items that need your approval, with expected effort noted qualitatively.
- Implement and re-test. Agreed changes are built and tested again on the same devices, so improvements are checked instead of assumed.
- Monitor and adjust. We compare the funnel after release, and recommend further changes only where the data supports them.
What SWIN can deliver
- Mobile funnel review listing where Korean visitors leave and why we think so.
- Device test log covering key journeys on real phones.
- Prioritized fix list separating quick wins from redesign work.
- Updated mobile templates or page changes, tested after implementation.
- Follow-up review comparing the funnel before and after changes.