Responsive redesign: making an old site work on the phone
A technically fluid layout and a genuinely usable mobile site are different things. Most old sites pass the 'does the layout break' test but fail the test of real one-handed use on the go.
Why 'responsive' does not mean 'usable'
Sites from 2016–2019 are often technically responsive — blocks rearrange to fit screen width — but designed with desktop logic: small type, buttons sized for a mouse cursor rather than a thumb, a menu that takes three taps to reach the section you need.
A simple test: open the site on a phone with one hand, no zooming, and try reaching the lead form in three taps. If you cannot, what you have is not a mobile version but a desktop layout squeezed into a narrow column.
Speed matters more than the visuals
A significant share of mobile traffic in Uzbekistan runs on 3G/4G outside areas of solid coverage. Test the page in PageSpeed Insights on Mobile and watch LCP — if the hero takes longer than three to four seconds to render, part of the audience leaves before ever seeing the design.
The main causes of slow loading on local sites: uncompressed gallery photos, whole libraries loaded for a single animation, and fonts pulled from external CDNs. Redesigning for mobile without fixing these gets you nowhere — a beautiful but slow site still loses people.
Element size and spacing
The minimum tappable area on mobile is 44 by 44 pixels with margin around it. Buttons and links packed tightly together cause accidental mis-taps, and people leave the site irritated without even understanding what went wrong.
The menu should open and close in one tap, without losing scroll position. Hover-triggered dropdown submenus inherited from the desktop version simply do not work on a touchscreen — there is no hover state to trigger.
The form and contact channel on mobile
The mobile lead form should ask for the bare minimum — name and phone; everything else is established in conversation. Every extra field feels heavier on a small screen because it means switching keyboards and scrolling.
The phone number and Telegram button belong in a fixed bottom bar visible on any screen without scrolling. This is not an aesthetic choice — it directly affects conversion: someone ready to call should not have to hunt across the page for the number.
Timeline and scope
Adapting an existing design for mobile without changing the page structure takes one and a half to two weeks and costs 4,000,000 to 6,000,000 UZS — covering layout rework, image optimisation, and the sticky contact bar.
If the problem runs deeper — the old menu structure simply does not translate to mobile — a fuller redesign with reworked navigation is needed, and budget and timeline shift closer to the mid-tier: 6,000,000 to 9,000,000 UZS over two to three weeks.