Open your analytics and look at the device split. In most Greek e-shops we work with, mobile is the clear majority of traffic. Yet mobile conversion rate is often noticeably lower than desktop. Part of that gap is natural (people browse on the phone and buy on the laptop), but part of it is simply a poor mobile checkout.
The catch is that most shop owners review their site on a computer. Let us fix that.
The five-minute test
Before anything else: take your phone, switch off Wi-Fi and place a real order in your shop, one-handed. Then ask someone who has never seen the site to do the same on a different phone (if you have an iPhone, try Android too).
Note every point where, honestly and without making excuses for your own site:
- You had to zoom.
- You tapped the wrong thing.
- The wrong keyboard appeared.
- You waited without knowing whether anything was happening.
- Details you had already typed disappeared.
That list is your plan.
Form fields that help instead of hinder
The right keyboard for every field
A small detail that makes a big difference:
- Phone:
type="tel", so a numeric keypad opens. - Email:
type="email", with @ immediately available. - Postcode:
inputmode="numeric", since Greek postcodes are five digits. - Card number (if the form is yours): numeric keypad.
Autofill that works
Browsers can fill name, address, phone and email in one tap, as long as fields carry the right autocomplete attributes (name, email, tel, street-address, postal-code, address-level2 for the city). Many themes strip them or get them wrong. Check yours.
Font size
If input text is smaller than 16px, Safari on iPhone zooms in automatically when the customer taps the field, and the page drifts sideways. The fix: 16px or larger on inputs.
Labels that do not vanish
A placeholder in place of a label looks neat, but once the customer starts typing they forget what the field was for. Use real labels above the fields.
Less typing
- The postcode can auto-fill city and region.
- Default the country to Greece.
- Show invoice fields only when the customer asks for an invoice.
- Address autocomplete can help, but test it with Greek addresses before rolling it out.
Wallets: the biggest win
Apple Pay and Google Pay remove almost the whole form: name, address and card come from the wallet, and approval happens with Face ID or a fingerprint. On mobile, this is the fastest checkout you can offer.
- Place them as express buttons at the top of checkout, or even in the cart.
- Make sure shipping is calculated correctly when the address comes from the wallet.
- Test on real devices, not just emulators.
For the other payment methods Greek shoppers expect, see our guide to payment methods in Greece.
Design for the thumb
- Buttons large enough: at least roughly 44–48px tall, with space between them.
- Main button always reachable: a sticky "Place order" or "Continue" at the bottom helps on long pages.
- A single column. Two fields side by side on a phone almost always hurt.
- A collapsible order summary at the top, with the total always visible.
- Options as large radio buttons, not dropdowns, for shipping and payment.
Speed on a real network
Checkout is often the slowest page on the site, because that is where every script loads: payment providers, tracking, chat, reviews, plugins that have no business being there. On average 4G, it shows.
- Strip out of checkout whatever is not needed (chat widgets, sliders, pop-ups).
- Watch INP: every tap should respond quickly. Google's "good" threshold is under 200ms.
- Show a loading state while shipping is calculated or when the pay button is pressed, and disable the button to prevent duplicate orders.
The return trip from the bank
On mobile, 3D Secure or IRIS approval often opens the banking app. The customer approves and must get back to the browser and the confirmation page. This is where orders get "lost":
- Test the flow with the major Greek banks on both iPhone and Android.
- Make sure the order is updated via the provider's callback, even if the customer never returns to the page.
- Send the confirmation email immediately so the customer can relax.
Mobile-friendly error messages
On desktop, an error at the top of the page gets seen. On mobile, the customer is three screens further down and never notices it. Put the message next to the field, scroll the screen to it, and say what to do: "Postcode must be 5 digits".
Checklist
- One-handed test order on 4G, on both iPhone and Android
- Correct keyboards and autocomplete on every field
- Inputs at 16px or larger
- Labels above fields
- Apple Pay and Google Pay as express options
- Single column, large buttons, sticky main button
- A lean checkout without unnecessary scripts
- A clean return from the banking app
- Error messages next to the field
The bottom line
Mobile checkout is not a smaller version of your desktop checkout. It is your main checkout. Every second and every field you save there shows up in sales. If you would like a speed and usability review of your shop, see our speed and Core Web Vitals service or get in touch.