Responsive Design
Responsive design means one site that works at every screen size, rather than a desktop site with a degraded phone version. For B2B the hard part is not the layout, it is the tables.
Do B2B buyers actually use phones?
Yes, and more than the desktop-heavy analytics of a typical B2B site suggests. Research happens on a phone in the evening or on a plant floor; the formal enquiry gets submitted from a desk later.
That pattern makes mobile look less important than it is. The phone session was where the shortlist got made. The desktop session was where a decision already taken got executed.
What actually breaks on a phone
Specification tables, almost always. A table with eight columns of technical data is the most valuable content on a product page and the hardest thing to render at 390 pixels wide.
The wrong answers are common: shrinking the text until it is unreadable, letting the table push the whole page sideways, or hiding columns and quietly removing the information the buyer came for.
The workable answers depend on the table. A comparison of a few items can restack as cards, one per item. A dense specification table is better scrolling horizontally inside its own container, so the page body stays still while the table moves. What matters is that no information is removed and the page itself never scrolls sideways.
What else needs attention
- Forms. Correct input types so the right keyboard appears, fields wide enough to see what was typed, and errors that say what to fix.
- Tap targets. Sized for a thumb, with enough space that the adjacent link is not a coin flip.
- Navigation. A menu that opens, closes, and does not trap keyboard focus inside itself.
- Images. Appropriately sized files per screen, not a desktop photograph downloaded over a phone connection.
- PDFs. Frequently where technical detail hides, and frequently unreadable on a phone. If it is important, it belongs on a page.
What mobile-first means in practice
Designing the narrow layout first and letting it expand, rather than designing wide and cutting things away.
The benefit is not really technical. Starting narrow forces a decision about what genuinely matters, because there is no room for anything else. Starting wide lets everything be included and then quietly deleted at small sizes, which is how the specification a buyer needed ends up hidden below 768 pixels.
How it is tested
| Check | What it catches |
|---|---|
| Real devices, not just a browser resize | Touch behaviour, actual performance, how fonts really render |
| Horizontal overflow on every template | A single wide element pushing the whole page sideways |
| Forms completed end to end on a phone | Keyboard problems and validation that cannot be dismissed |
| Text at increased browser font size | Layouts that break when someone enlarges type, which many people do |
| Landscape orientation | Fixed headers that consume most of a short viewport |
Does it affect search?
Yes, and indirectly more than directly. Indexing is based on the mobile version of a page, so content that only exists on the desktop layout effectively does not exist. Beyond that, page weight and layout stability are performance signals, and both are set by design decisions.
Where this fits
Inside web development, and inseparable from custom design: responsive behaviour is designed, not added afterwards. Usability problems that show up in real sessions are UX optimization.
Frequently asked questions
Our analytics say 80% desktop. Does mobile matter?
Probably more than that number implies. A site that is unpleasant on a phone suppresses its own mobile traffic, so the figure partly measures the problem. It also misses the research sessions that shaped a decision before anyone reached a desk.
Should we build a separate mobile site or an app?
Almost never. A separate mobile site doubles the maintenance and splits your content. An app is worth considering when there is a repeated task for existing customers, not for a site people visit while evaluating you.
Can our existing site be made responsive?
Usually, and it is worth assessing before assuming a rebuild. A site with sound structure can often be fixed at the stylesheet level. A fixed-width layout with content positioned absolutely is a different matter, and there the rebuild is the cheaper path.
See where you stand
We will review your current search visibility and show you what buyers find when they look for what you do.
Contact Us