Website · Mobile
More than 60% of Google searches now happen on a mobile device. Google switched to mobile-first indexing in 2019 — meaning it crawls and ranks your website based on how it looks on a phone, not a desktop. If your site doesn't work well on mobile, you're getting penalized in search rankings whether you know it or not. The good news: you don't always have to rebuild your site to fix it.
Google's mobile-first indexing means the mobile version of your site is the primary version it reads. If your desktop site is beautiful but your mobile experience is broken — slow load times, tiny text, buttons that are impossible to tap — Google sees the broken version and ranks you accordingly.
Beyond rankings, consider what happens when a potential customer clicks your site from a Google search on their phone and can't read the text, has to zoom in, or can't find your phone number. They leave. They call your competitor. A bad mobile experience doesn't just hurt rankings — it loses you customers in real time.
Before fixing anything, know what you're dealing with. Go to search.google.com/test/mobile-friendly and enter your URL. Google will tell you whether your page passes or fails, and flag specific issues.
Also run a PageSpeed test at pagespeed.web.dev — check the Mobile tab specifically. A score below 50 on mobile means you have significant problems. Below 70 means there's meaningful room to improve. Above 85 is where you want to be.
Test your most important pages individually — homepage, contact page, services page. They may have different issues.
This is the single most common mobile problem on older websites. Without the viewport tag, browsers render your site at desktop width and shrink it down — making everything tiny and unreadable.
Every page on your site must have this in the head section:
If you're on WordPress, Webflow, or Squarespace, this is usually added automatically by your theme. If you're on a custom-built or older site, check the source code (right-click → View Source, then search for "viewport"). If it's missing, add it immediately.
Body text should be at minimum 16px on mobile. Anything smaller forces users to zoom in. Headings should be readable without zooming — if your h1 is 48px on desktop and becomes 10px on a 375px phone, that's a problem.
Check your CSS for font sizes set in pixels without responsive adjustments. Use relative units (rem, em) or CSS clamp() for headings.
Don't use pixel-lock font sizes that don't scale. If your CSS says font-size: 10px anywhere on a mobile breakpoint, fix it now.
Google's standard: interactive elements (buttons, links, nav items) should be at least 48x48 pixels with adequate spacing between them. Tap targets that are too small or too close together cause mis-taps — users click the wrong thing and get frustrated.
The most common offenders:
Check your site on a real phone and try tapping every interactive element with your thumb. If you miss it or tap the wrong thing, fix it.
If a user can scroll sideways on your site, something is wrong. Horizontal scrolling breaks the mobile experience completely.
Common causes:
width: 1200px without max-width: 100%)Fix: Add max-width: 100%; overflow-x: hidden; to your body and main containers. Make all images use max-width: 100%; height: auto;. Wrap tables and embeds in a scrollable container.
Images are the #1 cause of slow mobile load times. A 4MB hero image that loads fast on fiber internet will kill your mobile score.
Target: all images under 200KB, hero images under 400KB.
Steps:
loading="lazy" attribute)Tools: Squoosh (squoosh.app) is free and browser-based. TinyPNG works for quick compression.
For WordPress sites, a plugin like Imagify or ShortPixel automates this for every upload.
Chrome DevTools mobile simulation is useful but not the same as a real device. Real phones have different rendering engines, different touch behavior, and different font rendering.
Pull out your actual iPhone or Android and open your site. Test every page. Tap every button. Fill out the contact form. Call your phone number from the link. If you find issues on a real device that didn't show in simulation — and you will — those are your real problems.
If you don't have an Android device, use BrowserStack's free trial to test on one. iOS and Android can render differently enough to matter.
Contact forms are high-stakes — if a customer can't submit your form on mobile, you lost the lead.
Common form problems on mobile:
autocomplete attributes (forces users to type everything)Fix: Set input height to at least 48px. Use appropriate type attributes (type="email", type="tel") so mobile keyboards switch automatically. Add autocomplete="name", autocomplete="email" etc. Test the entire form flow on a real phone.
Most mobile issues can be fixed without a full rebuild — especially if your site was built in a modern CMS (WordPress, Webflow, Squarespace). If your site was built before 2015 or is on a platform that doesn't support responsive design, a rebuild may be the better long-term investment.
Signs you should rebuild:
If your site is fairly modern but just needs tuning, work through the steps above first. A mobile audit before spending on a rebuild can save you money and time.
Yes, significantly. Google uses mobile-first indexing, meaning it evaluates and ranks your site based on its mobile version. A site that passes Google's Mobile-Friendly Test and loads fast on mobile will outrank a slow, hard-to-use mobile version — even if the desktop site looks great.
Go to search.google.com/test/mobile-friendly and enter your URL. Google will tell you whether your page passes and flag specific issues. Also test at pagespeed.web.dev — check the Mobile tab for your speed score and specific recommendations.
Mobile-first indexing means Google crawls and indexes the mobile version of your website first, and uses that version to determine your search rankings. Even if you have a perfect desktop site, your rankings are based on how your mobile version performs.
Above 85 is good, above 90 is excellent. A score below 50 on mobile means you likely have significant issues — large images, render-blocking scripts, or server problems. Focus on improving your score at pagespeed.web.dev, specifically the mobile tab.
No. Separate mobile sites (m.yoursite.com) are outdated and create more problems than they solve. The modern approach is responsive design — one website that adapts its layout to any screen size. If someone tells you that you need a separate mobile site, get a second opinion.
Start with your theme — use a responsive theme (most modern themes are). Check that your viewport meta tag is present. Install a performance plugin like WP Rocket or W3 Total Cache for speed. Use an image compression plugin like Imagify. Test each page at pagespeed.web.dev. If your current theme isn't responsive, switching themes is usually easier than patching a broken layout.