Testing: How to Test Your Website on Multiple Devices (Without Buying Them All)
Your website may look perfect on the computer used to build it and still be difficult to use on a customer's iPhone, Android phone, tablet, or older laptop. This matters because Singapore customers often discover businesses while commuting, shopping, or comparing services on mobile data. If a menu is cut off, a button is too small, a form cannot be completed, or important text sits outside the screen, visitors may leave before calling, booking, or buying. You do not need a cupboard full of devices to find these problems. With free browser tools and a small amount of organised testing, a complete beginner can check the important screen sizes and identify what needs fixing.
This guide explains a practical process for testing a website across multiple devices. It covers what to check, how to use free tools, when a real phone is necessary, and how to record problems clearly for your website provider.
What You Are Testing
Device testing is not only about asking whether a page “looks nice”. You are checking whether a customer can complete important tasks regardless of the screen they use. These tasks may include finding your address, tapping your phone number, submitting a contact form, selecting a product, paying for an order, reading a menu, or booking an appointment.
Different devices create different conditions. A wide desktop monitor can show several columns at once. A phone has a narrow screen and touch controls. A tablet sits between the two. Older phones may also have slower processors or less reliable connections. Your website should remain readable, usable, and trustworthy in all of these situations.
Step 1: List the Important Pages and Customer Tasks
- Write down your five most important pages. Start with the homepage, contact page, services or product page, booking or enquiry page, and checkout page if you sell online. Add any page that receives traffic from your advertisements or Google search.
- Write one customer task for each page. For example: “A customer can find our opening hours,” “A visitor can call us,” or “A shopper can add an item to the cart and pay.” Keep each task specific and easy to verify.
- Include the homepage header and footer. Menus, pop-ups, cookie notices, WhatsApp buttons, and footers often cause mobile problems even when the main page content looks fine.
Testing every page on every possible device is not realistic. Testing the pages and actions that produce enquiries or sales gives you the most useful result first.
Step 2: Check Your Website Using Your Own Phone
- Open your website on your phone using mobile data. Turn off Wi-Fi temporarily so you see a more realistic customer experience. Load the homepage in Safari on an iPhone or Chrome on an Android phone.
- Refresh the page and wait for it to finish loading. Look for images that are cropped strangely, text that flashes or moves, blank sections, and pop-ups that cover the entire screen.
- Try the tasks from Step 1. Tap the menu, open a page, call the business, complete a form, and proceed through checkout without submitting a real order.
- Rotate the phone. Test both portrait and landscape views. A layout that works vertically may overlap or become too wide horizontally.
- Use a different phone if possible. Ask a staff member or friend to test on the other major platform. An iPhone and an Android phone may display the same website differently because their browsers and font rendering are not identical.
Do not rely only on the phone used by the owner. A newer phone with a large screen can hide problems that are obvious on a smaller or older device.
Step 3: Use Your Browser’s Free Device Preview
Browser previews cannot replace every real-device test, but they are an efficient way to check many screen widths. They are available in Chrome, Edge, and other modern browsers.
- Open your website in Google Chrome on a computer. Go to the page you want to check.
- Open the browser inspection panel. Right-click the page and choose “Inspect”. If you are not comfortable with right-clicking, open Chrome’s three-dot menu, choose “More tools”, and then choose “Developer tools”.
- Turn on the device toolbar. Look for the icon shaped like a phone in front of a tablet. Click it to switch to a mobile preview.
- Select several device sizes. Check a small phone, a larger phone, a tablet, and a laptop-sized view. You can also choose “Responsive” and drag the page narrower and wider.
- Reload after changing size. Some menus, images, and scripts behave differently when the page loads at a new width. Reloading helps reveal these issues.
- Repeat the important customer tasks. Do not only look at the top of the homepage. Open the menu, scroll through the page, tap buttons, and enter sample information in forms.
When you use a browser preview, remember that the page is still running on your computer. It simulates the screen size but not every detail of a real phone, including touch behaviour, battery-saving modes, keyboard layout, and device performance.
Step 4: Test Common Screen Widths
You do not need to memorise device model numbers. Test a range of widths so that your site is not designed only for one popular phone. A useful basic set is:
- Small phone: approximately 320 to 360 pixels wide.
- Large phone: approximately 390 to 430 pixels wide.
- Tablet portrait: approximately 768 pixels wide.
- Tablet landscape or small laptop: approximately 1024 pixels wide.
- Desktop: approximately 1280 to 1440 pixels wide.
At each width, look for horizontal scrolling. Put your finger or mouse at the bottom of the page and check whether the page extends beyond the right edge. If it does, something is too wide, such as an image, table, button row, embedded map, or block of code. Horizontal scrolling is a strong sign that the mobile layout needs attention.
Step 5: Check the Mobile Menu and Navigation
- Open the menu from the top of the page. Confirm that the menu icon is visible and large enough to tap comfortably.
- Open every main menu item. Make sure the menu closes after a selection and that the selected page actually loads.
- Check dropdowns and submenus. They should not disappear off-screen or require a precise mouse hover that cannot be performed on a phone.
- Test the back button. A customer who opens the menu and then uses the browser’s back button should not get stuck or see an unexpected blank page.
- Check the phone number and address. Phone numbers should be tappable, and the address should be easy to copy or open in a map application.
Many Singapore businesses lose enquiries because their phone number is visible on desktop but buried below several screens of content on mobile. If calls matter to your business, put a clear call button near the top and repeat it at a sensible point near the bottom.
Step 6: Check Text, Images, and Buttons
- Read the text without zooming. Body text should be comfortable to read on a phone. If you must pinch and zoom, the text is probably too small or the layout is not working properly.
- Check headings and paragraphs. Look for headings that wrap into awkward single words, very long lines, or text placed on top of a busy image.
- Inspect every important image. Images should keep the main subject visible and should not be stretched, squashed, or cut in a way that hides the product or service.
- Tap every button. Buttons need enough space around them so that a thumb can select one button without accidentally pressing the next one.
- Check button labels. “Submit” is less helpful than “Request a quotation”, “Book an appointment”, or “Send enquiry”. The label should tell the visitor what will happen.
Pay special attention to floating chat, WhatsApp, and cookie buttons. These can cover checkout controls or form fields on a narrow screen. Move them if they block content.
Step 7: Test Forms, Booking, and Checkout
- Open the form on a phone. Tap each field and confirm that the correct keyboard appears. An email field should offer an email-friendly keyboard, while a phone field should allow numbers easily.
- Complete all required fields. Use a clearly marked test name and a safe email address that you can monitor. Do not use a real payment unless you intend to place an order.
- Try an incorrect entry. Leave one required field empty or enter an invalid email address. The error message should explain how to fix the problem and should not erase all the other information.
- Submit the form once. Confirm that the success message appears and that the business receives the notification. A spinning button with no confirmation is not enough.
- Test checkout from product to confirmation. Check quantity controls, delivery options, promo codes, payment fields, and the final confirmation page. Verify that the page does not require a desktop-only action.
This is one of the most valuable parts of the test. A website can look excellent while quietly losing leads because its form or payment process fails on mobile.
Step 8: Check Speed on a Mobile Connection
Use Google PageSpeed Insights or another reputable speed-testing tool to check important pages. Enter one page at a time and review the mobile report. You do not need to understand every technical recommendation. Focus first on large images, slow-loading videos, excessive pop-ups, and scripts that are not needed for the page.
- Test the homepage and a conversion page. A product, booking, contact, or checkout page is often more important than the homepage alone.
- Record the page load result. Take a screenshot or note the date and score so you can compare after changes.
- Fix the biggest items first. Compress oversized images, remove unused third-party widgets, and ask your website provider whether caching is enabled.
- Test again after each major change. A change that improves one page can create a problem elsewhere, so retest the customer tasks.
A speed score is useful, but do not chase a perfect number while ignoring whether customers can actually use the page. The goal is a fast, stable, usable experience.
Step 9: Record Problems So They Can Be Fixed Quickly
- Write the exact page address. Record the full URL rather than only saying “the product page”.
- Record the device and browser. For example: “Samsung Galaxy, Chrome, portrait view” or “iPhone, Safari, landscape view”.
- Describe the action and the result. Say “After tapping Checkout, the button moves off the right side of the screen” rather than “mobile checkout is broken”.
- Attach a screenshot or short screen recording. Include the problem and, if relevant, the steps that caused it.
- Rank the problem. Mark payment, enquiry forms, phone buttons, and broken navigation as urgent. Cosmetic spacing issues can follow.
Clear evidence saves time and reduces back-and-forth with a designer or developer. It also allows you to confirm that the exact issue has been fixed.
Step 10: Retest After Website Changes
Every update can affect another screen size. Retest after changing your theme, page builder, plugins, images, forms, payment system, pop-ups, or tracking tools. At minimum, repeat the homepage, menu, contact form, and checkout tests on one phone and one computer. After a larger redesign, repeat the complete checklist.
Keep a simple monthly reminder to test your most important customer journeys. Ask someone who was not involved in building the website to perform the tasks without guidance. A fresh tester is more likely to notice confusing labels and steps that the owner has learned to work around.
For more guides on managing your business website effectively, visit the complete collection at webcare.sg/guide/mobile
If you still need help, feel free to contact us at https://webcare.sg/contact for a free website health check.