Website Designing
Layouts built to convert.
Read moreWebsite Design · Delhi NCR & remote
Most “mobile friendly” sites are a desktop design that survived being squeezed. Genuinely responsive design asks a different question on a phone: with one thumb and a fifth of the space, what still matters?
Short answer
Responsive website design means the layout adapts to the device rather than being scaled down. In practice, for Indian traffic, it means designing the 360px phone layout first — deciding what appears, what collapses and what is dropped — then expanding to desktop. A shrunk desktop design passes automated mobile tests and still loses visitors.
Four details. A real reply the same day, from me.
01 The premise
Google’s mobile-friendly check asks a narrow question: does the content fit the viewport and is the text legible. A site can pass it comfortably and still be unpleasant to use — a phone number that is an image, a form with six fields above a keyboard, a menu that needs two taps and a pinch, a table that scrolls the entire page sideways.
Designing mobile first is a genuinely different exercise from designing desktop first. It forces the ranking of content early, because there is only one column and everything is a decision about what comes next. That constraint is why mobile-first designs usually turn out better on desktop too: the priorities were settled when they could not be avoided.
And there is a specifically Indian dimension. A meaningful share of traffic arrives on mid-range Android handsets over a congested mobile network, not on a recent iPhone over office wi-fi. A design that assumes the second one is a design that quietly fails a large part of your audience.
02 The checklist
These are design decisions, not development details — they belong in the drawing, not in a later fix.
03 Breakpoints
Breakpoints chosen from where the content breaks, not from device model names.
| Width | What the design does |
|---|---|
| 320–419px | Small and older Android handsets. Single column, largest tap targets, most aggressive trimming. If it works here it works everywhere. |
| 420–719px | Mainstream phones. Still one column, but headings, images and spacing can breathe. |
| 720–979px | Tablets and small laptops. Two columns appear where content genuinely pairs — not everywhere at once. |
| 980–1279px | Laptops. Full navigation replaces the drawer, sidebars and multi-column grids become useful. |
| 1280px and above | Large screens. Line length is capped so text stays readable — letting paragraphs stretch to 1900px is a real, common flaw. |
Free mobile review
Send me the URL. I will open it on a mid-range Android on mobile data and tell you what breaks, what is unreachable by thumb and what is quietly costing you enquiries.
Four details, and a real reply today.
04 Testing
Emulators are a starting point, not a verdict.
— Website Design
These sit next to responsive design and are usually bought with it. Same person doing the work in each case.
Layouts built to convert.
Read moreFor companies that sell offline.
Read moreScale, governance, many stakeholders.
Read moreOne page, one action.
Read moreNo themes, no templates.
Read moreFix what is losing you enquiries.
Read more— Questions
Straight answers, including the ones that cost me work. If yours is not here, ask it — I reply the same day.
That test checks whether content fits and text is legible. It does not check whether your form is completable one-handed, whether your buttons are reachable by thumb, or whether the page loads on mobile data. Plenty of sites pass and still lose most of their mobile visitors.
No. Separate m-dot sites were a workaround from a decade ago and they bring duplicate content, split rankings and double maintenance. One responsive site serving every screen is the current standard and the simpler thing to own.
Designing the smallest screen before the largest, rather than adapting downwards. It forces content priorities to be decided when there is no room to avoid them, which is why mobile-first designs usually end up cleaner on desktop as well.
If it is built with fluid layouts rather than fixed device breakpoints, yes — those sizes are just more widths. Sites built around specific device dimensions are the ones that break when a new form factor appears.
Nothing, because it is not an extra. Any site I build is responsive by definition. Retrofitting responsiveness onto an old fixed-width site does cost money, and in most cases rebuilding is cheaper than patching.
Indirectly and significantly. Google indexes the mobile version of your site and measures Core Web Vitals on mobile. A site that is slow or awkward on a phone is being judged on exactly that experience, whatever the desktop version looks like.
Free consultation · No obligation
Send me the URL. I will open it on a mid-range Android over mobile data and tell you exactly what a phone visitor runs into — before you spend anything.
Name, number, email, what you need.