Troubleshooting
How to Fix WordPress Mobile View: Causes and Fixes

Short answer
To fix WordPress mobile view, test on a real phone and in device mode, confirm your theme prints the viewport meta tag, find elements wider than the screen, correct page builder mobile settings and clear every cache. If the theme is old and not responsive, switch to a modern one.
Key takeaways
- Most mobile problems come from the theme, custom CSS or builder settings.
- A missing viewport tag makes the whole site look like a tiny desktop page.
- Sideways scrolling means one element is wider than the screen.
- Script delay settings often break mobile menus.
- Clear mobile, CDN and browser caches before judging a fix.
Why does a WordPress site look wrong on mobile?
A WordPress site usually breaks on mobile because the theme is not responsive, the viewport tag is missing, fixed-width content overflows, page builder mobile settings are wrong, or a cache serves old CSS.
Most modern themes are responsive by default. When the mobile view looks broken, something has usually overridden that behavior, such as a custom CSS rule, a wide image or table, or a plugin.
Common symptoms and where to look:
| Symptom | Likely cause | Where to fix |
|---|---|---|
| Whole page looks like a tiny desktop site | Missing viewport meta tag or old theme | Theme header or theme choice |
| Page scrolls sideways | An element wider than the screen | Wide images, tables, embeds or CSS |
| Text too small or too big | Font sizes set in fixed pixels | Theme typography settings |
| Menu missing or broken | Mobile menu script blocked | Caching, script delay or plugin conflict |
| Layout fine on desktop, mixed on phone | Page builder mobile overrides | Builder responsive mode |
| Changes not showing on phone | Mobile cache or CDN cache | Clear all caches |
Work through the sections below from the simplest checks to the deeper ones. For general mobile tuning, see our guide on adjusting WordPress for mobile.
How do you check the mobile view properly?
Test on a real phone and in your browser's device mode, and always clear caches or use a private window so you see the current version.
Desktop browsers include a responsive preview. In Chrome, open DevTools and switch on the device toolbar, described in the Chrome DevTools device mode guide. You can pick common phone sizes and rotate the screen.
The WordPress editor also has a preview menu with desktop, tablet and mobile views. These previews help, but they are not perfect. Real phones handle fonts, touch and browser bars differently.
Check several page types, such as the home page, a post, a page built with a builder and, for shops, a product page. A problem on one template points to that template or its content.
Is the viewport meta tag missing?
If the whole site shrinks to a tiny desktop layout on phones, the theme is probably not printing the viewport meta tag in the page head.
The viewport tag tells phones to use the device width instead of pretending to be a wide desktop screen. MDN explains it in its viewport meta tag reference.
To check, view the page source on desktop and search for viewport. You should see a line like this:
<meta name="viewport" content="width=device-width, initial-scale=1">
Modern themes add it automatically. If it is missing, you are likely using an old or custom theme. Adding the tag through a child theme helps, but an old theme often has other mobile problems too.
If the theme is very old, switching to a current responsive theme is usually the real fix. Our guide on changing a WordPress theme covers doing that safely.
Why does the page scroll sideways on phones?
Sideways scrolling happens when one element is wider than the screen, often an image, table, video embed, long URL or a fixed-width block.
Find the culprit in your browser's device mode. Scroll right and look for the element sticking out. In DevTools, hovering elements highlights their width.
Common causes and fixes:
- Images with a fixed width in pixels. Set max-width to 100 percent and height to auto.
- Tables with many columns. Wrap them in a scrolling container or simplify them for mobile.
- Embeds such as maps or iframes with fixed widths. Use responsive embed settings.
- Long words or URLs that cannot wrap. Use word wrapping rules or shorten the link text.
- Negative margins or wide rows in page builders. Reset them in the mobile settings.
A quick CSS rule often stops most image overflow:
img, video, iframe { max-width: 100%; height: auto; }
Add CSS in Appearance > Customize > Additional CSS on classic themes, or the Site Editor styles panel on block themes.
How do you fix page builder mobile settings?
Open the page in your builder's responsive mode and check spacing, columns, font sizes and hidden elements for the mobile breakpoint.
Builders such as Elementor, Divi and Beaver Builder store separate values for desktop, tablet and mobile. A large padding value on desktop can carry over to mobile and squeeze content.
Check these settings in mobile mode:
- Column widths, so columns stack at 100 percent
- Padding and margins, especially large left and right values
- Font sizes for headings
- Elements hidden or shown only on certain devices
- Fixed heights on sections, which can cut off content
Gutenberg blocks have fewer device settings. The Columns block includes a stack on mobile option, which should usually stay on.
Why is the mobile menu not working?
A mobile menu that will not open usually means its JavaScript is blocked by a script optimization setting, a plugin conflict or a JavaScript error.
Open the browser console in device mode and tap the menu button. Red errors point to a script problem.
Caching plugins that delay or defer JavaScript are the usual cause. Turn those features off, clear caches and test. If the menu works, add the theme's menu script to the plugin's exclusions.
If optimization is not the cause, test for a conflict with other plugins. Our guide on fixing a plugin conflict shows a safe process.
Also check that a menu is assigned to the mobile location in Appearance > Menus or in the Site Editor navigation block.
Why are your mobile changes not showing?
Mobile changes often do not appear because a separate mobile cache, a CDN or the phone's browser cache serves the old version.
Some caching plugins keep a separate cache for mobile devices. Purge everything, not only the desktop cache. Then clear your CDN cache if you use one.
On the phone, test in a private tab or clear the browser cache. Our guide on clearing cache in WordPress covers each layer.
If CSS edits still do not show, the rule might be overridden by a more specific selector. Our guide on CSS changes not showing walks through the checks.
How do you fix text size and spacing on mobile?
Set responsive font sizes in your theme or theme.json, and reduce large paddings and margins at mobile widths with CSS media queries.
Many block themes support fluid typography, where text scales between a minimum and maximum size. This avoids huge headings on small screens.
For classic themes, use the Customizer typography options if the theme has them. Otherwise, add a media query, which MDN covers in its guide to media queries:
@media (max-width: 600px) {
h1 { font-size: 2rem; }
.site-content { padding-left: 16px; padding-right: 16px; }
}
Keep body text at least 16 pixels. Smaller text is hard to read and makes phones zoom in on form fields.
Should you use a mobile plugin or AMP?
Usually no, because a responsive theme handles mobile better than a separate mobile theme or AMP, and those add extra maintenance.
Separate mobile themes and older AMP setups show a different version of the site to phones. That means two designs to maintain and more places for things to break.
Fix the responsive layout instead. If speed is the main issue on phones, see our guide on optimizing WordPress for mobile speed.
Google's guidance on responsive design basics explains why one responsive layout is the recommended approach.
How do you stop mobile problems coming back?
Check new pages on a phone before publishing, test after theme and plugin updates, and avoid fixed widths in custom CSS and builder settings.
A short habit list:
- Preview every new page in mobile mode before publishing
- Use percentages or max-width instead of fixed pixel widths
- Keep tables short or allow them to scroll
- Test the menu and forms on a phone after updates
- Use a child theme for custom CSS, so updates do not wipe it
If you are unsure whether WordPress itself is the problem, our guide on whether WordPress is mobile friendly explains how core, themes and plugins share the job.
Frequently asked questions
Why does my WordPress site look different on mobile than in the editor preview?
The editor preview approximates a phone but does not match real devices exactly. Caching, fonts, browser bars and touch behavior differ. Always confirm on a real phone in a private tab.
How do I hide an element on mobile in WordPress?
Page builders have device visibility settings for each element. Without a builder, add a CSS class to the block and hide it with a media query for small screens in Additional CSS.
Can a plugin fix WordPress mobile view?
Plugins can hide or adjust elements, but they rarely fix a non-responsive theme. Fixing the theme, custom CSS or builder settings gives a cleaner, longer lasting result.
Why is my WordPress site zoomed out on mobile?
The page is probably missing the viewport meta tag, or one element is so wide that the browser zooms out to fit it. Check the page source for the tag and look for overflowing content.
Does mobile view affect SEO?
Yes. Google indexes the mobile version of pages first, so content hidden or broken on phones can hurt rankings. A responsive layout with readable text and working links is the safe choice.
Sources
- Viewport meta tag MDN Web Docs
- Using media queries MDN Web Docs
- Simulate mobile devices with device mode Chrome for Developers
- Columns Block WordPress.org Documentation
- Responsive web design basics web.dev
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


