Fixing Mobile Problems: Responsive Breakpoints & Content Issues
With over 60% of web traffic coming from mobile devices, a broken mobile experience is a business problem. Here's how to identify and fix the most common mobile website issues.
Understanding Responsive Design
Responsive design uses CSS media queries to adjust layout and styling based on screen size. "Breakpoints" are the screen widths where these adjustments trigger. Common breakpoints include:
- Mobile: Up to 640px or 768px
- Tablet: 768px to 1024px
- Desktop: 1024px and above
- Large desktop: 1440px and above
Problems occur when content doesn't adapt properly at these breakpoints, or when specific device sizes fall between breakpoints without proper handling.
Common Mobile Issues
Horizontal Scrolling
If your page requires horizontal scrolling on mobile, something is too wide. Common culprits:
- Fixed-width images: Images with pixel widths instead of percentage or max-width
- Tables: Data tables often exceed mobile width
- Code blocks: Pre-formatted code with long lines
- Embedded content: Videos, maps, or iframes with fixed dimensions
- Long URLs or text: Unbroken strings that don't wrap
Fix by ensuring all content uses relative widths (100%, max-width) and that overflow is handled appropriately.
Quick Horizontal Scroll Fix
As a temporary measure, adding overflow-x: hidden to the body prevents horizontal scroll, but this hides the symptom, not the cause. Find and fix the oversized element for a proper solution.
Text Too Small to Read
If users need to pinch-zoom to read content, your text isn't scaling properly. Causes include:
- Missing or incorrect viewport meta tag
- Font sizes defined in pixels rather than relative units
- Body text smaller than 16px (minimum recommended)
Every responsive site needs this viewport tag in the head:
<meta name="viewport" content="width=device-width, initial-scale=1">Touch Targets Too Small
Links and buttons that work fine with a mouse may be impossible to tap accurately on mobile. Apple and Google recommend minimum touch targets of 44x44 pixels. Common fixes:
- Increase padding around links and buttons
- Space navigation items further apart
- Use larger icon sizes for clickable icons
Navigation Not Working
Mobile navigation often uses a "hamburger" menu that expands when tapped. If it's not working:
- JavaScript not loading: Check for console errors
- Menu hidden behind content: Z-index issues
- Click handler not attached: Event listener missing on mobile
- Menu off-screen: Positioned outside the viewport
Test navigation functionality, not just appearance. Tap the menu icon and verify it expands properly.
Content Hidden or Missing
Sometimes elements visible on desktop are hidden on mobile, intentionally or by accident:
- Intentional: Some content is hidden on mobile for simplicity (check CSS display rules)
- Accidental: Elements may be positioned off-screen or covered by other content
- Overflow: Content cut off by container with overflow: hidden
Use browser developer tools in mobile view to inspect hidden elements and understand why they're not visible.
Testing Mobile Issues
Browser Developer Tools
Every modern browser includes mobile emulation. In Chrome:
- Right-click and select "Inspect"
- Click the device toggle icon (or Ctrl+Shift+M)
- Select a device from the dropdown or set custom dimensions
- Refresh the page to trigger mobile-specific behaviors
This simulates screen size but doesn't perfectly replicate mobile behavior. Always confirm on real devices.
Real Device Testing
Nothing substitutes for testing on actual phones and tablets. At minimum, test on:
- An iPhone (Safari has unique behaviors)
- An Android phone (Chrome, which differs slightly from desktop Chrome)
- A tablet in both orientations
Google's Mobile-Friendly Test
Google provides a free mobile-friendly testing tool that identifies common issues affecting mobile usability and SEO:
search.google.com/test/mobile-friendly
This test checks viewport configuration, font sizes, touch target spacing, and content width.
Common Mobile Testing Mistakes
- Testing only in portrait orientation (test landscape too)
- Testing only on the latest iPhone (test older/smaller devices)
- Not testing forms and interactive elements
- Relying solely on browser emulation without real devices
Fixing Specific Problems
Images Not Scaling
Images should scale with their container. Add this CSS as a baseline:
img {
max-width: 100%;
height: auto;
}For images with fixed width/height attributes in HTML, either remove them or override with CSS.
Forms Difficult to Use
Mobile forms often have usability issues:
- Input fields too small: Use minimum height of 44px
- Labels not visible: Don't hide labels on mobile; use proper label elements
- Wrong keyboard type: Use type="email" for email, type="tel" for phone numbers
- Auto-zoom on focus: Happens when input font-size is below 16px
Video Not Playing
Mobile browsers have restrictions on auto-playing video:
- Videos must be muted to autoplay
- Some browsers block autoplay entirely
- Videos may not play inline without the playsinline attribute
For background videos, provide a fallback image that displays when video can't play.
Prevention: Mobile-First Development
The best way to avoid mobile issues is to design and build mobile-first:
- Start with the mobile layout and add complexity for larger screens
- Test on mobile devices throughout development, not just at the end
- Use relative units (%, em, rem, vw, vh) instead of fixed pixels
- Design touch-first interactions that also work with mouse
Final Thoughts
Mobile issues are often symptoms of deeper problems: fixed-width thinking, inadequate testing, or responsive design as an afterthought. Fixing individual issues is important, but the long-term solution is adopting a mobile-first mindset where small screens are the starting point, not a secondary consideration.