Cross-browser testing for small business websites

Key takeaways

Cross-browser testing means checking your website works in the browsers and devices your customers use, not just the one your designer uses. In the UK that means at least Safari on iPhone, Chrome on Android and Chrome, Edge and Safari on desktop. It catches broken layouts, unusable forms and missing buttons before customers find them.

• Test Safari on iPhone and Chrome on Android first.
• Then Chrome, Edge and Safari on desktop.
• Check your analytics for the browsers your visitors actually use.
• Test key journeys: menu, service page, form, checkout.

What is cross-browser testing?

Cross-browser testing is checking that a website looks and works correctly in different browsers, browser versions and devices. Browsers interpret code slightly differently, so a layout perfect in Chrome on a laptop may break in Safari on an iPhone.

• The most common business website design mistakes

Which browsers should a UK business test?

Start with the browsers your visitors use. Google Analytics 4 shows browser and device breakdowns. StatCounter publishes UK browser market share, which typically shows Chrome and Safari well ahead, with Edge and Samsung Internet behind. The GOV.UK Service Manual's guidance on testing browsers and devices is a useful reference.

• Which devices should you test your website on?

What design faults does testing catch?

Testing catches faults that are invisible on the designer's own setup.

• Layouts that overlap or break on Safari.
• Fonts that fail to load or fall back badly.
• Sticky headers or menus that cover content on iPhone.
• Form fields and date pickers that behave differently.
• Buttons or images that disappear.
• Videos that will not play or play with no controls.

• Website not working on iPhone? The usual Safari causes

How do you test without lots of devices?

Use the phones and computers you and your team already have to cover Safari on iPhone, Chrome on Android and desktop browsers. Browser developer tools can simulate screen sizes, though not every browser quirk. Paid cloud testing services give access to many real devices if you need more coverage.

What should you test in each browser?

Test journeys, not just pages. In each browser, open the homepage, use the menu, read a service page, send the contact form and, for shops, add to basket and reach checkout. Check the confirmation arrives.

• Website launch checklist

When should you test?

Test before launch, after any significant change, after platform or plug-in updates, and when major browser updates arrive. A quick monthly check of the contact form on an iPhone and an Android phone catches most problems early.

What does this look like in practice?

A pattern we see: a site built and reviewed on Windows laptops launches with a contact form button hidden behind the keyboard on iPhones. A five-minute check on an iPhone before launch would have caught it.

• See client work
• Website Design & Development for UK businesses
• Website design review: score your own site in 30 minutes

Cross-browser checklist

• Check analytics for visitors' browsers.
• Test Safari on iPhone and Chrome on Android.
• Test Chrome, Edge and Safari on desktop.
• Test menu, service page, form and checkout.
• Confirm form submissions arrive.
• Retest after updates and changes.

Next step

Send your own contact form from an iPhone and an Android phone this week.