Your website looks different on mobile: a step-by-step fix checklist
Short answer: A website that looks different on a phone is usually caused by one of five things: a missing or wrong viewport tag (a line of code that tells a phone how wide to draw the page), an element wider than the screen, a builder or plugin setting that overrides the mobile layout, an old cached copy of the page, or the phone itself showing the desktop version. Check the phone and cache first, then the viewport tag, then hunt for the wide element. Then test on a real phone, not just a narrowed desktop window.
Your site looks fine on your laptop but wrong on a phone, and you want to find out why and fix it without breaking the desktop version.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Most mobile problems have a small cause. Text that is tiny, a page that scrolls sideways, a menu that will not open, or images that spill off the screen are nearly always one wide element, one missing line of code or one setting. This guide gives you a fixed order of checks so you stop guessing. It works on any platform. Menu names differ between website builders, so use your builder's own help pages for the exact clicks.
Mobile matters for two reasons. Your visitors may be on phones, and Google uses the mobile version of your pages to decide how to index them. Both are covered below.
Step 1: Five minute triage, before you touch anything
Rule out the cheap causes first.
- Try a second phone and a second browser. If only one phone shows the problem, it is likely that phone's settings or browser, not your site.
- Check "request desktop site". Most phone browsers have a setting that asks for the desktop version of every page. If it is on, you will see the full desktop layout shrunk to fit. Turn it off for your site and reload.
- Open the page in a private or incognito window. This skips the cache and most extensions.
- Check the in-app browser. Links opened from inside apps such as Instagram or Facebook open in the app's own browser, which can behave differently from Safari or Chrome. Test it yourself: send yourself your link in a message from each app and open it there.
- Purge the cache. If you changed the site recently, clear the cache in your host, builder, caching plugin or CDN (content delivery network, a service that stores copies of your pages near visitors). An old cached page can show an old layout to phones only.
If it is fixed, stop. If not, move on to the site itself.
Step 2: Check the viewport tag
The viewport meta tag is one line in the head of your page that tells a phone to draw the page at the phone's width instead of at a wide desktop width. Without it, many phones render your page at about desktop width and shrink it, which is why the page looks tiny.
How to check: on your page, right click and choose View page source (on a phone, use a desktop browser). Search for the word viewport. You want to see this:
<meta name="viewport" content="width=device-width">
MDN Web Docs, Mozilla's reference for web developers, says that is the baseline. Adding initial-scale=1 is common practice and usually unnecessary, but it helps if overflowing content makes the page shrink. Avoid user-scalable=no and be careful with maximum-scale. They stop low-vision visitors from zooming, and the accessibility rules (WCAG, the Web Content Accessibility Guidelines) expect text to resize up to 200 percent without losing content.
Most website builders add this tag for you. If it is missing on yours, a custom code block or a theme edit has probably removed it. On a hand-built site, add it yourself or ask your developer.
Step 3: Reproduce the problem on your computer
You can see most layouts with Chrome's built-in tools, Chrome DevTools. Here is the routine.
- Open your page in Chrome. Press F12, or right click and choose Inspect.
- Click the Toggle device toolbar icon (it looks like a phone and tablet). Chrome's documentation calls this device mode.
- Choose Responsive and set the width to 360, then 390, then 320. Chrome's documentation lists width presets from 320 px (Mobile S) to 2560 px (4K), and Responsive mode lets you type any width. 320 px is a good "small phone" test.
- Turn on Show media queries to see where your layout changes width.
- For a speed picture too, pick the throttling option. Chrome describes Mid-tier mobile as fast 3G with a 4x CPU slowdown, and Low-end mobile as slow 3G with a 6x slowdown.
Chrome's own docs call device mode a first-order approximation, say some aspects of mobile devices can never be simulated, and recommend running your page on a real phone when in doubt. That is why Step 6 is a real device test.
Step 4: Find the element that is too wide
If the page scrolls sideways, or text is cut off at the right edge, something is wider than the screen. Common culprits are fixed-width elements, images without a maximum width, tables, embedded videos or maps, and long unbroken text such as a URL.
To find it, open DevTools Console at a 360 px width and paste this snippet, which lists every element that pokes out past the screen edge:
[...document.querySelectorAll('*')].filter(e => e.getBoundingClientRect().right > window.innerWidth).map(e => e.tagName + '.' + e.className)
The first few results are usually the real cause, because their children are listed after them. Then fix by type:
| Culprit | Typical fix |
|---|---|
| Image wider than screen | Set max-width: 100% and height: auto. Builders usually have a "fit to width" setting |
| Fixed pixel width (for example 1000px) | Change to a percentage, or max-width, or replace with a flexible layout setting |
| Table with many columns | Wrap in a scrolling container, or stack the cells on phones |
| Embedded video, map or form | Use the platform's responsive embed, or a wrapper that keeps the aspect ratio |
| Long word or URL | Allow wrapping with overflow-wrap: anywhere |
| Overlapping or ungrouped elements in a drag-and-drop builder | Group them into one section, and check the mobile stacking order in the builder's mobile editor |
Do not hide the overflow with overflow-x: hidden on the whole page as a first fix. It hides the symptom and can cut real content off. Find the element.
Step 5: Builder, theme and plugin overrides
- Separate mobile editor. Many drag-and-drop builders keep a separate mobile layout. Changes on desktop may not carry over, and elements can overlap or stack in the wrong order on the mobile view. Open the mobile editor and fix the order there. Check your builder's help for its mobile editor.
- Mobile modules and plugins. On WordPress, a plugin or theme setting that switches to a special mobile theme can override your layout. Turn off one plugin at a time and retest.
- Custom code. A custom code block or embed that sets fixed widths is a frequent cause. Remove it and see if the problem goes away.
- Fonts and tap targets. Text under about 16 px, or buttons close together, make a page feel broken even if it fits. Set body text to at least 16 px and give buttons enough space around them so a thumb can hit the right one.
Step 6: Test on real devices
A narrowed desktop window is not a phone. Real phones differ in browser engine, notches, toolbars that hide as you scroll, and fonts. Build a small test list and pass or fail each row.
| Device or setup | What to look at | Pass | Fail |
|---|---|---|---|
| Recent iPhone, Safari | Home page, a service page, the form | No sideways scroll, readable text, form submits | Any cut-off content or tiny text |
| Android phone, Chrome | Same pages | Same as above | Same |
| Older or small phone (about 320 to 375 px wide) | Header, menu, buttons | Menu opens, buttons tappable | Overlapping items |
| Phone in landscape | Header and menu | Usable | Header covers the page |
| Tablet | Layout at about 768 px | Tidy | Odd gaps or desktop menu squeezed |
| In-app browser (Instagram, Facebook) | Open your link from a message | Same as Safari or Chrome | Anything different |
No phone to hand? Borrow one from a friend or staff member, and ask a few customers to send a screenshot. Cloud device-testing services exist too, so check their sites for current prices if you want one. A cheap used phone often pays for itself quickly.
Chrome DevTools can also inspect a real Android phone connected to your computer by USB, so you can see its console while it shows your page. Chrome's remote debugging guide says you turn on USB debugging on the phone, open chrome://inspect on the computer and accept the prompt on the phone.
Step 7: What Google sees, and the mobile-first rule
Google's documentation says it uses the mobile version of your site, crawled with its smartphone agent, for all sites. So the phone version must hold the same content as the desktop one. Use this parity table.
| Check | What Google expects (mobile-first indexing guidance) |
|---|---|
| Content | Same main content on mobile and desktop. Content hidden in tabs or accordions is fine if it is equivalent |
| Structured data | Same on both versions |
| Title and meta description | Equivalent on both |
| Robots rules | Same robots meta tags and robots.txt rules |
| Images | Same alt text, and image URLs that do not change on every load |
| Lazy loading | Do not hide primary content behind a user action such as a click or scroll that never fires |
Google's April 2023 announcement said it would retire Search Console's Mobile Usability report, the Mobile-Friendly Test tool and its API from December 1, 2023, so do not rely on them. Today, use Lighthouse (a free auditing tool built into Chrome) and PageSpeed Insights, Google's page analysis tool at pagespeed.web.dev, and read the checks against the table above. For speed, see page speed problems on marketing sites. If you also rebuilt or moved the site recently, read how to keep SEO rankings when you rebuild or move a site and how to check your site for SEO problems. If traffic fell after a rebuild, see rankings dropped after a website migration.
How to confirm the fix worked
- The page does not scroll sideways at 320, 360 and 390 px in DevTools.
- The same pages pass on one real iPhone and one real Android phone.
- The menu, the phone number link and the form work with a thumb.
- The page also looks right after a cache purge and in a private window.
- Lighthouse mobile shows no layout shift or content-width warnings.
When to ask for help
Ask your builder's support or a developer if the problem appears only in one builder's mobile view and the editor offers no control, if the fix needs a code change you do not want to risk on a live site, or if you cannot find any element that overflows but the layout is still wrong. Send them screenshots from a real phone, the device and browser version, the page link and the list of steps above you already tried.
Copy-ready checklist
- Test on a second phone and in a private window. Turn off "request desktop site".
- Purge host, plugin and CDN caches.
- View source and confirm the viewport tag.
- Open DevTools device mode at 320, 360 and 390 px.
- Run the wide-element snippet. Fix the culprit.
- Check the builder's mobile editor and recent plugins or custom code.
- Test on one iPhone, one Android and one in-app browser.
- Compare mobile and desktop content, schema, titles and robots rules.
- Record each pass or fail with the date.
How I'd approach this
I would not redesign anything until I know the cause, because most mobile bugs are one setting or one wide element. Spend the first hour on the triage and the viewport check, since those cost nothing and fix a surprising share of cases. Spend the next hour on the wide-element snippet and the builder's mobile editor. Before you declare it done, test the form and the phone number link on a real phone, since a page can look perfect and still fail at the one thing that makes you money. Add a mobile check to every site update: open the three most important pages on one real phone after each change. If the form is part of what broke, use the forms not sending leads checklist too.
Blur Studio builds and cares for custom sites, so ongoing mobile checks are part of what I can take on. See what that includes if you would rather hand it over.
Questions people ask
Why does my website look different on mobile than on desktop?
A website is drawn by the browser each time. Phones have narrower screens, so the layout changes. Problems appear when the viewport tag is missing, an element is wider than the screen, a builder's mobile layout overrides your design, an old cached page is served, or the phone is set to request the desktop site.
How do I check if my website is mobile friendly?
Open the page in Chrome, press F12, toggle device mode, and test widths of 320, 360 and 390 pixels. Then open it on a real iPhone and a real Android phone. Google retired its Mobile-Friendly Test on December 1, 2023, so use Lighthouse and PageSpeed Insights, and check that your mobile and desktop versions hold the same content.
What is the viewport meta tag and do I need it?
It is a line in your page's head that tells phones to draw the page at the device's width. MDN's baseline is <meta name="viewport" content="width=device-width">. Without it, many phones show a tiny desktop-width page. Most builders add it automatically.
Does mobile layout affect my Google rankings?
Google says it uses the mobile version of your site for indexing across all sites, so content, titles, structured data and robots rules should match between mobile and desktop. It does not promise rankings from layout alone. Check the SEO problems guide for the wider picture.
Why does my site look right on desktop at a narrow width but wrong on a real phone?
A narrowed desktop window shares your desktop browser's engine, fonts and settings. Real phones have different browsers, toolbars and font handling. Chrome's own documentation says device mode is an approximation and that you should run your page on a real phone when in doubt.
My site scrolls sideways on mobile. How do I find the cause?
Something is wider than the screen. Run the wide-element snippet in the DevTools Console at 360 pixels wide, look at the first results, and fix by type: images, fixed widths, tables, embeds or long words. Avoid hiding the overflow on the whole page as the first fix.
Could the page speed be part of the mobile problem?
Yes. A slow page can look broken while it loads, with content jumping around. See page speed problems on marketing sites for the fixes and how to retest.
More in this topic: Websites: fixing migration, DNS, forms, speed and CRM problems (6 guides) →
Sources
- MDN: viewport meta element
- Google Search Central: mobile-first indexing best practices
- Chrome DevTools: device mode
- Google Search Central: page experience and helpful content (April 2023)
- web.dev: Core Web Vitals
- Chrome DevTools: remote debugging Android devices
- W3C: Understanding WCAG 1.4.4 Resize Text
- Google: About PageSpeed Insights