Responsive design: why the mobile version is the main one
Most website visits in Uzbekistan come from phones. The mobile version is not the second version — it is the site.
Mobile first as a working order
Drawing for a monitor and then squeezing it onto a phone produces a set of compromises: long blocks, tiny text, important elements hidden away.
The reverse order imposes discipline. At 360 pixels wide you fit one heading, one sentence and one button — which is exactly what the visitor needs.
Google also indexes the mobile version, so content hidden on phones effectively does not exist for search.
What breaks most often
Tables, which force horizontal scrolling of the whole page. Scroll inside the table or rebuild it as cards.
Images with text baked in: unreadable at small sizes and invisible to search. Text should be text.
Fixed headers eating a third of a short screen, and two-column forms with tiny labels. On a phone, fields stack and must open the right keyboard — numeric for phone, email layout for email.
Breakpoints and speed
Do not tie breakpoints to device models; place them where the layout stops looking right, typically around 480, 768 and 1200 pixels, and make it flex smoothly in between.
Responsiveness is worthless if the page takes ten seconds. Serve images sized for the screen and defer everything below the fold.
How to test
On real devices including an inexpensive Android, since that is what a large share of the audience carries and where performance problems surface.
Walk the key journey one-handed: find the service, see the price, submit a request. Anything requiring zoom or precise tapping is a defect.