Last updated: October 2026.
A mobile friendly website fits the screen without sideways scrolling, loads in a couple of seconds on a phone, and puts every button within thumb reach. DigiFix builds and repairs websites for Australian businesses. This mobile friendly website checklist covers the 15 checks that matter in 2026, the tools Google still supports, and how to fix what fails.
Key takeaways
- Google uses the smartphone version of your pages for indexing and ranking, so a thin mobile page limits what Google knows about your site (Google Search Central, mobile-first indexing best practices).
- The Mobile-Friendly Test and the Mobile Usability report were retired on 1 December 2023, so the checks now live in Lighthouse, PageSpeed Insights and the Search Console Core Web Vitals report (Google Search Central blog).
- Core Web Vitals targets are judged at the 75th percentile of real page loads: LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 (web.dev, Core Web Vitals).
- Lighthouse flags a tap target as too small when it measures less than 48 pixels by 48 pixels, which is the number to design menus and buttons around (Chrome for Developers, tap targets audit).
- Mobile accounted for 48.57 per cent of Australian web traffic in September 2026 against 48.48 per cent for desktop, so neither version of your site can be treated as the spare (StatCounter Global Stats, September 2026).
The short answer: a website is mobile friendly when the same content, the same links and the same calls to action work on a phone as on a desktop, and when the page is fast enough that nobody gives up waiting. Everything else in this guide is a detail of those three things.
What makes a website mobile friendly in 2026?
Three things decide it: Google has to be able to read the mobile page, a visitor has to be able to use it with one thumb, and it has to load before the visitor loses patience. Google states the first point directly: “Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking” (Google Search Central, mobile-first indexing best practices).
Mobile first indexing: Google crawls and indexes the smartphone version of your page and uses that version for ranking. Anything missing on mobile is treated as missing from your site, including text, links, structured data and images.
The second and third points are measurable. Google uses Core Web Vitals for the loading side, and the targets are LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, assessed at the 75th percentile of page loads for real users (web.dev, Core Web Vitals). A phone on a train does not get the benefit of the doubt.
One more number worth knowing before you audit anything: DataReportal recorded 34.1 million cellular mobile connections in Australia, equal to 126 per cent of the population, and 26.2 million internet users, or 97.1 per cent penetration (DataReportal, Digital 2026 Australia). Your customers are already holding the device you are designing for.
How is mobile optimisation different from responsive design?
Responsive design is one way to build the site. Mobile optimisation is the whole job of making it usable and quick on a phone, including the words, the buttons, the forms and the images. You can have a responsive layout and still fail this checklist on tap targets and speed.
Responsive, adaptive and separate mobile sites compared
| Approach | How it works | SEO note |
|---|---|---|
| Responsive design | One URL, one set of HTML, CSS reflows the layout to the screen size | Google recommends it because it is the easiest pattern to implement and maintain, and there is no second URL to keep in sync |
| Adaptive or dynamic serving | One URL, different HTML served by user agent detection | Needs the Vary: user-agent header, and any mismatch between the two versions becomes an indexing problem |
| Separate mobile URLs | A second site, usually on an m. subdomain, with its own pages | Needs rel=alternate and rel=canonical pairing on every page, which is the easiest of the three to get wrong and the hardest to keep right |
One point worth settling early: a mobile friendly layout is not the same as a fast one. The layout decides whether a visitor can use the page, and the weight of the page decides whether they ever see it. Our website speed work covers the second half of that problem, and if you would rather start from a build that is fast on a phone by default, websites.digifix.com.au is where we build those.
If you are rebuilding or choosing a theme, pick responsive and spend the saved effort on speed. The comparison above follows Google’s own guidance on the three configurations (Google Search Central, mobile-first indexing best practices).
How can you check mobile friendliness in five minutes?
The old one click check is gone. Google retired the Mobile-Friendly Test and the Mobile Usability report on 1 December 2023, and the retirement notice says so in a single line (Google Search Central blog, updated 1 December 2023). Four replacements take about five minutes in total.
| Check | Where to run it | What a pass looks like |
|---|---|---|
| 1. Lab audit | Chrome DevTools, Lighthouse tab, Mobile device setting | No failed SEO or accessibility audits, and tap targets pass |
| 2. Field data | PageSpeed Insights, Mobile tab | LCP, INP and CLS all in the green for real Chrome users |
| 3. Whole site view | Search Console, Core Web Vitals report | Most URLs in the Good group, with a short list of failures to fix |
| 4. Thumb test | Your own phone, one hand, on mobile data | You reach the enquiry button without zooming or scrolling sideways |
Do the thumb test last and do it honestly: turn off the wifi, use one hand, and try to call or enquire in under 20 seconds. Most of the problems we find on client sites show up in that step rather than in the tooling.
Failed three or more checks? We will review your site on a call, free, and tell you which failures are costing you enquiries and which ones do not matter.
What is on the 15 point mobile friendly website checklist?
Fifteen checks, grouped so you can hand a section to whoever owns it. Work top to bottom: layout problems hide speed problems, and speed problems hide conversion problems.
| Group | Checks | First fix to try |
|---|---|---|
| Layout and content | 1 to 4 | Add the viewport meta tag with width=device-width, then retest |
| Text and readability | 5 to 6 | Raise body text to 16 pixels and check contrast at 4.5 to 1 |
| Buttons, links and navigation | 7 to 9 | Give every tappable element at least 48 pixels by 48 pixels of space |
| Forms | 10 to 11 | Cut the field count and set the right keyboard for each input type |
| Speed on mobile | 12 to 13 | Convert hero images to WebP, then lazy load everything below the fold |
| Pop-ups and interstitials | 14 | Move the newsletter prompt to exit intent or a scrolled position |
| Local business must-haves | 15 | Add click to call, a map link and one sticky enquiry button |
Layout and content
- 1. The viewport meta tag is present and reads width=device-width, initial-scale=1. Without it a phone renders your desktop layout at 980 pixels wide and shrinks it.
- 2. Nothing scrolls sideways at 360 pixels wide, which is still a common small phone width.
- 3. Pinch zoom is left enabled. Do not set maximum-scale to 1 or user-scalable to no, because that removes the accessibility fallback for anyone with reduced vision.
- 4. The same main content, headings and links appear on mobile as on desktop, since that is the version Google indexes.
Text and readability
- 5. Body text is at least 16 pixels on a phone, with paragraphs kept to a few lines each.
- 6. Body text contrast reaches 4.5 to 1 against its background, and larger headings at least 3 to 1.
Buttons, links and navigation
- 7. Every tappable element is at least 48 pixels by 48 pixels with space around it. That is the threshold Lighthouse uses when it flags a tap target as too small (Chrome for Developers, tap targets audit).
- 8. The main action, whether that is call, book or buy, sits in the lower half of the screen where a thumb naturally lands.
- 9. The menu opens without covering the page content, and it closes when a visitor picks something.
Forms
- 10. Ask for the fewest fields you can act on, and give each one the right keyboard: type=tel for phone, type=email for email, inputmode=numeric for postcodes.
- 11. Autocomplete attributes are set so a phone can fill name, email and address in one tap.
Speed on mobile
- 12. The Core Web Vitals report shows most URLs in the Good group, not just the homepage.
- 13. Images are served as WebP or AVIF at the size they display, with lazy loading below the fold. Google can still see lazy loaded content as long as it loads when it enters the viewport rather than on a tap (Google Search Central, lazy loading).
Pop-ups and interstitials
- 14. Nothing covers the content on arrival. A full screen pop-up the moment a phone visitor lands is the pattern Google names as intrusive.
Local business must-haves
- 15. A tap to call number in the header, a map or directions link, and one sticky enquiry button that follows the visitor down the page.
Want the checklist run on your site? We audit all 15 checks across your main templates, not just the homepage, and hand back a prioritised fix list with the effort and cost of each item.
Which mobile mistakes do Melbourne small business websites make?
The same six keep appearing in our audits. A slider image that is 2,400 pixels wide. A phone number that is text rather than a tel link. A booking form with nine fields. A cookie banner that covers the whole screen. A page builder loading three font families. And a homepage that looks fine on an iPhone 15 and falls apart on a four year old Android.
The scenario: a Clayton plumbing business, 14 jobs a month from the website
Situation. The site passed every check in 2021. In October 2026 the owner notices enquiries dropped while Google Ads clicks stayed flat. Mobile visitors are 71 per cent of sessions, average LCP on mobile is 4.6 seconds, and the call button sits in a menu that takes two taps to open.
What we would do, in order. Day 1: convert the hero image to WebP and defer the two unused font families, which normally pulls LCP under 3 seconds on its own. Day 2: move the phone number into the header as a tel link and add a sticky call button. Week 1: rewrite the booking form from nine fields to four and set the keyboard types. Week 2: fix tap targets across the service pages and re-run the Core Web Vitals report to confirm the pages move into the Good group.
What waiting costs. At 14 jobs a month and an average job value in the low hundreds, a quarter of lost mobile enquiries is a four figure sum every month, and the fix is measured in days of work rather than months.
Does a mobile friendly website help Google rankings?
Yes, with a caveat worth repeating. Page experience is evaluated per page and it works as a tiebreaker rather than a trump card. Google puts it this way: page experience is evaluated per page, and while Google prioritises relevant content, good page experience enhances success, especially when many relevant options exist (Google Search Central, Understanding page experience).
The practical reading is that a fast, usable mobile page will not outrank a more relevant competitor, but it will beat an equally relevant one, and it will convert better regardless of rank. If you want the keyword work that sits alongside this, our SEO services page covers how we approach it for Melbourne businesses.
How do you make a WordPress website mobile friendly?
WordPress is capable of a fast mobile site, and most of the weight on a slow one comes from the page builder, the plugin list and the images rather than the theme. In Divi, set the mobile and tablet views for each section rather than relying on the automatic stack, because an automatic stack often leaves the desktop padding and a large blank gap. In Elementor, check the responsive tab on every section for the same reason.
Then reduce weight in this order: images, fonts, plugins, JavaScript. Regenerate thumbnails at the sizes your theme actually requests, cap font families at two, and remove any plugin that is not earning its place. Our guides on website speed and WordPress website design in Melbourne go through that work in more detail. For the writing side, our guide on optimising website content covers keeping the same content readable on a small screen.
Should you fix a mobile site or rebuild it?
Fix it when the failures are layout, text size, tap targets, image weight or form fields, because all of those are changes inside the existing site. Rebuild when the mobile site is a separate build nobody maintains, when the builder itself is the bottleneck on speed, or when the content on mobile is a shortened version of the desktop page.
A useful test: if more than half of your fifteen checks fail and the site is more than four years old, the repair bill approaches the rebuild cost and a rebuild gets you a faster starting point. Our comparison of custom websites against templates sets out what changes when you rebuild properly.
Not sure which side of that line you are on? Send us the URL. We will run the checklist, tell you the honest answer, and quote the repair if a repair is the better spend.
What are the most common questions about mobile friendly websites?
Is a mobile friendly website a ranking factor?
Mobile friendliness affects rankings in two ways. Google indexes the mobile version of your pages, so a mobile page that hides content removes that content from consideration. Page experience, which includes Core Web Vitals, is then evaluated per page and used as a tiebreaker between pages of similar relevance, which Google describes as good page experience enhancing success when many relevant options exist.
What replaced the Google Mobile-Friendly Test?
Nothing with the same name. Google retired the Mobile-Friendly Test and the Mobile Usability report on 1 December 2023. Lighthouse in Chrome DevTools covers the lab checks, PageSpeed Insights shows field data from real Chrome users on the Mobile tab, and the Core Web Vitals report in Search Console shows how whole groups of URLs perform over time.
How fast should a mobile page load?
Google’s targets are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1, judged at the 75th percentile of page loads for real users rather than a single test. Treat 2.5 seconds as the line to clear on a mid range Android phone over mobile data, which is usually slower than the desktop test you run in the office.
Do I need a separate mobile website?
No, and we advise against it for most small businesses. A separate mobile site needs rel=alternate and rel=canonical pairing on every page, and any drift between the two versions becomes an indexing problem. Responsive design on one URL is what Google recommends, it is easier to maintain, and it removes a whole class of duplicate content mistakes before they happen.
How big should buttons be on mobile?
Design around 48 pixels by 48 pixels as a minimum for anything tappable, with space between neighbouring targets so a thumb cannot land on two at once. That is the threshold Lighthouse uses when it flags a tap target as too small, and it is a reasonable proxy for how forgiving your menu needs to be for someone holding a phone in one hand.
Does a slow mobile site lose customers?
Every second of delay costs you a share of visitors before they see your offer, and on a phone the delay is usually caused by images and scripts rather than the hosting. Fixing images, fonts and unused plugins is normally the cheapest work on the list, and it is the work we start with because it shows in the Core Web Vitals report within a couple of weeks.
Ready to fix this properly? DigiFix is a Melbourne web design and development team. Tell us what fails on your phone and we will scope the work, with a fixed price before we start.
DigiFix builds and maintains websites for Australian service businesses from our office in Clayton, Victoria. You can see the work in our portfolio, read other guides in the blog, or start with the full range of digital marketing services. Our about page covers how we work and who does the work.