The component bitrix:catalog.section on mobile extends beyond the right edge of the screen, the filter bitrix:catalog.smart.filter takes three screens before products, and the popup window BX.PopupWindow on a tablet positions outside the viewport. We encounter this daily in client projects and know how to fix each problem. In 60% of requests for Bitrix site adaptation, the issue lies precisely in component templates that do not account for mobile resolutions. After our improvements, mobile conversion increases on average by 15–20%, and the bounce rate drops by 25%.
Responsive testing is not "opened on a phone and looked at." It is a systematic check of all critical pages on real resolutions with defect detection and elimination. We have been working with Bitrix for over 5 years and have completed more than 100 projects. Below is exactly how we do it.
How We Test Responsiveness
We use a combination of emulators and real devices. First pass — Chrome DevTools Device Mode: check all breakpoints, detect horizontal scroll via document.documentElement.scrollWidth > window.innerWidth. Second pass — BrowserStack (real iPhones, iPads, Androids). DevTools does not show touch event bugs on iOS, for example, position: fixed with an open keyboard or 100vh accounting for the address bar. According to Google's Web Vitals documentation, such errors reduce user experience by 30%.
| Tool | Purpose | Limitations |
|---|---|---|
| Chrome DevTools | Quick check of all breakpoints | Does not emulate touch events and Safari |
| BrowserStack | Real devices (iOS, Android) | Paid subscription |
| Lighthouse Mobile Audit | Tap targets, font size, CLS | Desktop emulation only |
| Resolution | Typical Issue | Frequency |
|---|---|---|
| 320px (iPhone SE) | Table overflow, small tap targets | 70% |
| 768px (iPad) | Popup outside viewport | 40% |
| 1024px (desktop) | Horizontal scroll from fixed width | 30% |
Why Standard Bitrix Templates Are Poorly Adapted
Most ready-made solutions were designed for desktop, and mobile responsiveness was added on top — often breaking the grid. Components like bitrix:sale.basket.basket and bitrix:catalog.smart.filter generate too much data for mobile. Our task is to rework these templates mobile-first. For example, we replace the cart table with cards using media queries and hide the filter in an off-canvas.
In one e-commerce project with a catalog of 50,000 products, the mobile version lost 30% of traffic because the bitrix:catalog.smart.filter did not fit on screen. We reworked the filter template into an off-canvas panel with asynchronous result loading. After the update, page load time on mobile decreased by 40%, and conversion increased by 18%. This case clearly shows why standard templates need responsive design rework. We guarantee no horizontal scroll after our fixes.
Work Process
- Audit: go through all pages, record defects, create a breakpoint matrix. Measure CLS and tap targets via Lighthouse.
- Fixing: correct CSS, rework component templates (add media queries, change tables to cards).
- Re-testing: verify on real devices, ensure CLS < 0.1 and tap target ≥ 48px.
- Delivery: provide a testing report and final check according to checklist.
Common mistakes we find
- Missing viewport meta or incorrect
user-scalable=no(violates accessibility). - Images without
max-width: 100%— overflow their container. - Tables with fixed column widths — horizontal scroll at 320px.
- Hamburger menu without touchstart handling on iOS.
What Is Included in Our Work
- Documentation: detailed report with screenshots, explanations, and a breakpoint matrix.
- Access: we provide access to our testing environment (BrowserStack sessions) for verification.
- Training: optional 1-hour session for your team on maintaining responsiveness.
- Support: 30 days post-delivery support for any questions.
- Image optimization for mobile: implementing
srcsetor webp. - Consultation on further responsiveness maintenance.
How to Check If Your Bitrix Site Is Ready for Mobile Traffic
The main indicators are absence of horizontal scroll on all breakpoints and CLS < 0.1. Additionally, check tap targets: they must be at least 48×48 pixels. Also ensure forms work correctly with mobile keyboards: the input field should not be covered by the iOS toolbar. If at least one condition is not met, a responsive audit is needed.
Timeline and Cost
Estimated timeline — from 2 to 5 days, depending on template complexity. Our responsive audit starts at $500 for small sites; for complex projects the cost ranges from $1,000 to $3,000. We perform the work turnkey — from testing to fixing all bugs. Get your project evaluated for free — just contact us. Get a consultation on responsiveness — easily: contact us.
Acceptance Checklist
After fixes we verify:
- No horizontal scroll on all breakpoints.
- All buttons and links are tappable (tap target ≥ 48px).
- Forms work correctly with mobile keyboard.
- Layout Shift (CLS < 0.1).
- Input font size at least 16px (prevents zoom on iOS).
- Popups and modal windows (
BX.PopupWindow) are correctly positioned.
BrowserStack is better than Chrome DevTools: real devices catch bugs with touch events and positioning that emulators miss. Entrust testing to professionals with extensive experience in 1C-Bitrix (over 5 years, 100+ projects). Order a responsive audit — and we will make your site convenient on any device.